![]() ![]()
This was always fixed by manually correcting the scenery.cfg. This was probably caused by *antother* product that act on the scenery.cfg, that can't deal with proper text encoding and saves back corrupted scenery.cfg files. Instead, they were caused by a corrupted scenery.cfg file with thousand of random names instead of the (c) Copyright symbol in the title of some scenery areas. Fumefx installation problem .dll#Other "DLL issues" people were having, weren't due to the Addon Manager. ![]() Fumefx installation problem install#The only catch, if you "switch" between an standard FS9.EXE and a nocd one, you need to run the Addon Manager (or any of our scenery) installer again, so it will be able to detect the change of the EXE and install the right version. This has been fixed months ago: the current version is now compatible both with >2GB FS9.EXE AND with the MS CD protection. Fumefx installation problem Patch#The original poster about the debugger problem is due to the fact he probably had an older version, the one that still didn't supported the >2GB patch together with the original MS CD protection. You have two options: Either drag a FumeFX path from the left to an alredy existing VrayVolumeGrid to change its linked simulation files or drag it to the element "Drop here to create a new VrayVolumeGrid" to create a new one that is placed and orientated correclty.There's nothing to be fixed right now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |