2 réponses à ce sujet

[3RavensMore]

Is there an issue with animated emitters and GMax?  When I load the base game resource tile tdc01_g03_02.mdl (crypt, 3-way corridor intersection with fire effect) into GMax and export it, everything works fine.  If I save it as .gmax, reload it, and export, the fire fountain emitter is broken.

 

Here are the two .mdl.  Nothing is changed between them, expect reloading the .gmax version and exporting.

 

tdc01_g03_02.mdl

tdc01_g03_02.mdl (with broken emitter)

 

Any help would be appreciated. 

 

Do I need to just re-import the .mdl each time I edit, and never save as a .gmax scene file? 

[3RavensMore]

It seems all that I need to do is copy paste the working emitter node into the .gmax saved and exported version.  Is there any other tidbits that gmax may cause issues with when the files are saved as .gmax and later exported? 

[MerricksDad]

I've had many problems with emitters in gmax. One of the worst problems that I fixed in my custom nwmax scripts is to make the default values more accurate. I assume, but have not looked, that MDA did the same with his updated nwmax scripts.

 

What I can see right off is that the spawn type is not saving in a useful range. Note in the one it is -1, and the original is 1. -1 is not a proper integer index.

 

What you might find is that if you click the spawn type radio button to something else and then back again, the internal code onChange will record the value into the nwmax proper location, instead of resorting to a null default value. Then you should be able to keep using the same emitter from gmax saved files.

 

This was one of the many errors with emitters in the code I originally downloaded for nwmax. I think I started with 0.8b or something like that, and never got the newer updates from MDA, mostly because I put too much of my own work into the scripts and didn't want to have to merge mine with his.