• Advertisement


  • Content count

  • Joined

  • Last visited

Community Reputation

1477 Excellent

About xexuxjy

  • Rank

Personal Information

  • Interests
  1. A 3D engine that doesn't render...

    If you need .NET compatibility, I ported Bullet Physics to XNA a while back, (https://github.com/xexuxjy/bullet-xna) , or you can use a c# binding such as Bullet Sharp (https://andrestraks.github.io/BulletSharp/) . It should do pretty much what you need and doesn't expect any form of renderer, though you can attach a simple debug renderer for testing.
  2. you should be able to find a directx implementation of btDebugDrawer , if not it's easy enough to write one (I did it for XNA), as long as you implement the methods in the interface then bullet will do all the drawing for you (not just heightfields)
  3. You'd do something like this :   Menu names : Fee    = &Fee Fi        = F&i Fo         = F&o Fum     = F&um   or whatever you like really - it's just there as a convenience and the ampersand is the shortcut key. You don't have to have it at all which may be easier if menus are dynamic.
  4. It just provides an automatic shortcut key so you can do alt-f (in this case) to open the menu.
  5. Unity Extract assets from an old windows (1998) game

    It's worth looking at the Xentax forums if you haven't already as they have a good list of tools and expertise in reverse engineering formats. I started there when I worked on extracting the assets from Gladius.  No harm in putting your code on github to look at.
  6. What you could also do is when you 'pickup' the grabbed object you could just parent it to the gameObject - would mean that any changes in position , rotation etc from the gameObject would be automatically transferred to the grabbed object.
  7. Not sure if a typo or something, but line 49 looks like you're setting grabbed object to null, rather than testing?   also line 45 you have :   grabbedObject.GetComponent<Rigidbody> ().velocity = Vector3.forward * 50;   when you _probably_ want something like :   grabbedObject.GetComponent<Rigidbody> ().velocity = grabbedObject.transform.forward * 50;   as your update code looks to be already setting the position/rotation of the object.
  8. The handler could still be useful for fine-grained behaviour or unusual circumstances, but yes, culling pairs early makes a huge difference :)
  • Advertisement