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:

Hi, by default, after installation of LOWS(which directed to D: p3dv3/simmarket) i also have a b12pilot/SODE folder in c programdata. The SODE installation itself at the end of the LOWS installation i directed inside my p3dv3 folder where it is now. My question, can i move the SODE folder from programdata to my P3dv3 folder where the other SODE folder is, and "merge" them? And one more btw, where should the p3dv3 exe.xml and dll.xml be located?? I have these both in programdata/LM... as well as in appdata/roaming/LM... . My UT2 entries for example sit in the ones at appdata/roaming/LM... But SODE installed its entries in the ones at programdata/LM... ?? Thanks, Simon

I use 75% airline - 25% GA... but also lowered the "show up" (amount, vis. distance...) settings in UT2.

I already had it smoothly running in p3dv3.1 and win10. But installation was an odyssey after reading 100 threads and applying this and that manually. No chance to remember all the steps... But now i had a problem with a scenery and tried this and that and finally broke my UT2 by searching for a solution. Now i get two times the red warning while the sim starts. ... As i'm writing here i'm installing again by your "simple way"... UT2 already installed. Started it right now, made some settings, closed it - no problem so far. ... Now the updated schedule and the powerpack... ... installed. ... Now disabled the migration switch and started the sim... ... WORKS!! ... THANKS!!

Sounds good - will try now. Can i simply disable the migration switch after the installation of UT2 and never have to switch it on again? Cheers, Simon

Does this work similar to the standard ATC window where you can choose this or that anouncement? I also prefer talking to atc by not talking...

Maybe my English didn't explain it clearly. I was meaning on non-ORBX airports or in other words on default airports. As many ORBX airports have custom build in lights sure they look great and are not affected by REX or whatever. And i don't think FTX Global (which i have installed) has something to do with the issue i was talking about. The cfg add from above i also have included since a long time. But sadly this doesn't change anything with the distance issue i talked about. With this cfg add it's possible to make the standard airport lights in the distance a little smaller for example, so you don't recognize the difference too much compared to the REX lights around your aircraft. As a temporary solution this is okay. But as i said, only with HDR turned off the REX lights show up correctly. So probably something else is responsible for this mismatch. Or maybe i should have started this as another topic as we are maybe talking about two different situations... If you like (and i hope it's okay to post this) here is a link to p3d forum which clearly shows my issue http://www.prepar3d.com/forum-5/topic/blurry-runway-lights-at-a-distance/

I just upgraded from a 580 to a 970 and the results are amazing! I'm running a 2700k CPU at 5GHz btw. Before i was flying most of the time with viewing distance limited in ASN to about 12 to 24 miles. This looked most realistic for me. Now i fly with about 60 miles and around 100 miles upper visibility, shadows and lighting nearly all in, i even tried maximum of 20 cloud layers in ASN and high reso clouds in REX4 with no big impact on fps to my surprise. Cloud drawing distance kept at around 60 to 70 miles. Maybe in certain situations or locations i will have to turn back some notches. Don't know if i really need 4096 clouds... But on a flight from ORBXs 7s3 to s45 i had no impact. FPS limited to 30, half refresh of 60 in NI, never went below 20FPS. I fly A2A GA. No tubes. Most of the settings i took from a thread from the ORBX forum. If you like do a search for "ultimate p3d setting" or so, you will find it. It was very useful as a base. At least here. But as always... different machines - different results. So keep tweaking.

I want to jump in hear again as i have the same abnormalities with runway lights on non-ORBX or default airports. Close to and around my aircraft i can see my desired rex lights. But at certain distance they disappear and instead i have generic lights showing up. Then with HDR turned off in game settings all lights show up correctly, rex lights all over the place. So for my simple knowledge it seems as if a specific HDR or fx file or value limits how far the rex lights are visible. Of course this value may have a global function and so is intentional set low by default? Can any expert out here explain which value causes this strange behavior or where is the relation? Or at least tell me i'm on the complete wrong approach... :-)

Do you mean the estonia tool? Then you don't need FSX to be installed as it creates a virtual or a fake FSX to migrate the desired addons. Cheers, Simon

Hello, after some more testing of visual settings i finally decided to keep HDR turned on in p3d v2.4. Til some days ago i had it turned off, but had installed something called "Nvidia RGB Full Range Toggle" which the author of simmershome.de suggested as an alternative for HDR or so. Don't know if this could have something to do with the issue i will talk about now... So now, with HDR turned on, like some of you i found the overall brightness a little too dark. Then i was thinking, why not turn up the monitor brightness a little... and voila, i was really happy with the result. But next time i entered the cockpit (A2A 182), the overall look of the landscape (VC pilot's view) was too dark again while my monitor brightness was still turned up. What i recognized then was, when i switch my ezca camera to the radio's view (mainly black background/panels...) and then back to pilot's view, everything is brightend up again like i want it to be. I mean it's not a big problem to quickly toggle views before starting the flight (simply because it's normal to tune radios before flying...), but sure it would be nicer to enter the cockpit with the brightness already set. So has anybody experienced similar issues or do you have a clue what is affecting what in my setup? Is it a monitor problem? Ezca? The probably still installed Nvidia Toggle? I'm at my parents home over Christmas so i won't be able to try this or that at the moment. Maybe it's not a hardware problem but if you need to know, Monitor is a Hyundai 24", GFX 580GTX Twin Frozer, Processor 2700K@4,5, h100i Cooler. Everything normally works smooth and 100% stable. Thanks you and have a nice Christmas time! Simon