I would like to bring a bizarre graphical bug to the attention of everybody that has been introduced with the release of the LOTV patch.
Some custom models, mainly ones that were created/exported using printIn´s m3 plugin for blender, now cause a weird graphical glitch on OTHER doodads, units and even cliffs that causes them to turn black. However, the imported model itself will display just fine.
The glitch just occurs on other doodads and units as soon as you put the model onto an actor that is currently placed on the map (be it a doodad or a unit). As soon as you remove the model from the actor, the graphics turn fine again. The glitch also disappears again if you simply remove all units/doodads from the terrain that have the bug-causing model.
This bug happens both ingame and in the editor. Note how the graphical glitch isnt consistent, as soon as you refresh the editor it will happen to different models.
Is anyone else experiencing this? Does anyone have any idea or clues as to why this is happening and how to fix it?
Help with this would be greatly appreciated.
Edit:
Ive found out that it has something to do with textures beeing assigned to the model. If I have no textures at all assigned to the model and export it, the bug does not happen. It doesnt even have to be a custom texture for it to break, if I simply export it with the texture path set to a normal SC2 texture, it still breaks.
Could anyone with access to the SC2 Art Tools maybe take a look at a problematic model and see what measures need to be taken to fix the bug? I could send you one of the models that cause these issues, obv.
Ive found out that it has something to do with textures beeing assigned to the model. If I have no textures at all assigned to the model and export it, the bug does not happen. It doesnt even have to be a custom texture for it to break, if I simply export it with the texture path set to a normal SC2 texture, it still breaks.
Edit: Could anyone with access to the SC2 Art Tools maybe take a look at a problematic model and see what measures need to be taken to fix the bug? I could send you one of the models that cause these issues, obv.
As Im obviously not the only one that experiences this, Ive made a thread about this over at the Blizzard forums. Please post in it if you have experienced this bug aswell:
it happens to me when i create a model on runtime (attach other hat model to a unit). i exported them all with printLn's script. it also affects shadows.
Heres another official forum thread you can post it in, I wasnt sure what was the better forum for it, editor issues or bug report. This thread is in bug report:
http://us.battle.net/sc2/en/forum/topic/19288270348
it happens to me when i create a model on runtime (attach other hat model to a unit). i exported them all with printLn's script. it also affects shadows.
Yeah, it happens with all models that have textures assigned to them exported through PrintIns plugin. Which is a shame because it seems like PrintIns M3 plugin for Blender is one of the most reliable (if not maybe THE most reliable) importer/exporter that SC2 has.
I've isolated the bug and found a way to fix it, but given my limited knowledge of python, I can't modify the script, and for now I can only hardcode the corrections.
I'm using println's m3toxml.py and xmltom3.py scripts included in the addon to edit manually the bugged xmls of the models.
The sections <unknowna44bf452>, <brightMult> and <brightness> should have the text "<nullValue>1.0</nullValue>" instead of "<nullValue>0.0</nullValue>"
After correcting all the lines where this happens, the models don't cause the bug anymore.
If someone can find println, or knows how to edit his scripts, this could be easily fixed directly in the addon. Meanwhile, I'm analyzing the option of making a batch file to carry my solution automaticaly (I still have to learn and plan how to do it), since I have around 60 models published to fix myself...
UPDATE: I've finally made a batch with the fix. Can you test it on your bugged models?
Heyho,
I would like to bring a bizarre graphical bug to the attention of everybody that has been introduced with the release of the LOTV patch.
Some custom models, mainly ones that were created/exported using printIn´s m3 plugin for blender, now cause a weird graphical glitch on OTHER doodads, units and even cliffs that causes them to turn black. However, the imported model itself will display just fine.
The glitch just occurs on other doodads and units as soon as you put the model onto an actor that is currently placed on the map (be it a doodad or a unit). As soon as you remove the model from the actor, the graphics turn fine again. The glitch also disappears again if you simply remove all units/doodads from the terrain that have the bug-causing model.
This bug happens both ingame and in the editor. Note how the graphical glitch isnt consistent, as soon as you refresh the editor it will happen to different models.
Is anyone else experiencing this? Does anyone have any idea or clues as to why this is happening and how to fix it?
Help with this would be greatly appreciated.
Edit: Ive found out that it has something to do with textures beeing assigned to the model. If I have no textures at all assigned to the model and export it, the bug does not happen. It doesnt even have to be a custom texture for it to break, if I simply export it with the texture path set to a normal SC2 texture, it still breaks.
Could anyone with access to the SC2 Art Tools maybe take a look at a problematic model and see what measures need to be taken to fix the bug? I could send you one of the models that cause these issues, obv.
Yeah I've had this happen, it's weird. It only happens in a part of the map.
Ive found out that it has something to do with textures beeing assigned to the model. If I have no textures at all assigned to the model and export it, the bug does not happen. It doesnt even have to be a custom texture for it to break, if I simply export it with the texture path set to a normal SC2 texture, it still breaks.
Edit: Could anyone with access to the SC2 Art Tools maybe take a look at a problematic model and see what measures need to be taken to fix the bug? I could send you one of the models that cause these issues, obv.
As Im obviously not the only one that experiences this, Ive made a thread about this over at the Blizzard forums. Please post in it if you have experienced this bug aswell:
http://us.battle.net/sc2/en/forum/topic/19288110445
@Crainy: Go
Does it only show up on low settings?
Nope, affect extreme too.
No, on all. As far as I know, Ive only tested extreme, though. I doubt its settings related.
it happens to me when i create a model on runtime (attach other hat model to a unit). i exported them all with printLn's script. it also affects shadows.
Heres another official forum thread you can post it in, I wasnt sure what was the better forum for it, editor issues or bug report. This thread is in bug report: http://us.battle.net/sc2/en/forum/topic/19288270348
Yeah, it happens with all models that have textures assigned to them exported through PrintIns plugin. Which is a shame because it seems like PrintIns M3 plugin for Blender is one of the most reliable (if not maybe THE most reliable) importer/exporter that SC2 has.
jeah i agree, it's also easy to use and to understand.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAllright.
I've isolated the bug and found a way to fix it, but given my limited knowledge of python, I can't modify the script, and for now I can only hardcode the corrections.
I'm using println's m3toxml.py and xmltom3.py scripts included in the addon to edit manually the bugged xmls of the models.
The sections <unknowna44bf452>, <brightMult> and <brightness> should have the text "<nullValue>1.0</nullValue>" instead of "<nullValue>0.0</nullValue>"
After correcting all the lines where this happens, the models don't cause the bug anymore.
If someone can find println, or knows how to edit his scripts, this could be easily fixed directly in the addon. Meanwhile, I'm analyzing the option of making a batch file to carry my solution automaticaly (I still have to learn and plan how to do it), since I have around 60 models published to fix myself...
UPDATE: I've finally made a batch with the fix. Can you test it on your bugged models?
Check out my kitbashes! Custom Campaign Initiative: Lots of great Custom Campaigns!! Check out and Support!!
Thanks for the fix, I merged it.