Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

I replied to your other comment in the fauxton engine. :) in general jumping and 3d collision detection are not included in gamemaker, but you can easily add gravity and vertical speed to the z position using variables. For collisions the best route would probably be to generate height maps. 

(1 edit)

Thanks for the reply Gizmo, I didn't notice you created both the camera and Engine.

I was playing around with the Fauxton engine yesterday and really like it but am having trouble incorporating it with my current game.

Also this 3D Camera is super easy to setup and get working but I'm having trouble getting the height maps and texture mapping for walls done.

Do you have any recommendations for creating sprite stacking objects by the way?


PS I would also pay good money for an updated 3d Camera with height mapping.

Hey! So the camera itself does not effect collisions. Height maps might be a bit complicated if you are just starting out. Collisions in general can be quite daunting in programming. Considering also that GM is primarily a 2D program makes this even more daunting of a task. I have covered how to make 3d collisions from scratch if you are interested in learning more Here if you are interested. I would, however, recommend that if you want a program that already includes basic collision functionality, physics, and the like then a program like Unity or Godot would probably be a better fit. :) I am mainly making these assets as a basic template for GM developers to play around with and learn basic 3d concepts. This is not a full 3d engine (hence the 'faux' part of the name). You can also look into ColMesh by thesnidr for a more robust 3d collision system! :)


I hope this helps! :D