• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA dds files

Pyscen

Pyscen

Resource contributor
Messages
3,040
Country
us-texas
Arno or anyone...

I'm noticing a alot of drive activity when using dds files in MCX and after awhile MCX stops and states "out of memory". This occurs when placing them in the Material editor (and wasn't completed in doing so). MCX ask to either quit or continue etc... Trying to continue only causes additional problems.. I have 1 gig memory... possibly a memory leak? I have tried to do other things such as not placing all the dds files such as specular, bump etc though all the diffuse textures,... but when adding the others (bump etc), its starts up again.... Drawcalls: 43, Triangles: 8140 and 10459 Texture vertices.

Edited: Attempted again and got a "Microsoft .NET Framework" error and states:

Unhandled exception has occurred in your application. If you click Continue,....

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: The parameter is incorrect
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.PropertyGridInternal.PropertyGridView.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:
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ModelConverterX
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ModelConverterX.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version:
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:
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.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ObjectWriter
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ObjectWriter.DLL
----------------------------------------
TextureObject
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/TextureObject.DLL
----------------------------------------
ObjectModel3D
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ObjectModel3D.DLL
----------------------------------------
ObjectRenderer
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ObjectRenderer.DLL
----------------------------------------
GRV11DLL
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/GRV11DLL.DLL
----------------------------------------
ObjectReader
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ObjectReader.DLL
----------------------------------------
TextureLoader
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/TextureLoader.DLL
----------------------------------------
ObjectEditor
Assembly Version: 1.0.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///C:/Program%20Files/FS%20Design%20Tools/ModelConverterX/ObjectEditor.DLL
----------------------------------------
System.Design
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
----------------------------------------
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

This was placing _lm files in their corresponding places... and this came up.
 
Last edited:
I have a question relating to the same subject too:

When I load up a BGL file from FSX (within the scenery directory) and the dds files being used on thoses models... the info concerning the dds files is being inputed into the corresponding spots (such as diffuse, ambient colors, etc as well as the Emissive Mode). I noticed that if I load in other dds file or used default dds files into another model that I create those bits of information isn't being filled in... was this by design?

I would think if you would use or create a dds file, those pieces of information would be filled in; whether it was load from a bgl or not. Would I be right about that?

Just wondering :)
 
Hi Doug,

This happens with any model? Seems like I need to test a bit more if the material editor does not have a memory leak somewhere.

I am not sure if I understand the second question. These parameters you mention are part of the material. If you would change the texture file used the other material settings would not change. They are not linked to a specific textures.
 
arno said:
Hi Doug,

This happens with any model? Seems like I need to test a bit more if the material editor does not have a memory leak somewhere.

I am not sure if I understand the second question. These parameters you mention are part of the material. If you would change the texture file used the other material settings would not change. They are not linked to a specific textures.
Click to expand...

For instance: the default texture "sky_w_red3.dds" on model:
80e8ccee-7f76-44c3-a3cf-1afa2f4d2365 KDAL terminal
(OBX22200.bgl) the material editor is calling up:
61, 56, 47 diffuse/ambient color
255,255,255 specular color

Blend on the Emissive mode

I think a few other things were different then the default

If I used this same texture on a different model wouldn't it not have the same info, since the information on the texture is in the texture and not the model?

as of right now its the only model but it has done this before on others but that was way back when and has done it since now, with (the lastest) this version.

I have noticed that if I loaded say the previous bgl file and then the model I'm working on... it does activate my drive more... or load up other models of mine... if that helps..
 
Last edited:
No, those data are stored in the model...

Those are data properties of the Material definitions created in Max/GMax and exported with the model.

The bitmaps contain nothing but ARGB information...
 
Hi Doug,

As Bill said that is part of the material and stored in the model. The material also contains a reference to the texture file that should be used. All these things together determine how the object will look.

The texture itself is just a collection of coloured pixels. They have no knowledge about night textures, how shiny they are or whatever. That is all part of the material.

So by changing the material settings you can get exactly the same texture to appear different on an object.
 
Hi Doug,

I can confirm there is indeed a memory leak when changing textures very often in the material editor. I am trying to implement a fix for this now.
 
Hi,

I think I have fixed the memory leak. Could you try again with the next development release tomorrow?
 
arno said:
Hi,

I think I have fixed the memory leak. Could you try again with the next development release tomorrow?
Click to expand...

Yes I can,... in fact I might be able shortly due to the time changes involved... on the material editor and what stored in the texture etc... ok... I guess I misunderstood on one of the previous questions that I asked before about what is stored. Now that I have that clear,... I can move forward and adjusting accordingly.
 
Arno,...

It appears that did the trick... will continue working with and will notify you if it hadn't.... Thanks again!!

:D
 
You must log in or register to reply here.
Back
Top