!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About MajorTom

  • Rank
    Flight Student - Groundwork
  1. 5850x1080 is a perfectly well setting if you use 3 Monitors with NVIDIA surround and 'bezel correction' as I do (nevertheless I would not use 'wide-view Aspect ratio' with this, but thats OT...). The GTX 1080 is very capable of driving this as long as your CPU is in the same class like 7700K OC or above. Your settings in the 'world' options are a little bit on the high side if you want to stay above the 'hard' 18fps threshold even with resource consuming add-ons like ORBX, ASP4 and AS EGLL or EDDF, but this has nothing to do with your problem... For me this lookes like a 'failed' installation, so have you checked (when you install): - AV scanner is of - reboot after initial instal of A330 - reboot after final update (experimental!) with the updater Another idea is to use DDU in order to get completely rid of the NVIDIA stuff and install this again from scratch without retaining any mods... As said above I have a similar installation with the latest NVIDIA driver and it works perfect ! Best regards, Tom
  2. sorry, my mistake: since i started installing liveries and do always backup aircraft.cfg.backup is already overwritten... but i remember that [FLTSIM.1] DRAGON AIR was there again as [FLTSIM.13] DRAGON AIR removing that entry solved the message (which is only a message, so the A330 run fine even with that message...). And i do have more Aerosoft products so the updater was already there in the current version prior to the installation of the A330. Regards, Tom
  3. Happend to me as well, was easily fixed in aircraft.cfg - how it happend: install actual download for the first time - reboot run updater -> - reboot run p3d and load A330... there it is ! I retained the 'original' aircraft.cfg before fixing it so I can email it if required. Regards, Tom
  4. I believe this is a 'out of sequence' trigger problem for the AI Baro settings: if your transition altitude is 10.000 feet (as in Austria) and you set your cruising altitude below at 9.000 feet (doing a short 'go around' at LOWG for example) the initial trigger for setting Baro to STD will not be there, but after initiating descent the second one (STD to actual ) is there... so after landing the AI FO will repeat the message "set baro reference..." several times. And if transition altitude is the same as the cruising alt (for example FL100 in Austria) in addition the sequence for the cabin signs gets disturbed and you may end up with the cabin signs 'toggling' forever... I know this is an 'artificial' situation, I just searched for an answer to the OPs question. Tested with 4.5 HF1 and AS on all models. Tom
  5. Hello Mathijs, thanks for your answer and shedding some light to the 'crosswinds' phenomenon - first of all I want to stress that I have flown all your busses (and other ac) from the beginning, I do like them very much and believe they form an outstanding product ! And you and your team do an outstanding job given the constantly moving P3D environment (a nightmare for every project/program manager I believe...) Now why I'm so insisting on 'answers' : I'm in Hard/Soft-Ware Development now for 40+ years and had to learn the hard way to 'dig deep' when software showed 'unusual beaviour'. What puzzles me most is the fact that this 'excessive roll' or 'wing wave' will always happen (given bus model and airport) at the exact same points in the final path, up to four times. So this makes it hard to believe something outside the sim is the cause, this being a very predictible 'coincidence'... I do understand that these questions are not really a support issue, given the fact that only a small number of users seem to experience this. So what about moving this thread to the 'general' forums where we could continue to search for answers ? Best regards, Tom
  6. Hello Emanuel, that sounds like a stringent explanation, but you're missing several facts (sorry...) : - it shows with default scenery - it goes away with crosswind - its not there with rnav approaches: same airport, date, conditions etc. so your passing the exact same scenery points... Default scenery in my case is ORBX Global, Vector and openLC Europe, no airport addon enabled - would you recommend to test without any ORBX product ? If this is related to something like scenery reload causing a sharp fps drop this would be 'visible' in performance montitoring for several hundred milliseconds, so I'll go and try to show this. Tom
  7. Well, I've read Mathijs answer in the old thread, but i don't buy it - yet ... There has to be proof ! At least I have to see the reason behind that. The phenomenon is very consistent and reproducible at exatly the same points on final with a given ac/airport combination, even without addon scenery. My fps are well above 50, sometimes even 80, and there is no weather nor AI injection enabled which could cause a frame drop. I do know these frame drops very well when doing night time approaches to EDDF or EGLL, sometimes I have to kill AI completely in order to stop erratic behaviour of the bus, but the low fps is visible and can be logged. Here evereything is absolutely stable and out of nowhere the ac swings to the right. And on RNAV or with crosswind it will not happen... I'll do some more testing with logging enabled, i might even try to run with fixed fps in order to see the difference, and I'll report back.
  8. This has been reported earlier, some called it 'wing wave on ils approach'... I'm trying to get more insight to this since I moved to 4.3 in October (im currently at and P3D 4.4). My conclusions so far: - it never happens on RNAV approaches, only ILS - it only shows in 'calm' conditions, if crosswinds are too strong it will not show - all models/variants will show it, also with min. and max. ZFW - it is somehow related to scenery, for eaxmple i can reproduce it at LOWG (FSDG) with and without the addon, but not EDDF (Aerosoft) - i believe it happens with Navigraph and NavData, but i'll recheck this (i have current navigraph cycle but NavData is the one coming with the bus) I suspect it has something to do with ORBX, i have all of it (global, europeLC, etc...) and I'm somehow unwilling to remove all of that, took so long to install... I have Simwings LEBL as you do so I'll try to reproduce this next. Tom
  • Create New...