mdls when rendered in FSX appear identical, I'm hopeful the Emissive Mode issue may be the only one of concern to me. corresponding differences in the LODT block.īut, since the.~50% more vertices - perhaps also due to the different Emissive Modes, and.there is a single bit difference in the MATE blocks - presumably due to the Emissive Mode issue discussed above,.the Win10/64 version includes a two-byte SMAP block - which seems of no consequence,.However, a byte-by-byte comparison of the respective.
#Windows 10 fsnavigator windows 7
A quick pass through ModelConverter X to switch it back to "Blend" and my ground/ramp illumination returns - a PITA but better than no ground/ ramp lighting.Ī byte-by-byte comparison of the Gmax file saved under Windows 7 and the same file simply loaded and saved with Win10/64 shows a large number of differences, so I suspect this one may be the first of several issues to be dealt with. But, when the model is exported with the FSX gamepack under Win10/64, the Emissive mode parameter is changed to the default "Additive Night Only". I use transparent planes just above the ground for night-time ground/ramp illumination with an Emissive Mode setting of "Blend". The problem (or at least the one I'm experiencing), has to do with the FSX material Emissive Mode parameter. After some further investigation, that turns out not to be the case. Yesterday, I reported that it appeared there was a problem with linked objects. This does not fix the freeze when clicking Look In: in the Open/Save File dialogs, so avoid clicking on that, but if you do then Gmax will probably unfreeze in around 15 minutes.Ĭlick to expand.I've discovered the next layer of the "onion". Just avoid clicking on the FileSystem radio button (I never do anyway). You can access any scene materials and also create new materials in the navigator. It seems to be OK to open material libraries. I don't know a way to prevent that, other than mute your audio.Īvoid exploring the file system in the material navigator as this will cause the freezeup. You'll get a beep when opening material navigator due to the invalid drive. Now you can open Gmax with the FSX gamepack and open the material navigator. Under Attributes check the box that says Read-only and click OK In file explorer, right click the abrowser.cfg file that you just edited and choose Properties. To prevent this I make the file Read-only:
#Windows 10 fsnavigator update
Gmax will update this file everytime you close material navigator and replace the value with a valid path, causing the freeze to happen again. The invalid drive will prevent the freeze when you open the material navigator. On my machine I don't have a G: drive, so I change the line like this: In this file there should be a line like this:Ĭhange the above C:\gmax to an invalid drive name for your system. Open the abrowser.cfg file that's in the FSX_GmaxGamePack folder with notepad or your favorite text editor. The file will be created in gmax\PlugCFG)
(In case you don't have any abrowser.cfg file, open gmax.exe without the gamepack shortcut, open the material navigator, then close it and exit gmax. If not, then you should be able to copy it from "gmax\PlugCFG" folder into the FSX_GmaxGamePack folder. In the "gmax\gamepacks\FSX_GmaxGamePack" folder, there should be a file called "abrowser.cfg". I haven't found the root cause, but here's another workaround: