vertigho

I know the texture issues have been mentioned ad nauseam, but is anyone experiencing significant performance hits at airports (other than those made by FSDT)? My Taxi2Gate, LatinVFR, and FlightBeam sceneries all cause a significant performance drop which is primarily seen as stuttering, especially when panning around/changing views.

Wonderful! Thanks for posting. Only waiting on a (functional) tool to tweak shaders, now.

I believe the answer is 'yes', to your question. You understand it correctly. I was previously running v3.0 and updated to v3.3 earlier today (err, yesterday, now). At any rate, I uninstalled "Prepar3D v3.x (Professional/Academic) Client". I also uninstalled "Prepar3D v3.x Content" (however this latter step is optional). I then downloaded the Install_Client.msi from Lockheed's website, along with cont1.cab and Install_Content.msi. Again, the latter two would not be required in your situation, as far as I know. You'd then run the installer for the client and you should be all squared away!

I've updated to v3.3 and am not experiencing any issues whatsoever with EZDOK. Obviously reinstall the client at your own risk, however I'm fairly confident that EZDOK will continue to fully function. :smile:

Hardly an accusation; merely an observation. The intent of my post was not to accuse Elaine of being disingenuous, but rather to explain my experience(s) and contrast it with that of others. Moreover, I took Elaine's post to mean that ASN is fully functional with P3D v3.3, assuming that it has been updated. If I misinterpreted her statement then mea culpa.

Anyone else noticed VAS issues? The simulator doesn't seem to be dumping memory upon changing the location of the aircraft and/or changing the time within the simulator. Immediate OOM upon doing any of the aforementioned. EDIT: After downloading/installing the current (beta) version of ASN, I'm unable to inject weather. I get the following error(s). This contradicts Elaine's statement earlier that ASN is fully-functional.

Halv, funny you should mention this. Mid-flight I had a realization -- I had enabled FSUIPC's autosave after an OOM. This is likely the cause of my occasional 'hiccups'. Will disable that and expect things will clear up. Thank you, all!

Will have a look. Thanks for the advice, will take a look and see if any of my other addons may be interfering. Starting to wonder about my AV, as it was recently updated. GTX 970 by MSI. Not top-notch, but up there. Doubt it's a GPU issue.

Walders, thanks for the heads-up. I suppose it's something to try. Will see if tweaking the built-in vsync makes any difference. Unfortunately the issue doesn't discriminate. It occurs quite similarly in all the aircraft I have flown (PMDG T7, PMDG NGX, Aerosoft Airbus).

Interesting. Yeah, mine don't sound anywhere near as bad as yours were. Mine are quite subtle (both in terms of frequency and severity) but they're annoying nonetheless.

Hello all, I know there have been a flurry of threads recently with the release of v3.0, and I had posted about this issue in the P3D v3.0 tweaking thread. That said, I thought this topic deserved a thread of its own. I have been experiencing micro stutters, where the sim will pause/freeze for roughly a quarter of a second every 3-5 minutes... closer to 1-2 minutes whilst on the ground. First and foremost: has anyone else experienced this since making the move to v3.0? I never noticed these prior to v3.0 -- I never noticed them at any point during v2.5. I have tried implementing an affinity mask, using a FFTF tweak, adjusting TEXTURE_BAND_MULT, implementing an internal and external frame limiter, and adjusted my road vehicle traffic. None of the above seemed to have made any difference. The only thing I haven't touched is the optimize_parts=1 entry in the .cfg, that I used in the past without issue(s), and noticed was automatically added to my .cfg, presumably by LM. At any rate, does anyone have ideas? I can post a link to my .cfg, NI settings, and in-sim settings. It's not horrible by any means but it's a slight bother. My frames are otherwise entirely fine. I livestream on Twitch and find that they rarely drop below 20 while on the ground, generally hovering in the 18-25 range while taxiing around, and almost always locked at around 30 while at 5000 feet or above. My sim feels incredibly smooth and "strong", for lack of a better term, it's just these darn stutters. FWIW, my frames seemed best with an affinity mask setting of 84, with 244 being a close second, and 254 seeming alright, although not as strong as the aforementioned. Using an external frame-limited (NI), and setting in-sim frames to unlimited gives a noticeable boost in smoothness and framerate (in lieu of a 30 frame lock in the sim). FFTF of 0.01 caused my autogen to load in at a slower rate, to the point where, essentially whatever I was overflying was rendering as my nose crossed the imaginary plane of the autogen. This isn't terribly surprising. I ended up deleting this entry soon after entering it (FFTF). As far as texture_band_mult goes, I heard some folks saying that raising it reduced their stutters, while others claimed that it's moot if you're using an unlimited frame rate. Any thoughts on this? Below are links to my pertinent sim inner-workings: .cfg Link: https://mega.nz/#!d9ZykKYJ!1JimqquCUI7B6PgJDtGpFAOucv47n_6YizsyUriMe2w NvidiaInspector Settings: http://puu.sh/kDNCx/7e6e586647.png http://puu.sh/kDNCY/617590d4dd.png In-Sim Settings: http://puu.sh/kDNxD/ff39c8466b.jpg http://puu.sh/kDNxT/147f840d16.jpg http://puu.sh/kDNy5/f287484bec.jpg http://puu.sh/kDNyf/eb6223cbca.jpg http://puu.sh/kDNyn/1a578f58f0.jpg Many thanks! -Ben

