levada

I get: An error occurred (500 Error)We're sorry, but a temporary technical error has occurred which means we cannot display this site right now. You can try again by clicking the button below, or try again later. Fatal error: Uncaught exception 'ErrorException' with message 'mysqli::prepare(): Couldn't fetch IPS\Db' in /home/orbxcom/public_html/forum/system/Db/Db.php:385 Stack trace: #0 [internal function]: IPS\IPS::errorHandler(2, 'mysqli::prepare...', '/home/orbxcom/p...', 385, Array) #1 /home/orbxcom/public_html/forum/system/Db/Db.php(385): mysqli->prepare('/*IPS\\Session\\_...') #2 /home/orbxcom/public_html/forum/system/Db/Db.php(688): IPS\_Db->preparedQuery('REPLACE INTO `c...', Array) #3 /home/orbxcom/public_html/forum/system/Session/Front.php(294): IPS\_Db->replace('core_sessions', Array, true) #4 [internal function]: IPS\Session\_Front->write('8ffdf85358e36f9...', '') #5 {main} thrown in /home/orbxcom/public_html/forum/system/Db/Db.php on line 385

That happens when you use the wrong version. I used the correct one never had a single crash, not just in the menu, but not even the game (as far as I can remember). Unlike what you claim, uiautomationcore.dll is most definitely required as stated a few years ago on the blog of one of the developers who worked on FSX. It depends on which OS you're using.

DX10 anti-aliasing is rather poor, it results in shimmering scenery and cockpit, it really kills the immersion in my opinion. I have none of these problems in DX9 with 4xS and 4xSGS selected in Nvidia Inspector, it makes scenery and cockpit look SUBSTANTIALLY better and I can't say that it affects my frame rates, but then again, my card is rather fast.

phmcrt wrote: "Your graphics engine has trouble processing the whole picture" I don't understand why you talk about memory in that context. Memory is just one thing that could cause issues and if it would have been a lack of memory, then you would have probably crashed with an OOM (Out Of Memory) error. A slow video card, a poor driver, wrong setting or poor tweaks are just a few things that could also lead to issues like this (more likely than lack of memory)

Meh... not uncommon under those circumstances with a decent machine. Wait until you're in a thunderstorm with settings at max, strong anti-alias settings in Nvidia inspector, taxing on the ground at a large add-on for Heathrow with all settings at max including AI during "rush hour" and with a PMDG 777... have fun!

FSGRW is less demanding than ASN in heavy weather (default settings) and this is coming from a fan and user of ASN.

Did you contact RealAir to inform them about your findings and what was their response?

The fastest way to solve a computer problem is by ruling things out and not by ramdomly fiddling. By just renaming your FSX.cfg and allowing FSX to create a new one, you could in a very short time rule out major issues with your configuration. The same story for files like exe.xml, dll.xm, scenery.cfg, etc. Also look at your add-ons and their settings Depends on what you call moderate. There is a little more we can do, since we don't know your add-ons, their settings, the content of FSX.cfg, scenery.cfg, exe.xml, dll.xml, your driver settings, where you're flying when you get low frame rates, what kind of weather you have, etc, etc. I could list leterally close to a 100 things (if not more) that could affect your frame rates.

In that case this thread shouldn't even exist, let alone with a title like "FSX .... End of an era".

I seriously doubt that. I've monitored my graphics card with GPU-Z when it would sometimes artifact on High 2.x and it wasn't even close to being stressed out. It's a design issue in FSX if you ask me.

It's alway nice to see threads like these that again confirm that I'm one of the lucky few who can tell the difference between rushed "quick bucks" products and the planes from (I bow for them) A2A, RealAir, Majestic and PMDG.

With Venema's logic, Adobe would never have switched from 16 to 32 bit or more recently, 64 bit...and also they have to deal with the fact that third party developers have developed tens of thousands of plugins, add-ons or programs that rely on their products. If Venema thinks that LM can stop progress, then he's hallucinating. The huge majority is already using a 64 bit OS, soon we'll see 8 core processors becoming common place or graphics cards that make a GTX 980 look like a 9800 GT. You can optimize VAS all you want, but at one point you're reaching limits (which P3D already does!), with graphics that will still look like the ones from FSX ...cough, cough.... almost 10(!) years old. Improved shadows, lighting or fog will never fix that. Compare that to the improvements in popular gaming... On top of that, if Venema wants to keep selling his products, he will have to make them look better and better. When you visit flightsimstore.com you'll notice that FTX Global, Vector and LC continue to be he his best selling products. To keep that going he'll need to improve those products and to make them look better, you're always going to meet the evil VAS at one point. If he thinks that he can just survive by pumping out more and more airports, then he needs to think again.... And look at the current situation with all these so called "VAS optimizations" in P3D: No... you can NOT continue this way without 64 bit and if you do, it's only a matter of time before someone else takes over, like a 64 bit Xplane that could start a kickstarter campaign with additional support from a major investor. And don't underestimate Dovetail Games, they have some major plans for the future with their business and I wouldn't be surprised if that could also include a brand new flight simulator, nothing related to FSX. The owners are very determined to become a major player in the simulation industry (their own words) and it's not without a reason that their reasonable young company has already over 100+ employees. Blackberry thought they were invincible too.... Internet Explorer was the most popular browser by far... and look at it now. 64 bit or the customers will eventually move elsewhere... I can guarantee you that! No company is invincible!

