3D Rad - Free 3D game maker - Forum

This forum is now archived!

This forum is locked, and is a read-only version. A new community-ran forum can be found at classdev.net

News:

The 3DRad community can be found at classdev.net.

Pages: [1]

Author Topic: 3drad bug involving imposters & animated sprites  (Read 245 times)

« on: January 09, 2014, 12:14:37 PM »
After creating 4 sets of imposter based on sprites, i set up the script to locate them, then hide them during initialization .

Then when a button is pressed, the specified sprite imposter is shown and animated.

Problem is the imposter sprites weren't all being hidden.

So i've spent a couple days now playing with my script, trying to figure out why this one sprite out of 4 wouldn't hide and show properly. ( the other 3 worked with the same script!)

I started to think the project was damaged in some way.

Well it turns out, the issue is the commands
 iObjectImposterHide(OBJ_X,int)
 iObjectImposterShow(OBJ_X,int)
don't work properly with animated sprites.

At first, i configured the program to use animated sprites, but then realized imposter commands can't control frames individually of an animated sprite.

So i separated the sprite frames into their own sprite objects, then created the imposters form them.

My issue was i forgot to separate this one sprite, which as it turns out, is the sprite showing the hide / show issue.

Now that this one sprite is NON FRAME ANIMATED, the imposter hide / show command works as expected.

Personally, i consider this a bug with 3drads handling of animated sprites, unless of course there is mention of this somewhere that i missed.
« Last Edit: January 09, 2014, 12:18:00 PM by TinSoldier »
« Reply #1 on: January 09, 2014, 04:51:43 PM »
iObjectImpostersCreate(OBJ_X,int)
   Create the specified number of imposters for the object (must be SkinMesh).
   Imposters are clones of the main SkinMesh object that can be placed by using the iObjectImposterSet() function.


Where*s the Bug?

Using 3D Rad 7.22
« Reply #2 on: January 09, 2014, 05:39:08 PM »
Well i'm glad you questioned me about this :)

I through together a project, using the same code as i used that showed the issue, to prove it.

Don't you know, 3drad is calling me a liar now.

Well, i can only attribute this to 3drad and an internal error that happens with time, or some other internal problem.
( i still contend 3drad doesn't handle arrays properly in certain situations)
( imposters involve arrays, so, i'll hold true to my bug report)

I'll continue at some point to play with this, to see if i can find an issue with my script, or not.

For now, all's well and working, so, this can wait :P.
Pages: [1]