placeAtMe - seems unreliable?

[dafydd99]

I've made a simple stone tablet to 'display' numerals which can change over time. It can display one of ten numerals, so I'm using 'placeAtMe' to put that item in place. The numerals are statics and have no collision, just a few BSTriShape's.

 

function setNumber(int numeral)
	Debug.Trace("Setting number to:"+numeral)
	ObjectReference newNumeral=placeAtMe(NumeralsList.GetAt(numeral) as form, 1, true, true)
  	newNumeral.SetScale(numeralScale)
  	newNumeral.enableNoWait()

  	if(!newNumeral.is3DLoaded())
    	Debug.Trace("3D NOT loaded")
	endif
endfunction

This works around 99 times out of 100. But just once in a while it doesn't. It believes it has made a new objectreference, and it believes the 3d has been loaded, but no object is visible.

Anyone got any thoughts about this? I had thought that putting a slight delay (utility.wait(0.1)) between the setscale and enablenowait fixed it, but alas no.

Thanks in advance for any help.

Cheers - dafydd99

Edited Tuesday at 12:09 AM by dafydd99

[greyday01]

I wouldn't use place at me. I would simply put all the numerals in place but disabled. Use a script to enable the one you want and disable all the rest. You could put them in a form list and use that to disable and enable them.