Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. And I think I am going to quote, just to preserve this elucidating analysis for posterity.
  2. Exactly, I am going to stay with 7 as long as possible. There is no need to upgrade NOW, but the way Microsoft is pushing 10, practically begging people to install it, you can probably count on 7 being unusable for anything that's evolving rapidly (like flight simulators) within a few years. For starters, DX12 will only be available 10 and sooner or later developers will make the transition to DX12. Same thing is happening with OpenGL and Vulkan, i.e. on the Linux side, so there's a major change in GPU driver design philosophy in progress. If you don't want to be left behind, you gotta move on at some point. I actually understand quite well why Microsoft is forcing updates. Anybody who's ever helped a computer-illiterate person getting a system going again after a thorough mess up will understand! Windows has to work flawlessly on laptops, tablets an smart phones since Microsoft has decided that it's going to be one single OS to rule the whole universe of devices. The vast majority of users just want their chat and video apps to work without a hitch and never think (or even know) about things like drivers and optimization. Well, as flight simmers we are not that kind of user and Microsoft has already shown with Flight how much they care about that niche... If I need to tweak I'd rather do it on a platform that's tweak-friendly! Moving to Linux is going to be a long term project for me. It was really only FSX and Prepar3D that kept me on Windows this long. Everything else I need an OS to do is already well covered.
  3. The update policy is really just the tip of the iceberg. That and many other things happening with Windows show the direction towards which Microsoft is heading so clearly that I am planning my slow migration to Linux / X-Plane within the next year or so. I don't expect P3D to ever be ported to Linux (maybe it will be possible to run with wine libraries in a few years) because the market is just too tiny. Sad but understandable: even with X-Plane it's only 3% Linux. I don't want to insinuate that this is the path everybody should take - it depends on your priorities and of course how happy you are to fiddle around with configurations and computers in general vs just wanting to go and fly - but I definitely am one of those who Microsoft has finally pushed to jump ship.
  4. Are you running Saitek drivers? If the system freezes it could well be that those are the culprit. I don't install drivers (they don't add anything for me that I'm interested in) for my controls and never had any freezes or problems with either Windows 7 or Windows 8.1. (I do have the trim wheel)
  5. For those who find the colors too bland without P3D HDR enabled and have an Nvidia card - did you set 'Output Dynamic Range' to 'Full' in Nvidia Control Panel/Display/Change Resolution?
  6. Well, thanks! I've modified the code a bit to take care of bouncing: Now only the first ground contact within 7 secs will be displayed. Also, the variable L:Timer clashed with one used somewhere in the A2A C172 gauges; needed to be renamed. Since the community interest seems to be very close to zero I'll probably limit myself to topics such as 'My feelings towards X' from now on. gauge code update: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0" id="VSpeed"> <Descr>AceXML Document</Descr> <SimGauge.Gauge id="Gauge"> <Update> <Frequency>6</Frequency> <Script> (A:SIM ON GROUND, bool) if{ (E:ABSOLUTE TIME,Seconds) (L:DisplayInterval,Seconds) > (L:TookOff,bool) and if{ (E:ABSOLUTE TIME,Seconds) 7 + (>L:DisplayInterval) 0 (>L:TookOff) } } els{ (E:ABSOLUTE TIME,Seconds) (L:DisplayInterval,Seconds) > if{ (A:VERTICAL SPEED, Feet per minute) (>L:VSpeed) (A:GROUND VELOCITY, Knots) (>L:HSpeed) 1 (>L:TookOff) } } </Script> </Update> <Element id="Touchdown"> <Visibility>(E:ABSOLUTE TIME,Seconds) (L:DisplayInterval,Seconds) <</Visibility> <Element id="VSpeed"> <GaugeText id="VSpeedText"> <Size>50,28</Size> <FontFace>Arial</FontFace> <FontColor>red</FontColor> <BackgroundColor>azure</BackgroundColor> <FontHeight>25</FontHeight> <HorizontalAlign>CENTER</HorizontalAlign> <GaugeString>%((L:VSpeed,Number))%!d!</GaugeString> <Length>5</Length> </GaugeText> </Element> <Element id="HSpeed"> <FloatPosition>50,0</FloatPosition> <GaugeText id="HSpeedText"> <Size>30,28</Size> <FontFace>Arial</FontFace> <FontColor>red</FontColor> <BackgroundColor>azure</BackgroundColor> <FontHeight>25</FontHeight> <HorizontalAlign>CENTER</HorizontalAlign> <GaugeString>%((L:HSpeed,Number))%!d!</GaugeString> <Length>3</Length> </GaugeText> </Element> </Element> </SimGauge.Gauge> </SimBase.Document>
  7. I forgot: In the [Window Titles] section in panel.cfg, add WindowXX=VSpeed to get the gauge selection into the pulldown menus.
  8. Hey all, this thread: http://forum.avsim.net/topic/469334-landing-rate-plugin-for-fsuipc-improve-your-landings-fsxp3d/ inspired me to try myself at gauge programming, since I don't have FSUIPC and wanted something similar: It's a bit more involved that the FSUIPC implementation - it requires a new panel definition in the airplanes for which the gauge is to be used; this is what I'm using: [Window10] visible=1 size_mm=80,50 window_size=0.08,0.05 window_pos=0.0,0.5 background_color=0,0,0 ident=14080 zorder=5 alpha_blend=0.4 type=special gauge00=Touchdown!VSpeed,0,0 (ident has to be a number greater than 10000 not used in the panel.cfg, and replace the 10 in [Window10] with a number that doesn't clash with any other window, probably best to stay greater than 10. in the gauges directory, create a folder named 'Touchdown' and create a file named 'VSpeed.xml' in there, containing the following code: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0" id="VSpeed"> <Descr>AceXML Document</Descr> <SimGauge.Gauge id="Gauge"> <Update> <Frequency>6</Frequency> <Script> (A:SIM ON GROUND, bool) if{ (L:TookOff,bool) if{ 0 (>L:TookOff) (E:ABSOLUTE TIME,Seconds) 7 + (>L:Timer) } } els{ (A:VERTICAL SPEED, Feet per minute) (>L:VSpeed) (A:GROUND VELOCITY, Knots) (>L:HSpeed) 1 (>L:TookOff) } </Script> </Update> <Element id="Touchdown"> <Visibility>(E:ABSOLUTE TIME,Seconds) (L:Timer,Seconds) < </Visibility> <Element id="VSpeed"> <GaugeText id="VSpeedText"> <Size>50,28</Size> <FontFace>Arial</FontFace> <FontColor>red</FontColor> <BackgroundColor>azure</BackgroundColor> <FontHeight>25</FontHeight> <HorizontalAlign>CENTER</HorizontalAlign> <GaugeString>%((L:VSpeed,Number))%!d!</GaugeString> <Length>5</Length> </GaugeText> </Element> <Element id="HSpeed"> <FloatPosition>50,0</FloatPosition> <GaugeText id="HSpeedText"> <Size>30,28</Size> <FontFace>Arial</FontFace> <FontColor>red</FontColor> <BackgroundColor>azure</BackgroundColor> <FontHeight>25</FontHeight> <HorizontalAlign>CENTER</HorizontalAlign> <GaugeString>%((L:HSpeed,Number))%!d!</GaugeString> <Length>3</Length> </GaugeText> </Element> </Element> </SimGauge.Gauge> </SimBase.Document> That should give you an entry 'VSpeed' in the 'Views->Instruments Panel' pulldown menu. Enable that and every time you touch down your vertical speed in FPM and horizontal speed in Knots will display for 7 seconds. The gauge updates 6 times a second; I felt that was enough to be reasonably accurate while having a minimal perfomance impact. Hope somebody gets some use out of it!
  9. This I've got to check out. I'm not using FSUIPC but I'd love to see this particular info. I actually programmed a little utility to poll the vertical speed using SimConnect but for some reason I couldn't figure out it was never accurate enough to be really helpful. This has the potential to be more precise since it's in-process. I have to wait until Sunday night to try it out but if it does work - thanks in advance!
  • Create New...