jormapaappa1235 wrote in Sat Oct 25, 2014 9:03 pm:Here're spinning tires for ya
https://www.mediafire.com/?pm39aq82gietbdr
Thanks! Pushed to git now.
jormapaappa1235 wrote in Sat Oct 25, 2014 9:03 pm:Here're spinning tires for ya
https://www.mediafire.com/?pm39aq82gietbdr
Soitanen wrote in Mon Oct 27, 2014 8:34 pm:abcaster - what is wrong? Right manipulation with thrust reverser: move throttles to the idle, press "delete" key on the keyboard, wait about 2 seconds, apply thrust.
RAM25 wrote in Mon Nov 10, 2014 8:22 am:Thank you for working on this Boeing 737, does anybody know how the canvas EHSI can be changed into a normal non canvas EHSI, this is because the EHSI canvas is white/blank on the aircraft for me due to having an older computer.
Hooray wrote:please post your hardware specs as per the box at the top of the forum.
It seems that you are lacking some OpenGL support that is required by the new canvas system.
This has been recently reported at least once: viewtopic.php?f=68&t=20887&hilit=canvas+fbo
So please follow up with your exact hardware/software specs, including info from the HELP/ABOUT dialog.
And if you are affected by this, please consider filing a bug report so that we can look into it: http://flightgear-bugs.googlecode.com/
Hooray wrote:could the people getting "white canvases" please get in touch to test a patch ?
Basically, the idea is to check if FBO setup failed and try some more conservative alternatives like pbuffers or ARBs instead.
We can use PIXEL_BUFFER_RTT or PIXEL_BUFFER instead of FRAME_BUFFER_OBJECT: http://lists.openscenegraph.org/piperma ... 04790.html
Given that we're going to use Canvas in more and more placed, including the GUI, it would seem like a good idea to get this sorted obviously.
On the other hand, it is hard to troubleshoot this without being affected by the problem yourself
it's not a new problem: http://www.mail-archive.com/flightgear- ... 20103.html
Hooray wrote:At the moment, this clearly isn't critical - because these cards are obviously very outdated and most FG features cannot expected to work on these types of hardware anyway (and 2.12 has just been released) - on the other hand, once more and more features are ported to make use of the canvas as the common 2D rendering backend (HUD, 2Dpanel, GUI etc), it would be good to know if this could be solved by optoinally using pbuffer rendering instead of FBOs as a fallback - but even just knowing if other hardcoded MFD instruments or the map dialog work, would be interesting.
Thinking along the lines of having a more basic startup mode in FlightGear, analogous to FGPanel/FGCanvas, it would be not that far-fetched that people may be using their old hardware to run multi-screen setups or other master/slave configurations, where just requiring FBOs for all machines may not be the best option.
So, again, if you are affected or know someone who is affected, please ask them to provide feedback, specifically:
- do airliners/jets with the wxradar/agradar, NavDisplay etc work or not ?
- does the map dialog work ?
If in doubt, please just post screen shots
Also, you could ask them to check if support for multiple windows works, because that should also be using offscreen-rendering internally: http://wiki.flightgear.org/Howto:Config ... ew_windows
PS: @TheTom: If in doubt, I'd suggest to get in touch with FredB, according to the devel list, he's using pbuffer fallback mode for the rembrandt/deferred rendering mode to get offscreen rendering support.
RAM25 wrote in Wed Nov 12, 2014 12:52 pm:I apologize hooray for not being very clear about my situation..i will try to explain it more clearly: i have turned GENERIC off at custom shader options (that is the reason for the white screen), when i turn it on i do get the canvas perfectly working but my frames drop from 25(where i have limited them) to 8-10..so you can understand that it is very difficult to fly like that, if i am not wrong the only realistic solution for me is having a better computer or flying non canvas ND aircraft.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Windows XP 32bit
Intel Core 2CPU T7200 @ 2.00GHz 997MHz, 2.00GB of RAM
ATI Mobility RADEON X1300 512MB
Users browsing this forum: No registered users and 10 guests