Board index FlightGear Support Graphics

no VASI/PAPI with flightgear 3.4

Graphics issues like: bad framerates, weird colors, OpenGL errors etc. Bad graphics ar usually the result of bad graphics cards or drivers.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?
- does the problem occur with any aircraft, at any airport?
- is there any output printed to the console (black window)?
- copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher).
- please upload a screenshot of the problem.

If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests).
To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you are seeing corrupted/broken textures, please see this article.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

no VASI/PAPI with flightgear 3.4

Postby Curtis » Thu Feb 19, 2015 4:07 pm

Hello,

I notice that VASI/PAPI are not displayed with flightgear 3.4, it's not normal because with flightgear 3.2 I could see VASI/PAPI on the left side of the runway ( airport LFSN )

I use archlinux 64 bits, ati radeon HD4650 pcie, cpu intel pentium dual core 3.33 Ghz, 4 Gb ram

and mesa 10.4.4

something seems wrong in flightgear 3.4 about the display of VASI/PAPI,

for example with flightgear 3.2 and LFSN airport I can see VASI/PAPI :

Image

but with flightgear 3.4 and the same airport there is no VASI/PAPI :

Image
Curtis
 
Posts: 105
Joined: Wed Jun 17, 2009 3:09 pm
OS: archlinux 64 bits

Re: no VASI/PAPI with flightgear 3.4

Postby stuart » Thu Feb 19, 2015 4:43 pm

Hi Curtis,

That's a regression which was fixed in origin/next, but not included in the release branch. Thanks for reporting it - I'll flag it on the -devel list.

-Stuart
G-MWLX
User avatar
stuart
Moderator
 
Posts: 1469
Joined: Wed Nov 29, 2006 9:56 am
Location: Edinburgh
Callsign: G-MWLX

Re: no VASI/PAPI with flightgear 3.4

Postby Curtis » Thu Feb 19, 2015 7:54 pm

Hello Stuart,

Do you know where I can find the git commit who solves this bug ?

maybe I can create a patch for flightgear 3.4
Curtis
 
Posts: 105
Joined: Wed Jun 17, 2009 3:09 pm
OS: archlinux 64 bits

Re: no VASI/PAPI with flightgear 3.4

Postby someguy » Thu Feb 19, 2015 8:27 pm

While you're at it, note the absence of numbers in the 3.4 HUD:

Image

https://www.dropbox.com/s/e1pgvnsl7o5vj ... s.jpg?dl=0
User avatar
someguy
 
Posts: 1653
Joined: Tue Nov 25, 2008 5:54 am
Location: USA
Version: 2016.2.1
OS: Mac OS X 10.11

Re: no VASI/PAPI with flightgear 3.4

Postby spencer.james » Wed Feb 25, 2015 4:41 pm

Hi everyone

I have noticed this as well. Any suggestions on what I can do to fix it (as my landing at night has got a bit shaky again!)

Thanks
Spencer
ErinAir

Project Ireland - Republic of and Northern Ireland Airports - http://forum.flightgear.org/viewtopic.php?f=5&t=26292 - Coming soon
spencer.james
 
Posts: 52
Joined: Thu Oct 30, 2014 6:40 pm
Callsign: ErinAir
Version: 3.4
OS: Windows 7

Re: no VASI/PAPI with flightgear 3.4

Postby elgaton » Wed Feb 25, 2015 8:28 pm

If you can compile FlightGear from source, grab the latest version - the fix was backported to the release/3.4.0 branch - and compile the program again.

If not, you can use the old FlightGear 3.2, get a (potentially unstable!) nightly build from the build server or wait for the next release - there was some talk on the development mailing list about publishing a 3.4.1 bugfix package to address this problem, but, as I'm not heavily involved in core development, I can not guarantee it will be released.
NIATCA 2nd admin, regular ATC at LIPX and creator of the LIPX custom scenery
elgaton
 
Posts: 1107
Joined: Tue Mar 19, 2013 4:58 pm
Callsign: I-ELGA/LIPX_TW
Version: Git
OS: Windows + Arch Linux

Re: no VASI/PAPI with flightgear 3.4

Postby jsb » Wed Feb 25, 2015 11:08 pm

I believe the community would highly appreciate an official bugfix release for this important feature - preferrably far far below the 1GB size of a normal release.
jsb
 
Posts: 219
Joined: Sat Oct 25, 2014 8:17 pm
Location: Hamburg, Germany
Callsign: D-JSB
Version: next
OS: Win7/Linux

Re: no VASI/PAPI with flightgear 3.4

Postby Bug Bunny » Thu Feb 26, 2015 12:24 am

I have this problem too on a FG 3.4 / Win7sp1 / ATI Rad 6870
Bug Bunny
 
Posts: 41
Joined: Tue Feb 24, 2015 4:00 pm
Location: Ukraine
Version: 3.6.0RC
OS: Windows 7

Re: no VASI/PAPI with flightgear 3.4

Postby spencer.james » Thu Feb 26, 2015 11:40 pm

jsb wrote in Wed Feb 25, 2015 11:08 pm:I believe the community would highly appreciate an official bugfix release for this important feature - preferrably far far below the 1GB size of a normal release.


Indeed, if it can be easily fixed then that would be brilliant!
ErinAir

Project Ireland - Republic of and Northern Ireland Airports - http://forum.flightgear.org/viewtopic.php?f=5&t=26292 - Coming soon
spencer.james
 
Posts: 52
Joined: Thu Oct 30, 2014 6:40 pm
Callsign: ErinAir
Version: 3.4
OS: Windows 7

Re: no VASI/PAPI with flightgear 3.4

