On 28 Jan 2005 at 11:02, Curtis L. Olson wrote:

> AnthonyL wrote:
> 
> >I experience a number of problems, some are new and some linger on
> >from v0.9.6.  I have simply upgraded to 9.8 over the top of 9.6.
> >
> >9.8 FG doesn't give me a full screen.  I run on a laptop set at 1400
> >x 1050.  It now changes my WHOLE windows screen to (guessing)
> >800x600.   It doesn't matter whether I have Game mode checked or not.
> > Previously Game mode would give me a FULL screen, and unchecked it
> >would leave my Windows screen at full size but run FG in a smaller
> >window.
> >  
> >
> 
> There is a 0.9.8a windows build now available on our web site. 
> Frederic redid the launcher interface a bit so it's easier to select
> the resolution FG will go to when you enter full screen.  If you want
> a "nonstandard" resolution, I think you can still enter it (i.e.
> 1400x1050 all run together with the x) in the "Advanced" settings
> section.
> 

/gripmode
Thanks but that took some finding.  Having only just downloaded 0.9.8 I 
wasn't sure which was "our web site" so I looked at yours and then on 
flightgear (carefully checking the version change log).  It was only by 
accident that I noticed the url had changed as I passed my mouse of one 
of the mirrors.  Could someone add a simple line to the change log to 
make it clearer for us Window users?
/end gripmode

ok well I've put geometry=1400x1050 in C:\Program 
Files\FlightGear\data\system.fgfsrc  and I now get the program to run full 
screen.  But what I can't get to happen is for my screen to stay at its 
native 1400x1050 and for flightgear either to run full screen or as a 
window as used to occur in the .0.9.6.  If I change the geometry that 
changes my screen size and flightgear always loads full screen size 
regardless of the game mode setting.

I'm a windows user so simple answers please :)

Many thanks



_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to