0 Favourites

Important 3d boxes suggestions

This forum is currently in read-only mode.
  • Please, can you add these suggestions? I need them and I think they're really useful :

    1) 3D Boxes don't manage collisions. This is annoying, you have to create colliders for everything! There are 2 problems : neither starting the condition from a 3D box nor from the object that must collide with it works :

    When sprite collides with 3dbox = events (nothing happens)

    And, you can't even manage collisions in 3Dbox.

    2) Depth too high by default. The "1" depth we have now should be 5, since we can't use decimal numbers.

    I'm really begging you to add collision support

  • Ah, I thought collisions worked better than that in 3D box. Also I can enter float values in to the depth and Z properties just fine.

    3D Box is coded to use the Back face as the collision mask, which is by default, the one facing away you can't see. So by default you get a box collision detection.

  • I know it uses back face, but damnit, that doesnt work... Maybe the back face must be a sprite? I have it all as alpha 0

  • 1) 3D Boxes don't manage collisions. This is annoying, you have to create colliders for everything! There are 2 problems : neither starting the condition from a 3D box nor from the object that must collide with it works :

    When sprite collides with 3dbox = events (nothing happens)

    And, you can't even manage collisions in 3Dbox.

    2) Depth too high by default. The "1" depth we have now should be 5, since we can't use decimal numbers.

    I'm really begging you to add collision support

    I've been working with the 3D Box quite extensively and I'm afraid I can't recreate any of the problems that you're having.

    I made a test .cap to see if I could test for collision between a sprite and a 3D Box. I gave the sprite 8-Dir movement, and added this event (just as you described:

    Condition: On collision between Sprite and 3D Box:

    Action: Sprite2: Set X to Sprite2.X+10

    Every time I collide Sprite with 3D Box, Sprite2 moves ten pixels to the right. Here's the test .cap to see for yourself:

    http://projectbrimstone.googlepages.com/3dCollisionTest.cap

    This is with the 3D Box's "Solid" attribute turned off.

    Now if you turn on Solid, then I can recreate it. Your sprite and the box won't be able to overlap and register a collision, at least with the default movements. It seems like Construct is checking objects against their Solid attribute before checking the event list, so objects with Solid turned on will be pushed apart before the collision condition occurs.

    As for the Depth, I'm really confused. I can enter in decimal values just fine:

    <img src="http://xs321.xs.to/xs321/07465/3dboxdepth.jpg">

    The Depth and Z values for these boxes were entered into the 3D Box Properties without any problem.

    As for collisions with the 3D Box, you have to keep in mind that the box is just a rendered overlay on top of a 2-dimensional bounding box:

    <img src="http://xs321.xs.to/xs321/07465/3dboxbound.jpg">

    The collisions between the box and other objects occur at the bounding box, regardless of it's Z depth. This means that even if it appears "above" or "below" your sprite, it will still collide at the bounding box.

    --------------------

    EDIT:

    As Ashley said, the "bounding box" is actually a mask of the back face, but the idea is still the same. It's a 2D area that stays on the same Z plane as your sprites.

    --------------------

    As for your back face rendering: The faces are one sided. This is the default with just about every 3D program. The faces won't render unless they are facing toward the display. Try changing the yaw of your box to rotate the back face forward and you will see it.

    I've been meaning to ask if Ashley would put a "Render 2 Sided" option in the textures panel, but he's busy with other stuff right now and I've already asked for a crapload of features for this object <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz" />

  • Perfect description, deadeye <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />

    It is an interesting object and tempting to add new features, but I'll probably stick to bugfixes for now (unless I think of something really cool and easy to do).

  • Yeah, checking my cap it was actually solid. Also, for the float values I can't remember if I used either . or , so I may've been wrong.

  • I can't use float values either, and i've tried both in 84 and 85. When i enter 0.5 (or 0,8) It just deletes the decimal.

  • I can't use float values either, and i've tried both in 84 and 85. When i enter 0.5 (or 0,8) It just deletes the decimal.

    That's... really weird.

    Are you able to change the Z to a decimal value at runtime with the event editor?

  • I know I've mentioned this before and I seem to be the only one having this problem, but inserting a 3D box object makes the Layout editor go completely black. I sent an e-mail about this on August 15th to you Ashley, if you want to go back and look.

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • That's weird about the float values, have you tried seeing what your locale settings are in windows? (ie. maybe windows has set it to something you didnt try, and the property grid is using windows' setting).

    Also the 3D box blanking out the layout is a known bug, I'm still working on that one.

  • I don't really see what "local settings" you are talking about? Like if i've told windows to round all numbers down?

  • No, in different countries they mark up the decimals in different ways. Ie. in Finland we write "3,14" when in number of countries people write "3.14". This might relate to the problem. I'm experiencing the layout-editor-goes-black-bug, so I cannot say anything about the matter itself.

  • But i've tried both. Maybe i could try x'x also, since that is used in some countries, but i don't think it will work.

  • I did some testing and noticed that the decimal numbers are being rounded here too! However, they don't round right away. If I change the number, then click the focus off from the 3d box object and click it back, the numbers have been rounded in the properties bar.

    About the 3d box bug. I wrote this originally to the bug tracker.

    I experience this bug too.

    Some additional information:

    Changing the display settings does solve the problem partially, the

    workspace isn't black any more. But display settings have to be changed when Construct is running, otherwise changing settings doesn't have effect. Here, 60Hz doesn't magically solve the problem, but changing the settings removes black.

    Secondly, after changing the settings, the 3d box itself seems to be

    invisible. Only the "root" is showing up. However, if then more 3d box objects are added, their boxes show up fine.

    Also, after changing the display settings, scrollbars become invisible and, quickly flicker, when user clicks the place where they should be. The "layout editor" and "event editor" tabs are gone too. This problem seems to appear even if there are no 3d boxes at all, just changing the display settings triggers it.

  • The value rounding is really odd, it could be the property grid library we use doing it. Not sure. Will investigate.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)