Irrlicht 2.0 - What's in store for the future!

Discuss about anything related to the Irrlicht Engine, or read announcements about any significant features or usage changes.
Granyte
Posts: 850
Joined: Tue Jan 25, 2011 11:07 pm
Contact:

Re: Irrlicht 2.0 - What's in store for the future!

Post by Granyte »

DX11 is almost completely fixed the only thing remaining is the text scenenode is depth writing for no good reason.

But as i told befor the patch is already massive because the whole material system was poorly done and will probably only get worst when i fix the textscenenode
lumirion
Posts: 79
Joined: Tue Sep 13, 2011 7:35 am

Re: Irrlicht 2.0 - What's in store for the future!

Post by lumirion »

In potential vulkan support and/or dx11 what about using a render target that uses per-pixel linked lists of fragments to provide order independent transparency by default. Any GPUs with over 100mb ram should handle it just fine.
hendu
Posts: 2600
Joined: Sat Dec 18, 2010 12:53 pm

Re: Irrlicht 2.0 - What's in store for the future!

Post by hendu »

Radeon R200 series, introduced in 2001, had 128mb VRAM cards.
devsh
Competition winner
Posts: 2057
Joined: Tue Dec 09, 2008 6:00 pm
Location: UK
Contact:

Re: Irrlicht 2.0 - What's in store for the future!

Post by devsh »

In potential vulkan support and/or dx11 what about using a render target that uses per-pixel linked lists of fragments to provide order independent transparency by default. Any GPUs with over 100mb ram should handle it just fine.
Thats too high-level, I think its something the developer should decide or at least have very fine grained access to

Remember, memory is not primary concern, performance is.
lumirion
Posts: 79
Joined: Tue Sep 13, 2011 7:35 am

Re: Irrlicht 2.0 - What's in store for the future!

Post by lumirion »

what about replacing type enumerations with some sort of type registration? That way deriving new extensions from the defaults would not require modifications to the Irrlicht source and the engine could dynamically accept new types. The cost would be slight over head of storing the type along with an int identifier.

Code: Select all

 
RegisterableTypeEnum
{
     string type;
     int ID;
     operator int*() {return ID;}
}
 
kornwaretm
Competition winner
Posts: 189
Joined: Tue Oct 16, 2007 3:53 am
Location: Indonesia
Contact:

Re: Irrlicht 2.0 - What's in store for the future!

Post by kornwaretm »

how about scalable timer. lets say device->setGlobalAnimatorTimeScale(0.5); and all animation speed scaled down to half speed. device->setGlobalAnimatorTimeScale(0.0); and all animation paused, particle emiter stop emitting etc.
CuteAlien
Admin
Posts: 9628
Joined: Mon Mar 06, 2006 2:25 pm
Location: Tübingen, Germany
Contact:

Re: Irrlicht 2.0 - What's in store for the future!

Post by CuteAlien »

@kornwaretm: ITimer::setSpeed should do that.
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
kornwaretm
Competition winner
Posts: 189
Joined: Tue Oct 16, 2007 3:53 am
Location: Indonesia
Contact:

Re: Irrlicht 2.0 - What's in store for the future!

Post by kornwaretm »

ow it is already exist this whole time :oops:
Post Reply