2016.1.0

[someguy]

I am not color blind. I suspect these lights were implemented on a PC without testing them on a Mac. Typical.

[Hooray]

I am not color blind. I suspect these lights were implemented on a PC without testing them on a Mac. Typical.

The only thing that is "typical" is complaints like your's: Unless you are willing to donate any hardware to the people developing these features, you should be willing to donate your time to help test/troubleshoot new features, especially if you care about them.

By the way, mac support is generally pretty good, in fact, the de-facto main FlightGear core developer (i.e. Zakalawe, in terms of commit activity) is Mac based, which is why many features are getting more testing on Mac/ than on Linux, and especially, Windows.

[Buckaroo]

While I dislike someguy's words about testing, I also believe patronizing replies are not helpful. They can only aggravate while adding nothing.

I can distinguish the color difference in someguy's pic but only barely. And I'm not colorblind in that spectrum.

It's difficult to compare someguy's and Thorsten's images since the positions, hardware and software are different, but someguy's red lights are noticeably desaturated, having a red light RGB value of approximately 255 245 245 and white light RGB of approximately 250 250 250, while Thorsten's shows a red of approximately 215 148 148 and a white approximately 210 210 210. This is hardly a rigorous study, but clearly there is a difference. Thorsten's are in a range of plausible, while someguy's are very washed-out. Anyone suggesting someguy is colorblind or not seeing a valid problem (from someguy's perspective) is not fairly examining the images.

-Buck

[Foxtrot15]

I think that this is quite accurate when compared to real life:

[ausdkunst]

I notice there are some sound clippings/distortions when the plane moves (using rumble.wav in the sounds folder). The wav file itself is fine, so I don't know where the clipping is from.

I have talked to Necolatis and we cannot come up with a solution. Here is the code that is causing the problem:

Code: Select all

<tire-rumble>
      <name>tire-rumble</name>
      <mode>looped</mode>
      <path>Sounds/rumble.wav</path>
      <condition>
        <or>
          <property>/gear/gear[0]/wow</property>
          <property>/gear/gear[1]/wow</property>
          <property>/gear/gear[2]/wow</property>
          <property>/gear/gear[3]/wow</property>
        </or>
      </condition>
      <position>
                <x>0.01</x>
                <y>0.01</y>
                <z>0.01</z>
       </position>
      <volume>
        <property>/velocities/groundspeed-kt</property>
        <factor>.1</factor>
        <max>1</max>
      </volume>
    </tire-rumble>

Removing the <condition></condition> does not make any difference. When the vehicle is standing still, there is no distortion. When I make changes to factor and max to a lower value in the code above, the distortion is still there but volume is lower. If I remove the code, distortion is basically gone. Help would be appreciated. I am using Mac OSX

Edited: Just tested the c172p, it also has sound distortion when it accelerates on the runway

[Parnikkapore]

I do notice,but it is very slight.

Check:What OS is Thorsten_the_shuttle_owner using? Can it be a Mac-only problem?

Check:Which photos have point sprite ON?

[Thorsten]

Can it be a Mac-only problem?

Judging from the screenshot, someguy isn't actually running an up to date version. I've been in discussion with Heiko Schulz about the PAPI lights since the 8th, verified that he has a point and checked color recognition distances, pushed a change on the 10th which addressed the issue to his satisfaction, and since then the lights look as in my screenshot.

Naturally I assumed that a complaint made on the 12th refers to a current fgdata.

The lesson: Pull the latest when there's a problem, see whether this resolves it before posting.

In other matters:

I volunteer to test all my developments on Mac before pushing anything if someone pays a Mac for me, and I volunteer to test all my developments on ATI if someone buys a laptop with an ATI card for me (I consider switching GPUs in my laptop not feasible, and I have no space for a desktop machine). But kindly don't expect me to pay a lot of money so that I can test your hardware.

Also, as TorstenD so aptly put it: In using the Flightgear development branch, you agree to be beta-tester. There's no requirement that things need to be tested on multiple architectures before pushing it, in fact the intention is to push it so that it can be tested on different architectures.

In yet other matters:

The color value of a pixel is a piece of data. How it looks on your screen is likely different how it looks on mine, but once you do a screenshot with a screen grabber (rather than, say, a digicam which images the light from the screen), the color data underneath the pixel is stored, so your screenshot seen on my computer will look exactly like my FG screen for the same pixel color values.

Which is to say, my screen will render a color value of (0.8, 0.7, 0.2) the same regardless of whether it is the output of an OpenGL shader or a value stored in a gif.

[Parnikkapore]

Ok.
Someguy,next time please send to us what version of FlightGear(the whole About dialog in case of nightly/devel builds) you are using in ALL bug reports?

[Parnikkapore]

I think that this is quite accurate when compared to real life:

Where is that from? Your camera,a website,a movie,or FSX?

[Foxtrot15]

Real life, found from google.

[Jet86]

Real life, found from google.

Yes, but it's a photo from real life, not what the pilots themselves are experiencing in real life. The two are very different and FG (I assume) is aiming to simulate what the pilots would see, not what it looks like when you take a photo. Notice for example that the entire inside of that cockpit appears black - I assume you wouldn't want FG cockpits to appear black all the time. The pilots would still be able to see their cockpit even the the photo doesn't show it.

[gsagostinho]

Where is that from? Your camera,a website,a movie,or FSX?

FSX? They wish

[MIG29pilot]

FSX is to RL as banana is to Spitfire.

[legoboyvdlp]

FSX is to FG as Samsung S3560 is to iPhone 6+
Even though I loved my Samsung, I realize it wasn't as good as my mothers iPhone or my current Moto G.

(The latter is a very good phone -- loads better than the Samsung III, but the same price. Was going to get a SIII mini, but it turned out to be TESCO -- NOT unlocked as we thought so we changed it for the Moto when we looked closely at the specs...)

[wkitty42]

Here's what I see at Bergen, from a bit closer than yours:

i see the same as this... it is slightly more difficult to make out the red since the light saturation change... if it could be made specific to certain lights or certain colors of lights, it might help more...