jonwil
09-18-2005, 08:23 AM
There is an issue with the scenery importer that could affect your scenery.
It is not present in version 10 but is present in version 9.
It may cause issues with the scenery under some circumstances because it doesnt match with what is expected by the game.
The fix is to re-export the scenery in question using the latest importer version (really anything >= 10 will do) but the latest is best.
To tell if any of your scenery is affected, open the .common.ovl file for the scenery (not the style.common.ovl) in a hex editor (or if you dont have one of those, something like notepad might work)
If you see the string SceneryItem followed by svd (with some numbers inbetween them) you have a bad scenery item and it needs to be re-exported.
If you see the string SceneryItemVisual followed by svd, then you have a working item and no action needs to be taken.
If you think some of the scenery in the pack was exported by one version and some by another version, it might be a good idea to check all the scenery objects in the pack :)
You do not need to change the .thm file or the style.common.ovl or the .ase files at all. (if the affected scenery was built with version 6 or below, you probobly need to deal with the new UI for making scenery that was added to support multiple mesh objects etc.
You may need to flip the texture 180 so that its "up the right way" when looked at in the paint program (older versions of the importer had an issue where the texture had to be flipped to make it work right, newer versions dont have that).
Needless to say, dont use any version below 10 to build scenery anymore otherwise you will be affected by this bug. (using the latest is the best though)
If you are good with a hex editor, it might be possible to fix it by changing the string SceneryItem to SceneryItemVisual and the 0B 00 just before the string to 11 00 (must be done in both .common.ovl and .unique.ovl for each affected item) but I wouldnt recommend it unless you are good with a hex editor (and needless to say, make backups in case you stuff anything up)
If you need the latest scenery importer version, download from http://users.tpgi.com.au/adsloptd/rct3imp12.zip
Just to help people out, here is a list of which scenery from my own collection has this issue: (I may not have the latest version of all of these though)
Comic Heroes set
Feen Letters Arial
Feen Letters Wall
Hollywood Sign
KLN Electro Set
KLN Framework
MNM Dark Ride
PNP Food & Drink
PNP Wall Set
Pumper Dark Ride Set
Pumper Steel Worx
Pumper Blox
Ride Backdrops (Viper etc)
Tidus Wall Set
Top Gun
Warner Bros Logo
The fix will not affect the use in parks or require any changes to parks using the scenery.
All it will do is to correct an issue that could cause the game to refuse to recognize the scenery properly in some cases.
Needless to say, people using scenery that is broken should update to fixed scenery when it is available.
It is not present in version 10 but is present in version 9.
It may cause issues with the scenery under some circumstances because it doesnt match with what is expected by the game.
The fix is to re-export the scenery in question using the latest importer version (really anything >= 10 will do) but the latest is best.
To tell if any of your scenery is affected, open the .common.ovl file for the scenery (not the style.common.ovl) in a hex editor (or if you dont have one of those, something like notepad might work)
If you see the string SceneryItem followed by svd (with some numbers inbetween them) you have a bad scenery item and it needs to be re-exported.
If you see the string SceneryItemVisual followed by svd, then you have a working item and no action needs to be taken.
If you think some of the scenery in the pack was exported by one version and some by another version, it might be a good idea to check all the scenery objects in the pack :)
You do not need to change the .thm file or the style.common.ovl or the .ase files at all. (if the affected scenery was built with version 6 or below, you probobly need to deal with the new UI for making scenery that was added to support multiple mesh objects etc.
You may need to flip the texture 180 so that its "up the right way" when looked at in the paint program (older versions of the importer had an issue where the texture had to be flipped to make it work right, newer versions dont have that).
Needless to say, dont use any version below 10 to build scenery anymore otherwise you will be affected by this bug. (using the latest is the best though)
If you are good with a hex editor, it might be possible to fix it by changing the string SceneryItem to SceneryItemVisual and the 0B 00 just before the string to 11 00 (must be done in both .common.ovl and .unique.ovl for each affected item) but I wouldnt recommend it unless you are good with a hex editor (and needless to say, make backups in case you stuff anything up)
If you need the latest scenery importer version, download from http://users.tpgi.com.au/adsloptd/rct3imp12.zip
Just to help people out, here is a list of which scenery from my own collection has this issue: (I may not have the latest version of all of these though)
Comic Heroes set
Feen Letters Arial
Feen Letters Wall
Hollywood Sign
KLN Electro Set
KLN Framework
MNM Dark Ride
PNP Food & Drink
PNP Wall Set
Pumper Dark Ride Set
Pumper Steel Worx
Pumper Blox
Ride Backdrops (Viper etc)
Tidus Wall Set
Top Gun
Warner Bros Logo
The fix will not affect the use in parks or require any changes to parks using the scenery.
All it will do is to correct an issue that could cause the game to refuse to recognize the scenery properly in some cases.
Needless to say, people using scenery that is broken should update to fixed scenery when it is available.