UDAfy
Re: UDAfy
Unfortunately, using something like that would require pretty much ground-up rewrites of all the core parts of the engine. The engine is currently focused on CPU architectures. Moving to a GPU, even if it could somehow use all of the existing code unchanged (which it cannot 
), would result in bad performance due extremely poor utilization of the hardware.
I've played with the idea of some kind of limited functionality GPU acceleration in the past, but it's currently pretty low on the priority list. My personal projects don't really have any GPU cycles to spare
), would result in bad performance due extremely poor utilization of the hardware.I've played with the idea of some kind of limited functionality GPU acceleration in the past, but it's currently pretty low on the priority list. My personal projects don't really have any GPU cycles to spare
Re: UDAfy
Thanks.
My concern is my current project will entail as many as 60 3D objects on the screen and I am concerned about performance regarded collisions. I amusing irrlicht with the lime wrapper, and would like to use BEPU. Any indication if it will handle what I am asking. I just do not want any lag o freezes in the display.
My concern is my current project will entail as many as 60 3D objects on the screen and I am concerned about performance regarded collisions. I amusing irrlicht with the lime wrapper, and would like to use BEPU. Any indication if it will handle what I am asking. I just do not want any lag o freezes in the display.
Re: UDAfy
My mainstream desktop PC can handle thousands of objects in real time. 60 objects, even on a modern phone, should be totally fine.
If you run into performance problems with that few objects, shenanigans are very likely afoot.
If you run into performance problems with that few objects, shenanigans are very likely afoot.