1 hour ago, Ray Proudfoot said:

@Nurmblitz, I've done as much as i can to help you but you seem unwilling to take my advice. You still haven't said what your startup aircraft was before you ran the nuclear option of Delete Generated Files.

Ignore SimStarterNG for now. Start P3D directly. At the scenario screen i hope you have a default aircraft already showing. Select Concorde. It takes a while as there lots of files to load.

You won't get a refund so if you want the problem resolving do the above.

You also haven't said if you have selected the Experimental option in the FS Labs Control Centre. Is that version up to date? You should be running Concorde build 227.

Have you turned off FXAA as recommended?

By all means I don´t want to look like a rude person but I gave a solved case to my fellow simmers who can take it as a warning or a hint to solve possibly a similar case. As said the Concorde and FSLabs CC do not reside in my computer any more as they caused the application to hang. I haven´t used the default plane method with P3D at all, I´ve chosen the plane I fly straight on. Originally I wanted to comment the earlier FSLabs thread but that was closed by administrators before I managed to do that. So I was not asking for help because I helped myself but offered a hint for others in trouble.

1 hour ago, Nurmblitz said:

By all means I don´t want to look like a rude person but I gave a solved case to my fellow simmers who can take it as a warning or a hint to solve possibly a similar case.

You're not rude but you are obstinate and apparently unwilling to take advice from someone who has successfully installed the FS Labs Concorde.

If your solution - after paying 70USD - is to uninstall the product that's one few if any are unlikely to pay any attention to.

1 hour ago, Nurmblitz said:

As said the Concorde and FSLabs CC do not reside in my computer any more as they caused the application to hang.

That's because you didn't follow the advice given by FS Labs or me here.

1 hour ago, Nurmblitz said:

I haven´t used the default plane method with P3D at all, I´ve chosen the plane I fly straight on.

And therein lies one of the reasons why it isn't working for you.

1 hour ago, Nurmblitz said:

Originally I wanted to comment the earlier FSLabs thread but that was closed by administrators before I managed to do that.

Because there were posts there that criticised FS Labs unfairly.

1 hour ago, Nurmblitz said:

So I was not asking for help because I helped myself but offered a hint for others in trouble.

But have you helped yourself? You're 70USD poorer and cannot fly a magnificent aircraft. I don't call that helping yourself. I call it shooting yourself in the foot.

If you want help in installing it I'm willing to help when your attitude changes.

Recently all of this talking about FSLabs just revived my serious will to see their products ported into p3dv6, specially after the 6.1 released...

I think it's fair critique to object to the intrusive way the FSL configurator interferes with the sim startup when not using the FSL software.  I sure would like to see it only run when an FSL aircraft is loaded.  Generally, though, once I make a choice to disregard the configurator's "suggestions", it doesn't keep popping up in successive restarts unless something weird happens like an incomplete/disorderly P3D shutdown.

I believe the need for FSL add-ons to ride on P3D running as admin is because the configurator must write to files in folder locations that require that permissions level, and a program can't spawn a subprocess with permissions higher than its own.  That could be solved by having a separate standalone configurator that runs in admin mode outside the sim, and TBH it probably should be done that way.  It doesn't bother me to run P3D as admin on a dedicated machine that is never used for other more security-critical tasks (e.g. banking, website admin, accounting etc), but for those that use a single computer to do all things internet, it can pose a legit security issue.

Anyway, I just cannot conclude that the inconveniences suffered from the FSL configurator's intrusive interventions are so strident that it warrants throwing my hands up, shelving the add-ons, and chalking up the hundreds of $$ spent as a total loss.  I just learned to work around it, just as I have for LOTS of other such small interprocess compatibilty problems in the flight sim universe.

1 hour ago, Bob Scott said:

I think it's fair critique to object to the intrusive way the FSL configurator interferes with the sim startup when not using the FSL software.  I sure would like to see it only run when an FSL aircraft is loaded. 

I'll need to double check in the morning but I think SimStarterNG allows customising of which DLLs can be loaded.

So if you have a Concorde or Airbus configuration it might be possible to only load their DLLs with those aircraft. For others create a custom DLL config that excludes them.

I'm not 70 dollars poorer but a thousand dollars richer now when I can continue to use the rest of the addons.

15 hours ago, Biggles2010 said:

To echo what Ray said, it has been the standard and recommended practice in FSX and all versions of P3D to install and run them as admin. It has also been standard to install and run most high end addons as admin. I have always followed this principle with zero problems......

I hardly ever ran anything in administrator mode in my entire time using FSX and P3D. Steve W advised me regarding what to do with respect to setting permissions (a very simple process), and running in administrator mode after that should not be required. As Luke says, it should be the user's choice how they run software on their own PCs, and what settings they use.

Edited December 27, 20232 yr by Christopher Low

1 hour ago, Nurmblitz said:

I'm not 70 dollars poorer but a thousand dollars richer now when I can continue to use the rest of the addons.

I've offered my help but you're clearly not interested. I'm done.

4 hours ago, Christopher Low said:

As Luke says, it should be the user's choice how they run software on their own PCs, and what settings they use.

This.

If I want to use FXAA (I don't) or SSAA is my choise and FSLabs doesn't have to interfere with that.

Edited December 27, 20232 yr by Juliett Alfa Romeo