tremor595

...@ http://www.shop.aerosoft.com Maybe just for a few days. It's part of their 25 Years Summer Sale with "new offers every week". At the moment you can grab NassauX at 50% off too for example.

Was just reading a comment by Rob A. over at AirDailyX with a sidenote like "...maybe 64bit already coming in v3...". Don't know how much beer was in play, but anyway: Just to keep the noise steady here...

...@ http://secure.simmarket.com/dreamflight-studios.mhtml

...@ http://cielosim.com/

...at http://www.fspilotshop.com If it's worth for you may depend on your location, conversion $/€... Also Justflight 33% off, PacSim 40% off and some other brands.

Sorry guys, untill I recognized the limited choice i I already typed it. Anyway, got Nuuk, Spitzbergen and Torp.

...at http://www.shop.aerosoft.com

...at simmarket.com

...and other discounts at simmarket!

Ok, back on my computer i found my old comparison shots. In the foreground you can clearly see the REX runway and taxi lights but at a certain distance they are "replaced" by the standard light bulbs. In the pictures you can see how different cfg settings (scalar) and HDR settings change the result. But really not a very satisfying workaround. These shots were taken in P3Dv2. But in v3 the results are the same. I really hope someone with a little better knowledge can explain what is needed to fix this. Cheers, Simon

Nice to see this suspect back on fire... When i'm back on my own computer i will see if i still have my comparison shots. Didn't know my post at LM's website doesn't exist anymore. Vincent, i think a night video probably could show the problem with the lights more clearly. At least on the little laptop here i couldn't see any lights in any of these comparison videos. But i'll give it another go when back on my computer/monitor. Anyway i really hope LM can fix this as it's a little frustrating when these big bulbs appear behind the nice REX lights. Cheers, Simon

You could also try to adjust the speed and smoothness of the mouse look. Lower settings makes it much easier to tune radios and so. Cheers, Simon

Hi Jeroen, maybe I should try without deleting the shaders folder, but yes, sometimes I do start the sim by just hitting the P3D.exe, for checking this or that without the simstarter options. But I think I don't remember any difference or black screen... I have this set up a long time. I was reading somewhere it doesn't harm to start with an empty shaders folder? And as I'm a tweeaker like many of us and new P3Dv3 installers, new things you don't need but have to try [ ] pop up everywhere, I was just keeping my start routine. But okay, I may take my stop watch and count the seconds when starting the sim. Maybe you're right? Simming time is expensive if you have a 10 months old son like I have... Cheers, Simon

I also have set up a batch file which deletes the shaders folder and also starts ASN and P3D, all in a row. The batch file itself is started by the simstarter tool, just had to point to it in simstarter's "start definition". So one cklick does it all. And so my shaders folder gets deleted everytime i start the sim. Simon

I now moved/merged the SODE folder from programdata to the SODE folder in p3dv3 root folder. Also deleted one of two SODE entries in simobjects.cfg. LOWS still seems to work alright. And i think the exe.xml and dll.xml in appdata/roaming which i was talking about in my above post have been created by the migration tool. I just copied the UT2 entries from there to the exe.xml in programdata, but then when starting p3d the red UT2 warning came back and UT2 didn't work. By deleting the UT2 entries again (so they are only in the exe.xml in appdata/roaming) UT2 works again with no warning. Sorry, completely off topic... :Shame On You: