Closed cadaver closed 11 years ago
I'm a little conflicted how we should proceed with this. I'd like to get this into our Meshmoon branch and we could do a preview release to test our scenes with it. But I'm a bit concerned that we pull this in, it does not work that great and we need to revert lots of code. Same goes with rex/tundra2 ofc, it might be painful to revert if things don't work out, dunno.
@Stinkfist0 and @cvetan5: Maybe we should make a admino_tundra_ogre1.9
branch based on admino_tundra
and merge this rex/ogre1.9
into it. We could then make the preview releases there without compromising our main working branch.
@cadaver What kind of scenes have you ran with this? Tundra examples or something more complex?
@jonnenauha sounds like a sound strategy.
Tundra examples, Circus, Arcala.
Modifies Tundra to use 1.9 RC1 branch of ogre-safe-nocrashes. Fixes #697.
Additionally, adds texture budgeting code to reduce possibility of crashing due to too much RAM use. When texture budget is exceeded or nearly exceeded, TextureAssets will be loaded at reduced resolution. The reduced resolution loading path excludes possibility to use threaded loading, but threaded loading will be used as long as the budget is not yet in risk of being exceeded. Texture budget is configurable from the command line and from the renderer settings dialog.