Great, many thanks. Up at FL400 and still noticing a minor hiccup, where the sim pauses/stutters for roughly half-a-second or so. Will see about throwing an AM change and going from there. Save optimize_parts and/or FFT for a later time, if ever... may not need them at all. One other question while I'm thinking of it -- any use in locking a framerate? Have heard mixed suggestions on this one. Some say unlimited (which is my current setting) whilst others suggest locking it around 30 FPS. Any thoughts on this? Thanks a lot, Bob.

I'm doing my first flight in P3D v3.0 and am noticing some minor stutters every 60-90 seconds. They seem more significant on the ground, around addon-scenery, and when moving within the sim. I have an i7 4790K, so I believe hyperthreading is enabled by default. Based on this, what would be my go-to AM setting, if any? Moreover, is there any use in inserting an FFT and/or optimize_parts entry (or any other tweak, for that matter) into my .cfg, or should I limited myself to only an AM entry. Thanks much. -Ben

Flew a short hop earlier on Vatsim in the PMDG ‪‎NGX‬. Callsign was DAL1363. Departed Phoenix Sky Harbor and arrived at Los Angeles. Great control, lots of fun!

No worries whatsoever -- feel free to use the thread however you wish. I can't answer to your question on AEC, however I can state that I'm absolutely thrilled with GEP3D and UTX. I ended up doing a full reinstall given my lack of comfort with the ORBX uninstallation (or lack thereof). I was able to turn *up* my autogen, and managed to gain roughly 5 frames and significant smoothness. The autogen itself looks phenomenal, both in terms of the raw aesthetic and the placement. While ORBX's night-lighting was quite nice, UTX provides a softer, orange'ish haze, a glow of sorts, and is visible from higher altitudes. I'd give UTX a slight edge in terms of night-lighting. VAS has been alright. I did a flight from KBOS to KPHL (FlyTampa to SunSkyJet) by night and got the warning dings on final, I'm assuming due to a combination of the night-lighting and the fact that downtown Philadelphia is right next to the airport, meaning there was a lot going on. I simply lowered my texture resolution from 1024x1024 to 512x512 and the dings went away and I landed without issue. All-in-all, I'm really pleased with my move and don't see myself going back. That said, it's ultimately a matter of personal preference. At any rate, I'm deviating from the topic at hand. Perhaps someone with more knowledge than myself can answer your question with regard to AEC.

Hi all, unfortunately the ORBX uninstaller didn't work for me (it wouldn't run, was unable to create the 'ORIG' folder during the uninstalling process). That said, I manually deleted my ORBX folder within P3D, removed the various entries in the scenery library, and went through and deleted all ORBX textures/sceneries I could find within my P3D directory, and then restored my backed-up textures. The one issue that still remains is the alteration of terrain.cfg. It would seem ORBX makes changes within there. Does anyone happen to have a backed-up copy of an original, unaltered P3D terrain.cfg that I could replace my current one with? Many thanks.

Thank you a bunch, David. Hugely appreciative! I'll post again if I have any further questions. I saw this was the case whilst researching GEP3D/UTX/ORBX tonight. Seems there are a handful of available combinations. What has tilted the scales towards GEP3D are the following: night textures, possible performance boost, autogen layout. Going to give the GEP3D/UTX combination a try, see what I think and proceed from there. May end up returning to the ORBX package, or end up with some combination, similar to what you mentioned. :smile:

