3 respuestas en este tema

[sea-]

I've started receiving this error recently, even after doing a 100% fresh install of the Toolset:



This error only occurs when rendering outdoor terrain levels - indoor levels work just fine.  As I said, I reinstalled the Toolset, reinstalled just about every possible extension I can think of (Python, Visual C++ Redists, etc.) but nothing appears to fix it.

Judging by the error I would think it's some sort of permissions problem related to PhysX, which might be used for lightmapping terrain or vegetation, but I really couldn't say.

I should note that it used to work for me in the past, but I haven't rendered an outdoor level in a few months. I recently switched from a retail install of the game to a Steam install, so maybe that's related somehow... hm.

Also just tried disabling UAC, adding pretty much all the executables in the Toolset folder to the DEP exemption list... still no improvement.

Any ideas anyone has would be very much appreciated!

Editado por sea-, 27 diciembre 2012 - 05:41 .

[sea-]

Okay, success.

What I noticed is there are two files called GraphicsProcessorMMH.exe in the Toolset install folder, one in tools/export_processors and another in tools/ResourceBuild\\Processors\\MMH. I swapped the one in the export_processors folder with the one in the ResourceBuild folder, because I noticed they were different file sizes (2260 KB vs 2000 KB).

Outdoor lights now render correctly. I am not certain if this is down to a corrupt install, some mis-configured settings in an INI file somewhere, or... something else.

My suspicion is it may have something to do with the Ultimate Edition or Steam version of the game vs. the original retail version, however, as I've also noticed another problem since switching to the Ultimate Edition, namely that the default var_module list appears to be different and makes anything exported with that version break the game.

In any case, problem "solved" for now.

Editado por sea-, 27 diciembre 2012 - 06:27 .

[Karma]

Side topic: Can you post the var_module from the UE? I don't have the UE, but I'm curious about the changes it makes to var_module.

[sea-]

Posted about it already. I can't confirm if it was the Ultimate Edition that made that happen, but it persisted after reinstalling the Toolset.  If I try to export with it, it completely breaks activated abilities because I believe they rely on some of the variables in var_module to work properly.

Editado por sea-, 29 diciembre 2012 - 02:41 .