NWMax Plus and NWgMax Plus Updated

[Legacy_Michael DarkAngel]

               @TheOneBlackRider

I can replicate your issue in gMax, unfortunately I'm not sure that I can fix it.  I already have a default value set for the new sanity check that was added.  3DSMax (at least 2014) does not exhibit this behavior, most likely because it is smart enough to apply the default value that I have set.  gMax on the othe hand crashes when attempting to open the MDL Base Parameters.

A dirty fix for this:

• Make sure the Modify panel is NOT selected prior to opening your saved scene file.
• Open your saved scene file.
• Select and Delete the AuroraBase helper (model base)
• Select the Create panel, click on the Helpers button.
• Select AuroraBase from the Object Type rollout
• Click anywhere in one of the viewports to drop the AuroraBase.  The Model Base Wizard will pop up, fill in and select what's necessary.
• Re-link as necessary and you should be good to go.

I'll keep trying to figure out a way to fix this, but so far I've come up empty.

@PSteMarie

The
'selfillumcolor' issue has been resolved, at least on the 3DSMax side. 
I need to apply the fixes to gMax which looks like that isn't going to
happen until tomorrow.

Incidentally, or perhaps it's
coincidentally, this will most likely break gMax scene files again. 
There is one more situation I need to test with 3DSMax, but so far
results there have been positive.

Look for an update at some point tomorrow.

Thanks for the help,


 MDA
               
               

               

                     Modifié par Michael DarkAngel, 14 janvier 2014 - 05:44 .
                     
                  

            

[Legacy_TheOneBlackRider]

               Thanks MDA!
Replacing the base does it - or, as written, (re-) importing the 4.08.23-exported model.
               
               

               
            

[Legacy_Michael DarkAngel]

               

Pstemarie wrote...
Great news!
Anyway to fix the misspelling of setfillumcolor...

Selfillumcolor and Setfillumcolor
As explained by OldMansBeard of the CTP Team It is not uncommon for a model exported by NWMax to not compile when run through nwnmdlcomp. This is caused by an error in the spelling of the “Setfillumcolor” parameter. At some point the spelling was incorrectly changed to “Selfillumcolor”. When you export a model using NWMax, the exporter scripts will change the spelling of “Setfillumcolor” to “Selfillumcolor”. NWMax IS WRONG, nwnmdlcomp is correct! Although the spelling has no effect in the game, to fix (so that you can properly compile your models), follow the procedure below:

1. Export the model using NWMax
2. Open the ascii file using Textpad.
3. Replace ALL instances of the word “selfillumcolr” with “setfillumcolor” (the correct spelling).
4. The models should now compile correctly with nwnmdlcomp.

I did some testing on this:

selfillumcolor is correct.  Thus the issue lies with nwnmdlcomp.

Using an ascii model, I tested the two spellings:

selfillumcolor 0.0 0.0 1.0

setfillumcolor 0.0 0.0 1.0

What does all this mean, it means NWMax was fixed long ago, and nwnmdlcomp has been the culprit all this time.

For the end-user.  If you want to compile your models you'll need to do so outside of NWMax/NWMax Plus, and you'll need to "fix" the ascii file prior to using nwnmdlcomp as stated above.

The way NWMax/NWMax Plus exports the ascii file works in game to produce the desired results.

I will attempt to fix this so that models can be compiled inside of NWMax Plus.


 MDA
               
               

               

                     Modifié par Michael DarkAngel, 23 février 2014 - 05:48 .
                     
                  

            

[Legacy_Tiberius_Morguhn]

               I always wondered about that.  "selfillumcolor" makes more sense as a directive name than "setfillumcolor".  Thanks for checking up on this!
               
               

               
            

[Legacy_Pstemarie]

               Yes, thanks. Just one more reason to not use compiled models I guess.
               
               

               
            

[Legacy_OldMansBeard]

               Yes, selfillumcolor is correct. There was a later version of nwnmdlcomp that fixed the bug, but AFAIK it wasn't made generally available.
Personally, I would recommend using the BW model compiler, with CM3.5 for decompiling. (But then, I'm biassed '>).
               
               

               

                     Modifié par OldMansBeard, 23 février 2014 - 06:43 .
                     
                  

            

[Legacy_Zwerkules]

               I haven't read this thread earlier, so I'm a little late when I say that selfillum is the correct spelling. I've used it hundreds of times also as selfillumcolorkey in animations and it works whereas setfillum doesn't.
I also ran these models through CM and it did NOT change selfillumcolor to setfillumcolor.
As Tiberius pointed out 'setfillumcolor' doesn't make sense.

Edit: I was typing this when OMB said that selfillum is the correct spelling. I only read his answer now.
               
               

               

                     Modifié par Zwerkules, 23 février 2014 - 06:52 .
                     
                  

            

