WW Pro Alpha Known Issues

Started by wallworm, January 19, 2015, 10:17:50 PM

Previous topic - Next topic

wallworm

There are some known issues in the WW PRO Alpha that some WW users are testing now. This page is just to discuss them as they are issues that will be addressed. They include functions or features that we currently know about. If you find a broken feature in WW Pro, please feel free to post it here.

Compatibility:
* Wall Worm and Wall Worm Pro may not work in Windows 8. We are looking into this. Fixed

Installer
* WW Pro functions may be blocked by Windows unless you manually unblock the WWPro download zip as described in the WallWormPro.txt that comes with the download.

* The WW Pro installer does not work unless Max is opened with the Run as Administrator method. Even when running as administrator, you may still need to manually copy the VTFLib.dll as described in the WallWormPro.txt that comes with the download.

* Some Antivirus/security software mistakenly detect the WallWorm.Stubs.dll as a Trojan. This is a false positive. We've posted the entire source code of this DLL here: http://www.wallworm.net/index.php/topic,1241.msg3556.html . If your AV software falsely detects this, the DLL files are generally immediately deleted upon installation. You'll need to disable your AV during installation and add an exclusion for the file after installation.

Settings
* The FGD parser crashes when set to use left4dead2.fgd . Fixed

Model:
* DMX Support is limited to Mesh and Skeleton. Flex and animation support is not yet added.

* DMX export has incorrect skin weights if your global settings is not set to WW Pro.

* DMX Exporter will crash Max if the global settings not set to use WW Pro. Set the SMD Exporter to WW Pro if using the DMX exporter. This won't be necessary in future versions.

* DMX Wrinklemap tools still experimental.

* VTA exporter is slower in Pro than standard WW. We are looking into this.

VMF Exporter:

* If all objects are in the default layer, then you may find that all nodes are invisible when you open the scene in Hammer. They are in Hidden visgroup. Fixed

* Some visgroups are hidden. Fixed

* Some nodes are hidden. This seems to affect Grouped geometry or CorVex nodes. We are looking into it. Fixed

Materials:

* The VMT Importer does not yet import WorldVertexTransition materials. If you need to import a blend material, temporarily change your global settings for Use MXS VMT Importer to ON.

* $include command is not yet implemented in WW Pro VMT Importer even if changelog says it does.

* The VTF Exporter no longer checks dimensions or texture class when WW Pro is installed. This is because WW Pro will have full VTF writing and the checks are not necessary. But at the moment, WW Pro us still using the standard compiler via VTEX.exe... so invalid dimensions or wrong file types can cause an error.

wallworm

#1
There is a bug in the WW Pro texture exporter that is forcing all textures to be output as normal. This is being fixed tonight. If you have WW Pro and your non-normal maps come out incorrect, open your bitmap node in Slate and uncheck the Normal flag.

wallworm

There was an update today to fix bugs in the wrinklemap tools in the DMX exporter. And with that:

http://www.youtube.com/watch?v=sQouaIZVcRc

wallworm

We've discovered a problem with the VMF exporter in WW Pro for non US users. We are looking into the solution right now.

wallworm

The installer for WW Pro was updated on 2015-6-17. Please read the updated installation instructions which have now been shortened with the latest version of WW.

wallworm

#5
It appears that there is a problem with the way WW Pro is launching the batch files for WW Pro VTF exporting on some systems. I'm looking into it now.

This is now fixed in the latest update to WW Pro.

wallworm

We have found a bottleneck in WW Pro when using Explicit Normals. We are looking into it to see what can be done.

wallworm

Update to WW Pro today to fix slow exports when using explicit normal.

SMF spam blocked by CleanTalk