Jump to content

View more

Image of the Day

Inventory ! Va falloir trouver une autre couleur pour le cadre D: #AzTroScreenshot #screenshotsaturday https://t.co/PvxhGL7cOH
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

Sign up now

Should rendering geometry and physics geometry separated?

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
5 replies to this topic

#1 lride   Members   


Posted 27 October 2012 - 05:35 PM

I feel like it's better to separate the rendering geometry and physics geometry, but this takes up twice as much memory as using one same geometry for both rendering and physics.
An invisible text.

#2 zacaj   Members   


Posted 27 October 2012 - 05:42 PM

Usually you don't use high resolution graphical assets for the physics, you'd either use really low quality versions or primitive shapes (boxes, cylinders). Either way, you need to store two versions, and the physics one should take up much less space than the rendering version. Plus, that data really isn't that big, compared to even a single texture

#3 ATC   Members   


Posted 27 October 2012 - 07:15 PM

Absolutely... And there should be, in my opinion, a complete separation from visual game entities and logical/physical game entities! For a physics object, for example, the visual representation should do nothing more than mirror the transformations of the logical representation. The logical representation holds the physics hull and all of the calculations are made against it, whereas the visual representation just follows it and gets rendered.
CEO & Lead Developer at ATCWARE™
"Project X-1"; a 100% managed, platform-agnostic game & simulation engine

Please visit our new forums and help us test them and break the ice!

#4 Hodgman   Moderators   


Posted 27 October 2012 - 07:28 PM


Also, your rendering geometry is generally stored in the GPU's RAM and has more attributes, like tex-coords, whereas your physics geometry is generally stored in regular CPU accessible RAM.

#5 superman3275   Members   


Posted 28 October 2012 - 11:17 AM

I separate mine. How I do it is to have a separate Rendering Geometry and Physics Geometry. My Physics Geometry figures out what forces to apply to what (So I'll pass in Collision Points to physics along with some other general information like the type of collision) and then sends the forces to rendering, which will render the objects correctly.
Hodgman is correct too. Rendering concerns the GPU, while your Physics should be doing the calculations, so that's stored in the CPU's RAM, just like he said.

I'm a game programmer and computer science ninja ph34r.png!

Here's my 2D RPG-Ish Platformer Programmed in Python + Pygame, with a Custom Level Editor and Rendering System!


Here's my Custom IDE / Debugger Programmed in Pure Python and Designed from the Ground Up for Programming Education!

Want to ask about Python, Flask, wxPython, Pygame, C++, HTML5, CSS3, Javascript, jQuery, C++, Vimscript, SFML 1.6 / 2.0, or anything else? Recruiting for a game development team and need a passionate programmer? Just want to talk about programming? Email me here:


or Personal-Message me on here smile.png!

#6 MAD UNICORN GAMES   Members   


Posted 30 October 2012 - 09:58 AM

It's better practace to seperate the two, it will provide the most advantages in the long run.
Mad Unicorn Games

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.