Please, can we just stick to the topic of this thread, instead of chatting about the metric/imperial system, French, Canada or any other off-topic subject you guys can think of? Thanks.

Quote P3D developer Kevin Cartrette: "This attempts to optimize multiple parts of a model by combining them into fewer meshes if possible. If you have a complex model that is not already optimized to reduce draw calls etc, this will attempt to do that for you. There is some overhead to this, as it happens at runtime when the model is being loaded and ideally the model would already be optimized before runtime. This only happens for FSX Models, and not older model types." Quote P3D developer Adam Breed: "The reason this is disable by default is we identified potential issues with crashing on Windows 8 machines." Geesh guys, don't you ever check the P3D forum, you know....the guys who actually made this product....

Sorry Robert, I planned to buy the Turbine, but since you obviously care more about potential customers than existing customers who are already facing a lack of landing lights of almost 1 1/2 year, I don't see why I should buy the Turbine with such a lack of customer service. I pass.

That; That just shows how people can differ in opinion. I think the C207 has one of the best engine sounds out there. I want planes at least to be close to the original, but more importantly, sound like "heavy" sounds that come from an engine and not a speaker and that's the case with the engine sounds of this plane. I'm very disappointed in the sound of most Alabeo/Carenado planes out there, but pleasantly surprised with this one, most definitely in my top 3 when it comes to sound.

You know what, I'm just going to order it. I just came to the conclusion this week that the whole lighting system in FSX is completely messed up to being with. It is strange however that you say "we give you an option of reverting to default landing beams", when the piston V2 would completely loose all landing lights with the fix. Is there something I'm missing here Rob? Sound is super important to me, to a point that I actually refuse to fly any plane that completely fails in that area and for which I can't find better third party sounds. Needless to say that I don't fly many Carenado planes...

Yeah, I don't get it either, they look like clouds that were heavily smudged, blurred and put back in the pack, the outcome doesn't look like real clouds, not even in shots of people who claim that they're looking great. Too me it looks overdone. Anyway, that's just *my* opinion. :wink:

I haven't commented on this thread so far and I had no intention either, but do I feel the need to say that we shouldn't call the people who have a criticial note "whiners", "whingers" or ones that "slag him off". Just because someone puts a lot of effort into something, which all us of appreciate, shouldn't stop others from sharing their opinions. Their opinions are just as imporant as this test. Just my 2 cents.

I don't know if I should buy it....I'm tempted, but I had many missing clickspot issues with the Duke B60 V2, solved with a patch, but it killed the landing lights.

Thanks guys! Temporarily switching to a bare bones FSX for testing purposes and back to the original FSX is just a piece of cake when you know how to do it and you have a backup, it's just a matter of taking a shower and it's done. We do a lot of this kind of scripting in our IT department. Anyway, thanks for the assumption that I would spend like 3 days on setting up FSX + add-ons and do something as ludicrous as removing it all just because of a light issue, I appreciate it. :wink:

I already solved the issue with the bright lights, it was related to REX 4, but the biggest problem remains; why do they turn off when I get closer? I even completely unistalled FSX and only installed FSX + SP1 & SP2, but the issue remains (on modern hardware), every time I get closer these lights turn off and stay off. The closest lights also turn off when I zoom in. A lot more people should have this issue when they only have FSX + SP1 & SP2 installed and nothing else. Note: all autogen settings were at lowest settings for this screenshot to make the issue better visible.

How can I be the only who has seen this both on this computer and 2 completely different computers, all with a bare bones FSX? After further testing It seems to be a landing lights issue, I can clearly see it when I fly at night, triangular cones in front of the planes. They turn off when I get close, plus they seem to be way too high.

Strange lights near planes that disappear when I get closer. What is causing this? I also saw it with a bare bones setup of FSX. FSX SP2, no traffic add-ons used, no airport add-ons used, other than Orbx Global:

I refuse to buy anything on Steam.