PlaceAtMe function vs. patch 1.5 and hire

[arcoolka]

I discovered that using of PlaceAtMe function for any vanillas tree Form ID (static object) with official Fo3 patch 1.5 and higher installed causes CTD. It is weird beacuse CTD doesnt appear for other static objects placed via this function. Any idea what is the reason and if it can be fixed?

 

PS: (CTD doesnt appear if patch 1.4 is installed)

[Skree000]

what is that object 00000000f

 

some objects cannot be placed in the world since they are references only, (ie. non geometric, non visual entities)

[gsmanners]

I use placeatme all the time in my mods, although admittedly not with static objects. It's entirely possible that you need to limit yourself to non-static or movable static objects with 1.5 or later.

[arcoolka]

other static objects work fine, also some trees (static objects), weird

 

0000000f ID for caps :)

[Skree000]

placeatme corrupts savegames, better to use player.additem

[Cipscis]

PlaceAtMe is only going to cause save game bloat if it's used in a way that might result in it being called any number of times. For example, a script like this could cause bloat:

Begin OnActivate

PlaceAtMe <Item>

End

However, a script like this will not cause bloat:

int bDoOnce

Begin OnActivate

if bDoOnce
else
	set bDoOnce to 1
	PlaceAtMe <Item>
endif

End

Likewise, calling PlaceAtMe in the console isn't going to cause any noticeable amount of savegame bloat. Some types of references, like explosions, are automatically cleaned up by the engine anyway.

 

I'm not sure what might be causing that CTD, but if you need to get around it try using Enable to enable a disabled tree, or moving a tree from a remote position to a marker.

 

Cipscis