Bug 485525 - FlightGear vertical compressed
Summary: FlightGear vertical compressed
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: FlightGear
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Fabrice Bellet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-13 22:20 UTC by John Ellson
Modified: 2009-02-15 16:46 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-02-15 16:46:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Opening window (84.82 KB, image/png)
2009-02-13 22:20 UTC, John Ellson
no flags Details

Description John Ellson 2009-02-13 22:20:52 UTC
Created attachment 331880 [details]
Opening window

Description of problem:
For about the last month or so, since some update, the y-axis of the FlightGear openGL window has been compressed to about 30% of its correct value.  The lower 70% of the window is just grey.  This initial aircraft position seems to be subterrainian.

x86_64, NVidia GeForce 7800 GT, twinview, 2x1920x1200 Lcds 

Version-Release number of selected component (if applicable):
FlightGear-1.9.1-1.fc11.x86_64
SimGear-1.9.1-1.fc11.x86_64
NVIDIA-Linux-x86_64-180.29

How reproducible:
100%

Steps to Reproduce:
1. fgfs
2.
3.
  
Actual results:
see attached

Expected results:
proper Y scaling

Additional info:

Comment 1 Fabrice Bellet 2009-02-14 14:28:22 UTC
Yes, I've seen this problem too. This is caused by the version of OpenSceneGraph used in rawhide currently (2.6.0). Since version 2.8.0 has been released last week, I'll rebuild against this new version as soon as it'll be available in rawhide.

Comment 2 Fabrice Bellet 2009-02-15 13:34:50 UTC
SimGear-1.9.1-3.fc11 and FlightGear-1.9.1-2.fc11 have been rebuilt with OpenSceneGraph-2.8.0. Can you retest with these new packages ?

Comment 3 John Ellson 2009-02-15 13:59:38 UTC
FlightGear-1.9.1-2.fc11.x86_64 is looking much better.   Thanks.


Note You need to log in before you can comment on or make changes to this bug.