Game Development Community

Added Items floating up to the sky

by Richard Marrevee · in Torque 3D Professional · 11/03/2010 (2:40 pm) · 3 replies

For some curious reason I have Items that after reloading a mission start floating up into the air. I've tried changing the mass and all the other options, but they still are going up.

Does anybody knows what causes this, and even better is there a solution?

Thanks in advance
Richard Marrevee's profile picture
Richard Marrevee
R.G.S - Richards Game Studio

About the author

Started programming in 1984 on an Oric, when time progressed switched to MSX, Amiga and finally the Windows PC with T3D. Now developing an epic fantasy game: The Master's Eye. Creator of the DoorClass pack and VolumetricFog pack @ richardsgamestudio.com

Recent Threads

  • Windows7 stating T3D is not responding although all is fine
  • SOLVED! Engine hangs with Could not write to socket. Error: WSAEWOULDBLOCK.
  • Unexpected behaviour using compiled shaders and PL lightmaps
  • Shader help
  • Hardware Instancing Problem
    • NextNext Thread
    PrevPrevious Thread
    More from Torque 3D Professional


    Associate Steve Acaster
    [YorkshireRifles.com]
    #1
    11/03/2010 (2:53 pm)
    Are they in a trigger? When objects collide with items, items float up - go stand on one and see. In some Betas, items have triggers as typemasks (or the other way around), I think it's changed in beta3 (or did I put the fix in the code agian ... need more cups of tea to get brain working ...). Look in item cpp and take trigger typemask out of collision. If you can't find it, look in trigger and take item out.

    Richard Marrevee
    R.G.S - Richards Game Studio
    #2
    11/03/2010 (3:41 pm)
    Thanks Steve, you have earned your cup of tea personally I like Earl Grey, taking out the trigger typemask did the trick.

    So for all people who have the same problem:

    In items.cpp at line 42 change this:

    const U32 sServerCollisionMask = (sClientCollisionMask |
                                  TriggerObjectType);

    into this:

    const U32 sServerCollisionMask = (sClientCollisionMask);

    and rebuild.

    Thanks again Steve for the quick answer.

    Associate Steve Acaster
    [YorkshireRifles.com]
    #3
    11/03/2010 (4:18 pm)
    I'm quite partial to the Earl d'Grey myself, but it's copious amounts of Yorkshire Tea until brain starts functioning correctly.

    The issue is still in beta3, not sure whether my workaround has any particular side-effects, or whether triggers can't detect items inside them after it.