Model lights up the whole map

[Tommi Gustafsson]

Hello!

I have come up with a few models a problem that a model lights up the whole map.
Now, I came with the same problem with my edit of Mephestrial's Gnoll Mystweaver model (attached).
I posted a video on YouTube about it:

You can see in the video how, when the Mystweaver is trained, it will change lighting dramatically. I also tested that when the Mystweaver dies and has decayed, the light disappears.

The original Mystweaver does not have this problem. I only edited the camera with Magos' Model Editor, but it caused also this side effect.

Can anyone help me fix the problem?

Thanks a lot,
Tommi

 

[Warseeker]

The source of this problem is due to the intensity of the lighting which lights up the entire map in the editor and in-game, To fix it you should reduce the intensity to 10 for example instead of 14 which is higher, or simply remove this lighting in the node manager directly.

 

[Tommi Gustafsson]

The source of this problem is due to the intensity of the lighting which lights up the entire map in the editor and in-game, To fix it you should reduce the intensity to 10 for example instead of 14 which is higher, or simply remove this lighting in the node manager directly.

Any idea why the original model works and causes no problems?

 

[Tommi Gustafsson]

The source of this problem is due to the intensity of the lighting which lights up the entire map in the editor and in-game, To fix it you should reduce the intensity to 10 for example instead of 14 which is higher, or simply remove this lighting in the node manager directly.

I tried this as well, but it did not fix the problem.
Removing the light did, but it would be nice to have small light like in the original model.

 

[Tommi Gustafsson]

The problem seems to be with the MDX MDL Converter. When I convert the original file to MDL and then back to MDX, the problem occurs.

 

[Tommi Gustafsson]

I can confirm that the problem is indeed with MDLX Converter. I edited the original file directly from MDX and it caused no bug. The model worked perfectly. It seems that MDLX Converter cannot be used. Is there any other tool that we can use instead?

 

[Tommi Gustafsson]

The problem has been indeed reported before:
MDLX Converter

 

[Tommi Gustafsson]

I tried Retera's Matrix Eater for MDL<->MDX conversion, and it did not produce any bugs. It seems that we have to use it instead.

 

[Zwiebelchen]

Remember when you use omnilights in your models, that they must have the same intensity value as all the default omnilights in WC3 (for example of the lanterns).

Otherwise the game engine will crash once you view the model once and all omnilights in your map will malfunction.

 

[GhostWolf]

What exactly is the problem with that model? must the intensity be 10? what are the rules? Thanks.

 

[Tommi Gustafsson]

What exactly is the problem with that model? must the intensity be 10? what are the rules? Thanks.

The original model has no problems, but the culprit was MDLX Converter, which I used to convert MDX to MDL format and vice versa. That program messed up with omnilight intensity and it became so high that the lantern omnilight lighted up the whole map.

 

[GhostWolf]

Yes, the bad model. Do you know the exact rules? must the intensity always be 10 for every light, or what? (and if so why it exists)
I would like to add a test for this in the sanity tester, so I need to know how it should work.

 

[Dr Super Good]

Technically WC3 does not support intensities larger than 1.0 due to no HDR shaders. Instead what I suspect is happening is that the intensity is controlling the range of the light. The light falloff polynomial is fixed and the light intensity multiplier computed for a pixel is automatically clamped to at most 1.0 (no HDR). Hence a higher than 1.0 intensity means that the intensity multiplier will remain 1.0 for more distance.

The reason lights start to break if there are too many per vertex patch is because the fixed function shaders can only apply 8 lights simultaneously when rendering. The WC3 engine uses some selection algorithm to choose which 8 lights are used in the case of there being more than 8 lights, however it is possible it will discard the environment model lights.

 

[GhostWolf]

Is that supposed to answer my question? someone else's? because it isn't related to anything in this thread.

 

[Tommi Gustafsson]

I got now the unofficial MDLX Converter 1.04 and it works, but I have another problem with the Gnoll Mystweaver model:
When I click the unit with the Mystweaver model it also lights up a small area in the middle of the map (about the size of a lantern).

Any idea what might be causing it? The original model has also this problem.

 

[PROXY]

Is that supposed to answer my question? someone else's? because it isn't related to anything in this thread.

I suspect that the number 10 counts as the 1.0 in the Dr.'s message. So it would somewhow explain a part of it. So everything over 10 would count as surpassing the 1.0 limit he was talking about.