Hi Dave,
same here. But it is ok, if I start with 4:3 window and maximize it when
fg runs (my normal start procedure).
Maik
dave perry schrieb am 06.01.2008 05:08:
Maik Justus wrote:
Hi,
Maik Justus schrieb am 26.12.2007 20:38:
Hi Syd,
what's about an algorithm, which checks
Hi Dave,
I checked again, if I start with a 4:3 resolution the gages remain round
when maximizing to 1680*1050 by clicking the square in the upper right
corner. I am running win xp, compiled on msvc-express. The same, if I
start with --resolution=800x600. If I start with --resolution=1680x1050
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Maik Justus wrote:
Hi Arvid,
AnMaster schrieb am 04.01.2008 23:13:
My resoltion is 1400x1280,
not 4:3 nor 16:9 ?
20 1400x1280 TFT. I got no idea what format it is, but the monitor works well
for me.
The screen area of the monitor is about 30.5
Hi Arvid,
maybe your pixels are not of square size? If yes: can you look to
/sim/current-view/aspect-ratio-multiplier? If it is not 1, then we need
to scale 47.5 with this factor (to get a larger fov).
Thank you very much,
Maik
AnMaster schrieb am 05.01.2008 11:40:
-BEGIN PGP SIGNED
Hi Arvid,
AnMaster schrieb am 05.01.2008 14:48:
it is 1400x1050.
ok (4:3). Try 58.6.
Thank you,
Maik
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
Maik Justus wrote:
Hi,
Maik Justus schrieb am 26.12.2007 20:38:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and
sets fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 =
(4/3) / (16/9) )
Maik
P.S.:
for non-physicists:
(55 /
Hi,
Maik Justus schrieb am 26.12.2007 20:38:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
Maik
P.S.:
for non-physicists:
(55 / 73,333 = (4/3)
On Fri, 04 Jan 2008 21:01:15 +0100
Maik Justus [EMAIL PROTECTED] wrote:
Hi,
Maik Justus schrieb am 26.12.2007 20:38:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
How does this work with windowed mode (that I always use, as maximized window,
still showing the 64
pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3,
but the window isn't.
Regards,
Arvid Norlander
Maik Justus wrote:
AnMaster wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
How does this work with windowed mode (that I always use, as
maximized window, still showing the 64 pixels high KDE taskbar at the
bottom, and window edges). My monitor is 4:3, but the window isn't.
AnMaster, same problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My resoltion is 1400x1280, but you also have to consider window borders. Not
sure how large they
are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for
example), were in
maximized window. Should be possible to calculate from
Hi Arvid,
AnMaster schrieb am 04.01.2008 23:13:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My resoltion is 1400x1280,
not 4:3 nor 16:9 ?
but you also have to consider window borders. Not sure how large they
are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for
Hi All
I love the new changes Stuart did, the reset button is great.
Is there still anyway to add a text field?
EG When I try to adjust fwd/back.
Move the slider 1/2 a degree and you move 1m is distance.
Anyway to fine tune that. Where you can enter the value
1.005m instead of 1.004m ???
Thanks
I Don't know if it my changes
I simply applies Stuarts and Syd
When I adjust Up/Down
The dial rotates but the value always stays the same 1.84m (using 737-300) ??
Thanks
Barry
Barry Fawthrop wrote:
Hi All
I love the new changes Stuart did, the reset button is great.
Is there still anyway
On Fri, 28 Dec 2007 08:11:05 -0500
Barry Fawthrop [EMAIL PROTECTED] wrote:
I Don't know if it my changes
I simply applies Stuarts and Syd
When I adjust Up/Down
The dial rotates but the value always stays the same 1.84m (using 737-300) ??
Thanks
Barry
Barry Fawthrop wrote:
Hi All
On mer 26 décembre 2007, SydSandy wrote:
Hi everyone , and merry christmas...
I'm busy playing with my new 1440x900 flat - panel monitor ...wow what a
difference in FG ! Which gave me an idea maybe others would appreciate
too
Before this , a default field 0f view of 55 was about right ...
Sounds very smart.
I haven't gotten my giant flatscreen yet.
:-)
Rather than modifying my set files and possibly ruining someone else's
setup ... maybe a field-of-view slider in the view options would be an
idea ?
Im poking around in view.xml now but might take a bit to figure it out
:)
Hi All
I would Agree and like to suggest that the View Distance also have an edit
field to type in the number.
Trying to move the dials is far to excessive for a minute change.
Thanks
Barry
gerard robin wrote:
On mer 26 décembre 2007, SydSandy wrote:
Hi everyone , and merry christmas...
I'm
On Wed, 26 Dec 2007 18:50:26 +0100
alexis bory [EMAIL PROTECTED] wrote:
gerard robin wrote:
We have the x and X key to tune it
Yes, but I (and probably others) use often view.resetView(), which is
triggered by a button on my joystick, to recenter the view and in this
case using x/X
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
Maik
P.S.:
for non-physicists:
(55 / 73,333 = (4/3) / (16/9) )
SydSandy schrieb am 26.12.2007
On Wed, 26 Dec 2007 20:38:22 +0100
Maik Justus [EMAIL PROTECTED] wrote:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
Maik
P.S.:
for non-physicists:
(55 /
On mer 26 décembre 2007, SydSandy wrote:
On Wed, 26 Dec 2007 20:38:22 +0100
Maik Justus [EMAIL PROTECTED] wrote:
Hi Syd,
what's about an algorithm, which checks the ratio of the screen and sets
fow to 55 for 4:3 screens and 70 for 16:9 screens? (55 / 70 = (4/3) /
(16/9) )
Maik
On mer 26 décembre 2007, SydSandy wrote:
Hi all...
Just had another thought ...
Maybe a simpler idea would be to have the sim/view/config/field-of-view
property added to the autosave function ? This way it could be set per
aircraft
but that still means editing the properties in the
On Wed, 26 Dec 2007 21:19:30 +0100
gerard robin [EMAIL PROTECTED] wrote:
On mer 26 décembre 2007, SydSandy wrote:
Hi all...
Just had another thought ...
Maybe a simpler idea would be to have the sim/view/config/field-of-view
property added to the autosave function ? This way it could
--- SydSandy [EMAIL PROTECTED] wrote:
On mer 26 décembre 2007, SydSandy wrote:
Hi all...
Just had another thought ...
Maybe a simpler idea would be to have the sim/view/config/field-of-view
property added to the autosave function ? This way it could be set per
aircraft
On Wed, 26 Dec 2007 21:49:19 + (GMT)
Stuart Buchanan [EMAIL PROTECTED] wrote:
--- SydSandy [EMAIL PROTECTED] wrote:
On mer 26 décembre 2007, SydSandy wrote:
Hi all...
Just had another thought ...
Maybe a simpler idea would be to have the sim/view/config/field-of-view
On Wed, 26 Dec 2007 21:49:19 + (GMT)
Stuart Buchanan [EMAIL PROTECTED] wrote:
--- SydSandy [EMAIL PROTECTED] wrote:
On mer 26 décembre 2007, SydSandy wrote:
Hi all...
Just had another thought ...
Maybe a simpler idea would be to have the sim/view/config/field-of-view
27 matches
Mail list logo
