These hardware recommendations for FlightGear are based on community feedback, be sure to consult other sources before making serious decisions regarding computer hardware. The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 Īlso, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…) That's what we recommend for everyone who wants to fly and enjoy flying. If ' next' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use 2020.3. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!) Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. In that time the build dependencies, minimum system requirements, performance baseline and basically everything else are going to change (and keep changing). ' next' is work-in-progress: likely 12 or 18 months before it becomes a release. ![]() We tried to communicate this: 2020.3 is the last release that will work on really old hardware: ' next' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU. It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022). In addition, adopting OSG 3.6 means that the experimental CompositeViewer Support can be more widely enabled and tested (it is already enabled by default on next).Īlso, as part of the CompositeViewer effort, Canvas FBO rendering is in the process of being moved out of the scene graph into dedicated viewer-level cameras, which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.įurthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our Canvas Path backend from Shiva to ‘something else’ (see Shiva Alternatives) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL. More importantly: Adopting OSG 3.6+, moving to the OpenGL core profile, WS 3.0, Osm2city buildings, Photoscenery and Compositor shadows & lights. If better to ask these types of questions in forums I will head over there.Note FlightGear is currently undergoing a lot of huge changes. ![]() Relatively small (?) amount of data could be fed to external devices and let the tablet handle graphics/map/GUI/etc. Although, using old tablets / phones seems like a great way to offload some work to another device. Hopefully add more when I find good deals :). Looking for cheap ($50?) card will something like this suffice(not a gamer): MSI GeForce GT 710, 2GB, fan, low profileĬurrently have one 1920x1080 monitor. ![]() But, it only has intel motherboard graphics with shared RAM. graphics card-I found a great deal on HP i5 system 8GB ram, added 240GB NVMe. I can configure most buttons to aircraft controls (gear brakes etc) but some aircraft have special keyboard presses that don’t show in the FG joystick config screen. joystick rudder sensitivity adjustments- my thrustmaster works great except the rudder controls on stick and thrust are way too sensitive. iPad/tablet-what is the best way to get a moving map onto a tablet next to my monitor? I saw reference to ios app that doesn’t exist now, Atlas? IP:8080/gui/map? What’s the latest greatest method?Īlso is there a similar way to put an MFD/PFD / radio/gauges onto tablet? Can I ask bunch of noob questions here? The FG forums don’t seem to have lots of new info my searches hit topics from 2012, 2015.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |