It is like a prayer, never ever let something come on your products. Before you even read my post you already pushed away every responsibility of your products.
It's precisely because I DID read your post, that I gave you that complete and accurate description of the problem.
When will you ever understand that not everyone wants to blame you for making your products. I was just asking for help.
The only one here who clearly misunderstood it's you. Nowhere I even felt you were "blaming" the product and nothing in my reply suggests that, I only wanted to EXPLAIN why things are done in some way, because YOU asked "why you don't do it like others do". There, I've explained WHY we don't do like the others do, you made a specific question I replied to it.
If you wrote something different like, for example:
"I KNOW your method of installing is the proper one but, do you have any idea hot to fix my P3D which is SO abnormally SLOW to start ?"
That would have sounded very different because, you just can't say my post was only "defending" our products, when you don't even realize yours WAS, in fact, attacking. That's what "why you don't do like the others do ?" really means. So I told you why. Because you asked for it.
you recently hijacked my tutorial on Avsim to show the world your competence, but you would not use your competence to help me here.
Ok, I suspected there was something else going on. I haven't "hikjacked" anything and nowhere I said your tutorial wasn't useful. In fact, I STARTED that post with:
Some historic perspective why this procedure is required
The subject there was YOUR procedure: I was vouching for it!
I just wanted to help people understanding WHY they need to do that, and what issues might possibly happen either, so they might eventually understand why, on some scenery, they lost their effects or jetways, worrying they might have done something wrong.
The whole answer was only defending your products, your installation procedure. Did I attack your way of installation?
Yes, you did. You tried to pass our installer as doing something useless, which is why I explained why it's NOT and, in fact, it's the safest option, for most users.
I only said others can do it without Prepar3d.exe. I mean such an installation takes me 30 seconds. It still takes endless time for me to install a FSDT product on my P3D system.
30 seconds for the whole installation no, we can't beat that so, the "others" are clearly better than us. But just for kicks, I tried installing a scenery ( PHNL ), asking to enabled it in BOTH P3D4 and P3D5. Timed the procedure from the moment the sign "Configuring Support software in P3D" appeared to when it ended and, it took EXACTLY 20 seconds for each sim so, 40 seconds in total added to the installation.
Could we make it faster if we added the add-on to the add-on.cfg directly ? Sure, but it's not worth risking all the horror issues we DID have with FSX, just to save 20 seconds on each install.
It is not antivirus, I know about exclusions but defender was off anyway for installation, as I wrote. So tell me, what am I doing wrong? You say my system is broken somehow, it does not work like expected. What do you know, what I don´t know?
Where, exactly, I said "your system is broken" ? Nowhere, of course. You said you have a lot of sceneries and objects. Ok but, even that still can't explain such a dramatic difference between a normal 20-30 seconds and your reported 30 minutes and over. Just the GSX installation adds about 10.000 files to the Simobjects, but I still see just a 20 seconds delay to start P3D in configuration mode from the installer. Even if you had 5x the number of objects, it would still not explain that.
Have you added the antivirus Exclusions ALL folders that contains both Sceneries and Simobjects, whenever they are ? So, for example, if you have several drives containing add-on with lots of files, have you added all of them to the antivirus Exclusions ?
If you have multiple drivers, are these all SSDs, or you also have mechanical drives or, possibly, network drives as well ?
If you have mechanical drives, could be they might have turned down in sleep mode, so perhaps there's an added delay because they need to wake up ? That won't last minutes, of course, but I'm trying to think ALL things that might result in a startup slowdown of the simulator.
Do you have some cloud drives too ? MS OneDrive gives you the option to have your entire Documents folder on the Cloud, but it's not really reliable, up to the point that, some developers for P3D even said their add-ons work ONLY if the Documents folder is NOT on OneDrive.
Also, do you also have an abnormally long startup time when you start P3D normally ?
Memphis runs fine after a reinstall. I don´t know if ORBX has something to do with it. But you seem to know everything.
There's always an explanation, as usual, even for those that don't know everything, but are willing to learn. Reinstalling KMEM put it automatically on top of the Scenery Library so, it's possible this was that fixed it.
Of course, it's not that I "made up" the problem caused by OrbX. I said that to save you from searching the forum, where the canyon walls issue has been discussed and yes, it was caused by something from OrbX, did it looked something like this ?
http://www.fsdreamteam.com/forum/index.php/topic,13614.0.htmlThat seem to match what you described as a canyon so, I was HELPING you here trying to understand the problem.