• Welcome to SC4 Devotion Forum Archives.
 

News:

The SC4 Devotion Forums are no longer active, but remain online in an archived, read-only "museum" state.  It is not possible for regular members to post or use the private messaging system, and no technical support will be provided for any issues pertaining to the forums in their current state.  Attachments (those that still work) are accessible without login.

The LEX has been replaced with SC4Evermore (SC4E), and SC4E maintains an active Discord server.  For traditional forums, we recommend Simtropolis.

Main Menu

BSC Parks Exemplar Error

Started by Rakor, July 08, 2009, 04:19:17 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rakor

While researching an unrelated issue I found an exemplar mixup that affects most BSC Parks.  In almost all of them the property 0x87CD6399 - 'Landmark Effect' was used.  However, Maxis parks use the property 0x2781284F - also labeled 'Landmark Effect' in iReader.

The problem is that 0x87CD6399 is used as a general developer modifier, 1 for each developer type.  And it appears that the property is just ignored when used for a lot.

So, I changed it to the correct property ID and tested it.  The fixed parks now show a noticeable increase in the desirability chart for CO$$$ in comparison to the originals.  It took me 5-10 min to fix all the parks I had, but I thought I'de let you guys know.

As mentioned the problem probably stems from iReader having the same name for both IDs.

Andreas

IIRC, Maxis introduced the second "Landmark Effect" (and "Park Effect") property with Rush Hour, maybe to "fix" said issue with the developer modifier. Depending on the modding tool that was used to create the lot, or the lot that was used as a base when creating the new lot, the old property might be still included.
Andreas

RippleJet

Rakor, we've known about the existence of those two Landmarks Effects (and Park Effects) for quite a while:


  • 0x87CD6399 and 0x2781284F for Landmark Effect
  • 0x87CD6341 and 0x27812850 for Park Effect

However, it wasn't until you pointed it out now that I realised that those being of type Float32 (0x87CD6399 and 0x87CD6341) are indeed Developer Exemplar properties.
Not that I haven't known about them being in the developer exemplars, but I've never made the connection to that same property being in parks and landmarks.

Maxis Plugin Manager is indeed the program to blame here. ::)
Both for parks and landmarks, Maxis PIM adds the property 0x87CD6399 instead of 0x2781284F.

Luckily enough, for the X Tool, I've used the correct properties for parks and civic buildings.
However, eyecandy landmarks still have been getting the wrong Landmark Effect, copied from Maxis PIM.
Thanks to you I have now been able to fix that! Worth a Karma point for sure!

Now we unfortunately have to realise that almost all custom landmarks and all plazas made with Maxis PIM actually have no landmark effect... &mmm

Andreas

Wow, I'd never guessed that. Quite an interesting discovery indeed; looks like Rush Hour (and the Plugin Manager) was a bit "rushed" after all...  ::)
Andreas