Aller au contenu

Photo

Custom placeable tooset error.


  • Veuillez vous connecter pour répondre
5 réponses à ce sujet

#1
IAmDeathComeForThee

IAmDeathComeForThee
  • Members
  • 288 messages

I'm getting the following error seemingly at random on placeables I export from 3ds.  Some get the error, some dont.  The name's aren't too long and follow the proper PLC_MC etc etc format as well as each individual object inside of 3ds named accordingly.  It doesn't matter if ther is a C2, C3, both or no collision meshes on the object exported, the error still persists.

 

It pops up when moving across certain interior tiles, or simply if I export the area as an erf.  If there are 2 placeables in the area, the error will pop up twice while exporting, 3 such placeables, 3 errors and so on and so forth during the exporting process.

 

When the error pops up moving across a tile, it seems to be on tiles with hook points attached to them and the placeable tries to jump to that hookpoint it seems.  Any ideas?  This is very very frustrating, especially when trying to place and arrange these placeables within interiors. :(

 

The key phrase in the error seems to be "get_HookableInstanceType()."   I never placed any hookpoints on these placeables either.

 

 

244zl0m.png



#2
Morbane

Morbane
  • Members
  • 1 883 messages

have you tried "lock position" for the placeables in question?



#3
IAmDeathComeForThee

IAmDeathComeForThee
  • Members
  • 288 messages

"lock position,"  you mean in the toolset?  That wouldn't get rid of the error no, and I wouldnt be able to get it into the area where I wanted it either.  I should clarify too, the placeables aren't always constantly trying to snap into place while moving it around a tile, Ive just noticed it happen one or two times.  But the error just "pops up" as I move the placeable across the tile, and pressing ok makes the error just pop up instantly again.  It almost gets caught in an infinite loop where I have to hold the enter key and move the mouse curser off the tile until the placeable eventually makes it's way off to the edge and the error stops.



#4
rjshae

rjshae
  • Members
  • 4 505 messages

These placeables you exported from 3ds, did you make sure you are using different names for all the component part numbers than are used for component parts in any other placeables? They all need to be unique. Also check your numbering in the placeables.2da file and make sure you don't have a duplicate row number.



#5
PJ156

PJ156
  • Members
  • 2 986 messages

Is this is happening on interiors only

 

If so there's a good chance it's your 2da settings.

 

Check column 7 after the row number. it should be checked with a 0.

 

I don't have tkedit downloaded yet to tell you the column name sorry.

 

PJ



#6
IAmDeathComeForThee

IAmDeathComeForThee
  • Members
  • 288 messages

Wow... Well I think I have you to thank PJ, we may have solved it. It wasn't column 7, but there is a column called IsAccessory (2nd last column?) in placeables.2da that I had astrixed, ****, it out whereas it should have been set to 0!

Um, this is somewhat (extremely) exciting as this has been quite the mystery for quite some time. Thanks for the advice to at least look into placeables.2da. This had been plaguing me for a long long time. :) :) :)