BRF Edit 0.8.2

[Leprechaun]

Wonderful. No cloning textures and materials AT LAST!

[fujiwara]

Wasn't sure where to put this...

A question regarding a scabbard not showing up in the game. BRFEdit was used to make the scabbard (nice work, BTW Thor!)

http://forums.taleworlds.net/index.php/topic,8771.msg510271.html#msg510271

[RTWfreak132]

Thorgrim, you have any idea why this exception pops up when trying to load any brf files into brfedit?  this is the report I get: I checked my .NET and the other requirements.  this one has me baffled....I hope it's not something easy...

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at loadCompressedTexture(UInt32 tex, SByte* fileIn, BImage* image, Boolean mod)
   at CreateTexture(UInt32 tex, SByte* filename, BImage* image1)
   at loadMapModel(Int32 modelNum, Resource* meshIn, Mesh** mesh2, SByte* texture, SByte* mbPath, SByte* module, Int32 type, Int32 timeIn, Int32 renderType, Boolean wireframe, Boolean color, Boolean light, Int32 selBone, Boolean face, Scene* scene, Boolean positionAnim, Int32* textures, Int32 reachVal)
   at BRFEdit.Form1.resetDisplay()
   at BRFEdit.Form1.renderScene(Boolean initIt)
   at BRFEdit.Form1.updateMeshes()
   at BRFEdit.Form1.meshList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
BRFEdit
    Assembly Version: 1.0.2729.32
    Win32 Version:
    CodeBase: file:///C:/Documents%20and%20Settings/Ryan%20O'Connor/Desktop/BRFEdit.exe
----------------------------------------
msvcm80
    Assembly Version: 8.0.50727.1433
    Win32 Version: 8.00.50727.1433
    CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1433_x-ww_5cf844d2/msvcm80.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

[Agent Griff]

It happens to me as well, both when I try to open BRF Edit, and when I try to view objects.

I have come to understand, however, that two error messages in quick succession means something works, while only one error message followed by a message which gives the option to either quit or ignore symbolizes an imminent crash.