[Legacy_Pstemarie]

               Well at least we have a definitive answer now. I was working off outdated information and hadn't realized that it was incorrect. Thanks for clearing it all up.
               
               

               
            

[Legacy_OldMansBeard]

               If you are using tools with the setfillumcolor bug in them (for example nwnmdlcomp or NWNExplorer) and you want to make yourself versions with the bug fixed, it is possible to do it using a hex editor. Edit the .exe file, find the string "setfillumcolor" and change the "t" (0x74) to an "l" (0x6C). It won't break anything because changing one byte to a different one doesn't disrupt any internal addresses.

Of course, if you edit nwnmdlcomp.exe to remove the bug, you will also have to remove the bug from your ascii models otherwise it won't compile them correctly any more. But, you can't have your cake and eat it, as they say.

In the version of NWNExplorer that I have (dated 2004-01-26), the offending character is at offset 0x78C12.

In the fixed version of nwnmdlcomp (dated 2006-01-25) the correct character is at offset 0xCAD3E.

I guess the bug is now 10 years old. Happy Birthday, bug.
               
               

               

                     Modifié par OldMansBeard, 23 février 2014 - 09:13 .
                     
                  

            

[Legacy_Bannor Bloodfist]

               Part of the problem is that both nwmax AND nwmaxplus include a physical copy of the WRONG  nwnmdlcomp.exe inside their respective script folders.  So that needed to be corrected for either one to function even semi correctly.

Even though the internal code for nwmax version 8 has been properly set to use the correctly spelled item, in this case "selfillumcolor" it still included the WRONG nwnmdlcomp which re-generates the bug.
               
               

               
            

[Legacy_Michael DarkAngel]

               

OldMansBeard wrote...

Yes, selfillumcolor is correct. There was a later version of nwnmdlcomp that fixed the bug, but AFAIK it wasn't made generally available.

Found it -->> here <<--

OldMansBeard wrote...

In the fixed version of nwnmdlcomp (dated 2006-01-25) the correct character is at offset 0xCAD3E.

And that is this version.

This will be included with the next update of NWMax Plus/NWgMax Plus which will also include a fix for PWK/DWK creation.

The import routine of NWMax and both Plus versions will accept either setfillumcolor or selfillumcolor, so if you have an ascii model with the error you won't need to change anything before importing it.  And they will all export the ascii file properly.

Checking "Compile Exported Model" seems to have an issue (at least on the 3DSMax side, haven't checked gMax yet).  The 3DSMax command "DOSCommand" does not like spaces in file or directory names.  I have fixed that issue and compiled model export works properly now.


 MDA
               
               

               
            

[Legacy_Michael DarkAngel]

               

Compiled model export issues resolved.

NWMax Plus v5.02.23 Now Available!!!

NWgMax Plus v5.02.23 Now Available!!!


Link is in the first post.

 

 MDA

               
               

               
            

[Legacy_Michael DarkAngel]

               

Fixed an issue with Lens Flare parameters.  Thanks to Rolo Kipp for bringing it to my attention.

 

NWMax Plus v5.04.22 Now Available!!!

 

NWgMax Plus v5.04.22 Now Available!!!

 

Links remain in the first post

 

 MDA

               
               

               
            

[Legacy_Pstemarie]

               

GAH, you posted before I got a chance to post an issue I ran into while attempting to mass scale some models. If the model fails a sanity check then you have to click OK in the popup warning to continue and the model doesn't export. Is there a way to bypass the sanity checks so that the popup doesn't occur and the model exports anyway. 

 

While I do understand its important to know if a model fails to pass sanity, I was scaling over roughly 600 models, of which I was aware some had sanity issues, and having to manually scale and export 110 models that failed their check was more annoying than anything else.

               
               

               
            

[Legacy_Michael DarkAngel]

               

GAH, you posted before I got a chance to post an issue I ran into while attempting to mass scale some models. If the model fails a sanity check then you have to click OK in the popup warning to continue and the model doesn't export. Is there a way to bypass the sanity checks so that the popup doesn't occur and the model exports anyway.

 

The Mass Scale Wizard turns off two of the Sanity Checks that most commonly cause issues prior to exporting, but yeah there could be other issues.

 

If you know what Sanity Check your models are failing you could turn them off prior to running the Mass Scale Wizard.  In the General Utils rollout you'll see the Reset Sanity Check group, uncheck any/all that you want and press the Set Sanity Checks button.  Then run the Mass Scale Wizard.

 

Keep in mind that this will reset the default for Sanity Checks, so that when you do want them you'll need to check the ones that you unchecked and press the Set Sanity Checks button again.

 

Hope that wasn't too confusing.

 

 MDA