Hello all, I'm a rare poster here but when I have posted with a question, I've always been incredibly appreciative of the support and assistance of the folks here. I'm back with another question, this one with regard to uninstalling ORBX products. I currently have ORBX Global, Vector, and Trees installed, along with several terrain corrections for FlightBeam airports. Given that I do the majority of my flying in the United States, and have been experiencing some minor performance issues, along with blurries and slow rendering of textures and night-lighting (as well as a general dissatisfaction with overall night-lighting), I wanted to make the transition to GEP3D and UTX 2.1 (along with a clean cfg), in an attempt to see if these will give me a better experience. But I digress. I'm aware that in order for GEP3D and UTX 2.1 to properly install and function, all ORBX products need to go. I'm also aware that uninstalling the aforementioned can be a bit tricky. How, exactly, does one go about cleanly and completely uninstalling *all* ORBX products, and the various remnants they may leave within the P3D directory? I've attempted to do some research on this issue but never saw a convincing answer -- I've also seen G3P3D/UTX converts mention that they uninstalled ORBX products, so it seems to be possible. At any rate, I was wondering if someone could possibly explain/guide me through the process of uninstalling all my various ORBX products, so that GEP3D and UTX will properly install and function. I don't care for the idea of wiping P3D and doing a clean install but unless I can figure out how to remove ORBX, I'm afraid I may have no other choice. I wanted to shoot this post out early this morning, as I plan on making the move to GEP3D/UTX later today at some point. Thanks much, Ben

This very well could have been some form of psychotic depression. Who knows, it's purely speculation, but psychosis can compel one to act in less-than-ideal ways.

Yeah, they are indirect victims of depression. Not only did depression claim Lubitz, it destroyed the respective lives of his family members, as well as those unfortunate others on the plane. Did Lubitz killed 150 people? I suppose he technically did. But I would argue that truly, depression (among other mental illnesses, apparently) killed 150 people. No rational, mentally fit person acts as Lubitz did. That wasn't Lubitz expressing himself. That was the black-hole that is depression expressing itself via Lubitz.

Hardly joking. I'd suggest you read the remainder of my post(s), as opposed to selectively quoting a one-liner.

When did I state that anyone is entitled to a job at an airline?

So what's your point? You seem to be backing off of the, "I knew this was coming", and now stating something more along the lines of, "he was at risk of doing this, steps should have been taken". I don't disagree with that much. What I do disagree with is the notion that Lufthansa shouldn't have hired him. If Lubitz could have proved himself to be mentally stable and fit, and received various evaluations (psychiatric, neuro-psychological, etc) that deemed him to be mentally stable, I see no reason that he should have had that opportunity. The FAA has a similar system in place. But this is another topic for another time. To call him "crazy" is misguided. He was human, just like the rest of us. I agree, he should have not been piloting that plane, at least not in his current state. If he had received proper treatment and had recovered from his illness, there's no reason that he should be denied that opportunity, in my opinion.

You can predict that someone is "at risk", which is the operative phrase, one you failed to state earlier (although it may have been implied). Just because someone is at risk of doing 'x', does not mean they will do 'x'. Again, think of how many mentally-ill pilots are currently flying. Now compare that number of ill pilots to the number of aviation crashes in a given year. And given this, take the number of crashes that ensued because of a mentally-ill pilot making a poor decision. See my point? Was Lubitz at risk of doing such a thing? I suppose so, if that means he was (in some quantifiable way) more likely to do so than the average pilot to do what he did. Does that mean this was predictable? I'd still say 'no'. This seems to imply that I'm not weeping for the victims. I certainly appreciate and empathize with their and their families' pain. That does not mean that I am incapable of empathizing with Lubitz and the pain he was experiencing. The two are not mutually exclusive. Again, I did not excuse or condone his actions. What he did was horrible and beyond selfish. That does not mean that we should disregard what he was going through. His "life issues" were very serious, likely worse than what the average human-being will ever have to deal with.

Sorry, but you really can't predict this type of thing. There are thousands upon thousands of pilots who are addicted to drugs, have some kind of (undiagnosed) mental health issue, whether that be psychosis, depression, bipolar depression, anxiety, etc, etc. They unfortunately deal with their respective issues in the dark, never looking for help, knowing that doing so may end their career. This is the unfortunate part of the medical-certificate system that exists for piloting, but it is what it is. This is another conversation for another time. I digress. My point is: there are many pilots who, despite many troublesome and agonizing mental issues, do not choose to fly their respective planes into the ground. To say that you could predict Lubitz's action(s) is shortsighted. I would also encourage posters to have a bit of empathy for Lubitz. While his action(s) was/were incredibly selfish, you must understand what he was experiencing. I would not wish depression on my worst enemy. I cannot think of a worse disease. Life is truly unenjoyable. There is nothing, and I mean absolutely N-O-T-H-I-N-G that brings you joy, happiness, or gives you a reprieve from feeling miserable. You're dull, flat, blue... essentially life is empty, and beyond that, there's a physical pain and discomfort of sorts. You feel bad, you feel sad... everything is miserable. This is not to excuse his action(s), because they were terribly selfish and certainly horrible. But please take a moment to understand and appreciate the awful pain he was experiencing on a daily basis (via no choice of his own).