Postby zlsa » Fri Feb 27, 2015 1:26 am

Not to belittle the efforts of the core devs who use their valuable time to push out a project for which they've received no pay...

but IMO this should have been caught before release.
zlsa
 
Posts: 145
Joined: Fri Feb 14, 2014 2:29 am
Callsign: N275A
Version: 3.5 git
OS: Linux

Re: no VASI/PAPI with flightgear 3.4

Postby Thorsten » Fri Feb 27, 2015 6:24 am

but IMO this should have been caught before release.


It was caused by a last minute decision to add a memory-saving patch to the release which broke the lights, followed by an oversight in which the patch to fix this went to next only. In essence, an attempt to do something good...

I understand there is a bugfix release in the making, fixing the light as well as unusual memory usage of the route manager.

In general, my impression is that there's a trend in the community not to use the release candidates to test and report in the expectation that the release will then by (magically?) bug free, so once the release comes out effectively many bugs which should have been caught by release candidate testing are reported, which prompts the need for a minor version release. The light bug mentioned above is rather exceptional in that respect.
Thorsten
 
Posts: 10982
Joined: Mon Nov 02, 2009 8:33 am

Re: no VASI/PAPI with flightgear 3.4

Postby sanhozay » Fri Feb 27, 2015 12:15 pm

It's true, as a user community we don't seem to do a very good job of testing release candidates. I know the scale is different but if you look at something like Ubuntu, there's a whole army of end users testing the next release and the subforum created for that purpose is highly active. What's impressive about what they have done over there is that people are testing for testing's sake -- as in trying to break the new features rather than just have the latest and possibly greatest version.

Our release candidate subforum is quiet, even considering the smaller user base of Flightgear: viewforum.php?f=68

I do suspect that more end users run the latest Git version than install release candidates for testing.

I think it would help the limited number of testers if we were given more hints about what's actively changing. It does happen -- you show off your new stuff on the forum and so does Torsten -- but these things get a bit lost in newsletters, buried in forum threads, on the mailing list and wiki. What do you think of the idea of having a subforum in Release Candidates for "Next" with a locked, sticky thread where developers list out areas that need some testing focus? Effectively a living set of release notes that builds from one feature freeze to the next. When the feature freeze happens, "Next" becomes 3.6 RC and the basis of the release notes for 3.6 RC are sitting there at the top of the subforum. Users can test and when we come to a reasonable conclusion that we have a bug, post it on the devel mailing list.
sanhozay
 
Posts: 1207
Joined: Thu Dec 26, 2013 11:57 am
Location: EGNM
Callsign: G-SHOZ
Version: Git
OS: Ubuntu 16.04

Re: no VASI/PAPI with flightgear 3.4

Postby Thorsten » Fri Feb 27, 2015 4:04 pm

What do you think of the idea of having a subforum in Release Candidates for "Next" with a locked, sticky thread where developers list out areas that need some testing focus?


If it helps, I'd certainly be willing to do that.

Not sure whether I would know what requires testing focus though... Many bugs are actually not in new features which get a lot of testing before they are committed, but caused by 'innocent' maintenance things (so the missing light - wasn't broken by maintenance on lights - that would have been tested before committing - but by restructuring terrain info storage).

So such a list would only be useful if it's finite - once I list every subsystem I touched with a commit, it ceases to be helpful. But to keep it finite might be problematic.

I think what is important to realize is that most developers probably have rather different use and test profiles of FG. I do 90% of my testing with AW and ALS on (simply because that's what I develop), shader quality at highest and check breakage of other rendering frameworks only comparatively briefly in the remaining time. Usually I just do a few minutes with the ufo at some benchmark locations (Caribbean, French Alps, South Africa, US Southwest) - I do 30+ minute flights in aircraft except the ufo very rarely and never any hour long airliner flights.

Obviously, testers which have a different use profile are more valuable then.

In general, I think I have the advantage that rendering tends to produce very visual bugs, so I tend to get notice soon. Though the disadvantage that they're highly architecture dependent, so knowing about a bug might still not help much.
Thorsten
 
Posts: 10982
Joined: Mon Nov 02, 2009 8:33 am

Re: no VASI/PAPI with flightgear 3.4

Postby zlsa » Fri Feb 27, 2015 4:16 pm

I didn't even know there was a release candidate. Do I have to download the full 1GB+ of FGdata for that as well? I'll certainly be testing it next time if I have a chance.
zlsa
 
Posts: 145
Joined: Fri Feb 14, 2014 2:29 am
Callsign: N275A
Version: 3.5 git
OS: Linux

Re: no VASI/PAPI with flightgear 3.4

Postby Curtis » Mon Mar 02, 2015 6:14 pm

zlsa wrote in Fri Feb 27, 2015 1:26 am:but IMO this should have been caught before release.


I think also this kind of bug should have been detected by the developpers by doing a kind of "checklist", in order to be sure that some basic features are still Ok ( lights during night flight, VASI/PAPI, sound, shaders, weather for example ),

another way :

- writting unit tests for each modules of flightgear, the developer by launching these automatic tests will be sure that there is no regression/bug ( at least in a module, a function, a class )

http://en.wikipedia.org/wiki/Unit_testing

and then make some integration tests before the final validation :

http://en.wikipedia.org/wiki/Integration_testing

flightgear uses C++ for his source code, cppunit can be a good framework for unit testing :

http://sourceforge.net/projects/cppunit/
Curtis
 
Posts: 105
Joined: Wed Jun 17, 2009 3:09 pm
OS: archlinux 64 bits

Next

Return to Graphics

Who is online

Users browsing this forum: MSN [Bot] and 1 guest