[Flightgear-devel] PAPI/runway lights size - Rembrandt
Hi there, the size of the PAPI lights has been bothering me for quite some time. It looks just too big for me. Going through the simgear git history I found out quickly that it was changed by commit 1dfde64ac2e6ed0a Use bigger point sprites for airport lighting. I reduced the size locally to 14 for the PAPI and 8 for the runway lights. All was good until I started FG with Rembrandt enabled. Then the PAPI lights do not show up during daytime now. This looks like a Rembrandt bug to me. I think the sizes should be reduced for the non-Rembrandt users as this is still our main audience. Fred, do you have a clue what is going on? Cheers, Chris -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PAPI/runway lights size - Rembrandt
Hello, the size of the PAPI lights has been bothering me for quite some time. It looks just too big for me. Going through the simgear git history I found out quickly that it was changed by commit 1dfde64ac2e6ed0a Use bigger point sprites for airport lighting. Real life PAPI and runway lights have very high intensity and can be distinguish from air easily but the raster display has limitation and can not display that high intensity. Usually FFS uses caligraphic (not using raster but pinpoint to have high intensity) but we can't use that method. Only thing we can do is larger the size. It's better than not to be seen. I like it. I reduced the size locally to 14 for the PAPI and 8 for the runway lights. All was good until I started FG with Rembrandt enabled. Then the PAPI lights do not show up during daytime now. This looks like a Rembrandt bug to me. I think the sizes should be reduced for the non-Rembrandt users as this is still our main audience. Fred, do you have a clue what is going on? Yes, this might be rembrandt issue. Regards, Hyde -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FGx 2.8.0rc1 for OSX
Hi all Just announced at forums that a FGx 2.8.0rc1 rolled out. It contains latest sg/fg/fgdata (with a own fgdata base package with a slightly different aircraft selection) and current fgcom. http://downloads.fgx.ch/OSX/FGx-2.8.0rc1.zip We use jenkins now to build and deploy FGx, an equal windows version will follow the next days. You will always find a weekly updated FGx trunk in downloads, besides of the releases following fgfs release numbers. Trunk or master deployment is based on openscenegraph/sg/fg/fgdata/fgcom/fgx next branches. Bug reporting and feature requests for FGx still at http://code.google.com/p/fgx/ Thanks for having FlightGear ! Cheers, Yves -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PAPI/runway lights size - Rembrandt
Am 16.07.2012 16:22, schrieb Christian Schmitt: the size of the PAPI lights has been bothering me for quite some time. It looks just too big for me. Going through the simgear git history I found out quickly that it was changed by commit 1dfde64ac2e6ed0a Use bigger point sprites for airport lighting. I reduced the size locally to 14 for the PAPI and 8 for the runway lights. All was good until I started FG with Rembrandt enabled. Then the PAPI lights do not show up during daytime now. This looks like a Rembrandt bug to me. I think the sizes should be reduced for the non-Rembrandt users as this is still our main audience. Fred, do you have a clue what is going on? To me it appears the lights aren't scaled with the screen size, unlike the rest of the scenery. So they appear really huge especially on small screens (while on large screens, they might even appear too small). http://code.google.com/p/flightgear-bugs/issues/detail?id=716 cheers, Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 2.8-RC3 Startup Failure for Unknown Reasons
ORIGINAL BUG REPORT at Forums here: http://flightgear.org/forums/viewtopic.php?f=68t=16940start=15 and FG Bug Report Issue 807. Good evening, I attempted to start FG's new release candidates, but met unexpected startup problems that the guys in the FG Forum could not solve. I was wondering if y'all here could help me figure out what's wrong? Thank you so much, beforehand! I experienced this problem with FG versions 2.8.0 Release Candidates 2 and 3 on a Windows Vista 64bit SP1 with 4GB RAM, Pentium Dual-Core CPU (2.50GHz) and ATI Radeon HD 5450 GPU. This is mostly copied from my FG Bug Tracker report: STEPS FOR ISSUE REPRODUCTION (no precedents to current issue reported) 1. Install FG ver 2.8.0.RC2 or RC3 on Windows. (User uses Vista 64bit with 4GB RAM, but 32bit version is force-installed. Computer has run FG successfully in the past up to ver 2.6) 2. Start with any aircraft at any airport, with the following parameters: C:\Program Files (x86)\FlightGear\bin\Win32\fgfs.exe --fg-root=C:\Program Files (x86)\FlightGear\data --fg-scenery=C:\Program Files (x86)\FlightGear\data\Scenery;C:\Program Files (x86)\FlightGear\scenery;C:\Program Files (x86)\FlightGear\terrasync --aircraft=777-200 --control=joystick --disable-random-objects --prop:/sim/rendering/random-vegetation=false --enable-hud --enable-anti-alias-hud --disable-hud-3d --enable-distance-attenuation --disable-specular-highlight --enable-ai-models --disable-ai-traffic --in-air --disable-real-weather-fetch --disable-clouds --enable-clouds3d --bpp=32 --timeofday=noon --prop:bool:/sim/rendering/random-buildings=false --log-level=warn 3. Run FGrun and hope FlightGear launches successfully. FG HAS been uninstalled and reinstalled at least three times, but all attempts lead to the same result. EXPECTED Outcome: FlightGear starts up with selected aircraft at selected airport. ACTUAL Outcome: FlightGear fails and crashes when splash screen starts to fade away. CONSOLE OUTPUT: Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr aft Failed to create beacon for unknown runway 'KONT 26L OM'. Failed to create beacon for unknown runway 'KONT 26R OM'. Failed to create beacon for unknown runway 'KSAV 01 OM'. Failed to create beacon for unknown runway 'KSAV 10 OM'. Failed to create beacon for unknown runway 'PAYA 11 OM'. Failed to create beacon for unknown runway 'WARQ 26 OM'. Failed to create beacon for unknown runway 'WARR 10 OM'. Failed to create beacon for unknown runway 'ZULS 27R OM'. Failed to create beacon for unknown runway 'EDDB 07 MM'. Failed to create beacon for unknown runway 'EDDB 25 MM'. Failed to create beacon for unknown runway 'KIAD 01C MM'. Failed to create beacon for unknown runway 'KONT 08L MM'. Failed to create beacon for unknown runway 'KONT 26L MM'. Failed to create beacon for unknown runway 'KONT 26R MM'. Failed to create beacon for unknown runway 'KSAV 01 MM'. Failed to create beacon for unknown runway 'KSAV 10 MM'. Failed to create beacon for unknown runway 'PAED 06 MM'. Failed to create beacon for unknown runway 'PAYA 11 MM'. Failed to create beacon for unknown runway 'WADD 27 MM'. Failed to create beacon for unknown runway 'WALL 25 MM'. Failed to create beacon for unknown runway 'WAOO 10 MM'. Failed to create beacon for unknown runway 'WAOP 34 MM'. Failed to create beacon for unknown runway 'WARJ 09 MM'. Failed to create beacon for unknown runway 'WARQ 26 MM'. Failed to create beacon for unknown runway 'WARR 10 MM'. Failed to create beacon for unknown runway 'WIDD 04 MM'. Failed to create beacon for unknown runway 'WIHH 24 MM'. Failed to create beacon for unknown runway 'KIAD 19C IM'. Failed to create beacon for unknown runway 'KONT 26L IM'. Skipping bad material entry params Dir::children: FindFirstFile failed:C:/Program Files (x86)/FlightGear/data/Aircr aft/777/gui/dialogs Failed to tie property /environment/attention to object methods Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam ed to MetarController:layer:wind-from-heading-deg_0 Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam ed to MetarController:layer:wind-from-heading-deg_1 Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam ed to MetarController:layer:wind-from-heading-deg_2 Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam ed to MetarController:layer:wind-from-heading-deg_3 Duplicate autopilot component MetarController:layer:wind-from-heading-deg, renam ed to MetarController:layer:wind-from-heading-deg_4 Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me tarController:layer:wind-speed-kt_0 Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me tarController:layer:wind-speed-kt_1 Duplicate autopilot component MetarController:layer:wind-speed-kt, renamed to Me tarController:layer:wind-speed-kt_2
