From: <fli...@go...> - 2012-02-10 23:13:54
|
Status: New Owner: ---- Labels: Rendering ReleaseCandidate New issue 658 by stuar...@gmail.com: Effects do not allow fallback to Textures/ from Textures.high http://code.google.com/p/flightgear-bugs/issues/detail?id=658 What steps will reproduce the problem? 1. Delete Textures.high 2. Start FG 3. What is the expected output? What do you see instead? Previously, FG was designed such that Textures.high/ contained higher resolution versions of the textures in the Textures/ directory. Users will lower performance systems could delete the Textures.high directory, and run FG using just the textures in the Textures directory. This was handled by the materials code prefixing texture paths with "Textures.high/", and if that files was not found, trying "Textures". However, the Effects code does not do this, and references a number of textures in the Textures.high directory. We should modify the Effects code to be consistent with the materials.xml handling, then produce lower resolution Effects textures. A workaround would be to move the textures files into the Textures directory. An enhancement would be to make the Texture quality selectable, but that's a feature request rather than a bug fix! What FlightGear version (or GIT date)? 20120210, though I'm highly confident this bug exists in the 2.6.0 RCs, so I'm marking it as such. What operating system and graphics card? Please use labels, text and attachments to provide additional information (avoid expiring external links, e.g. imageshack, pastebin etc). |
From: <fli...@go...> - 2012-02-10 23:18:00
|
Comment #1 on issue 658 by stuar...@gmail.com: Effects do not allow fallback to Textures/ from Textures.high http://code.google.com/p/flightgear-bugs/issues/detail?id=658 In my bug report I forgot to mention what happens currently if you delete Textures.high: FG (reasonably) refuses to run because it can't find a number of textures references by effects. -Stuart |
From: <fli...@go...> - 2012-02-11 09:05:55
|
Updates: Status: Accepted Labels: SimGear Comment #2 on issue 658 by bre...@gmail.com: Effects do not allow fallback to Textures/ from Textures.high http://code.google.com/p/flightgear-bugs/issues/detail?id=658 I have fixed the crash when Textures.high is missing. This was partly due to a bug in simgear, where we resolved an empty filename - which resulted in a directory (fgdata) path. And partly it's a result of an apparent bug in "osgDB::readImageFile", which reports "success" when given a directory (instead of a file) path, though it doesn't return a valid image object - eventually causing a segfault in simgear. This fixes the issue for me: http://www.gitorious.org/fg/simgear/commit/2a0e9d31e10b3a9643f982516259be82a6154134 Switching to low resolution textures for effects still isn't working - but it's possible to run flightgear now anyway. This is also partly related to issue #610 - since all effect textures are always loaded, even when the effects/shaders are completely disabled (also bad for low performance/low memory systems). |
From: <fli...@go...> - 2013-09-16 16:41:40
|
Updates: Labels: -ReleaseCandidate Comment #3 on issue 658 by gijsrooy: Effects do not allow fallback to Textures/ from Textures.high http://code.google.com/p/flightgear-bugs/issues/detail?id=658 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-08-28 10:19:20
|
Updates: Status: Done Comment #4 on issue 658 by clement....@gmail.com: Effects do not allow fallback to Textures/ from Textures.high https://code.google.com/p/flightgear-bugs/issues/detail?id=658 Textures.high/ has been merged into Textures/ so bug is kind of fixed now. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |