kmagelie

It might work fine, or it might not work. But since Asus hasn't listed it as supported, they have either not tested it, or it does not work on the current Bios version. You can either take your chances, or you will have to find a motherboard that supports that RAM, or buy that motherboard and some other RAM that is supported. I have an Asus Z170 pro gaming motherboard and I'm running my G. Skill 3200 MHz CL14 RAM at 3000 MHz CL15, which works without any issues. But of course I would like to run my RAM at the specified speed, so I will buy a new motherboard when I have saved up some money for it.

Not all motherboards support all RAM, you need make sure the motherboard supports the RAM you have. Most manufacturers list the supported RAM on their support pages. I made the mistake of not checking compatibility before buying, and now my computer doesn't POST if I try to run my RAM on the XMP settings, I have to run it a bit slower. It's my own fault for not checking compatibility first though. I will probably buy a new motherboard (probably ASRock Z170 Extreme6, which is one of few motherboards that support the RAM I have).

Or you can use something like ModelConverterX to open the mdl files and look at the liveries.

Same here. Bought a GoFlight yoke in August and ordered two new saitek throttle quadrants to put my new cockpitphd levers on (btw, I do not recommend them, too expensive for what you get), but I am still waiting on the quadrants. In the mean time I have had to keep my Saitek yoke plugged in just to be able to use the throttle quadrant that came with it (tried just plugging it in to a PS/2 port, but that didn't work). Really hoping that they get the new stock out in December.

That's Flytampa. They just released updated installers for their scenery for P3D3, so they are sending people download links. Nothing to worry about. :smile:

Yeah, it's a great tool, when it works. :smile:

Sorry, Ron, I wasn't implying that you were exporting anything, just that you should still be able to open any model you want to, but you can't export it unless it is your model. The message will display every time you open a model that has custom animations that are not in your Modeldef.xml. As for the big red cross, I don't know, but you could maybe ask in the fsdeveloper forum. I know there has been some problems with the latest builds.

It just informs you that you can't export. I'm guessing this is done to try to stop people from changing other peoples work without the authors consent. You can still use it to check your repaints, though. Edit: The author explains the feature here: http://www.fsdeveloper.com/forum/threads/anti-piracy-measures.435395/

You can find the preview thread for the Aerosot CRJ here: http://forum.aerosoft.com/index.php?/topic/33966-aerosoft-da-crj-preview/ It's very long (177 pages right now), so I'll just post the latest news from Mathijs Kok from Friday: So it's looking like it's very close now (September, maybe?). And it's definitely for P3D2, as you can see from the tag "Preview FSX / P3DV2 / FSX:SE"

Interesting, indeed. I wonder if deleting these files or replacing them with dummy files will decrease the VAS consumption and, if it does, to what degree. I personally don't have many problems with VAS, but it is nice to see that they are looking into these things.

No, I have only installed REX Soft Clouds. To tell you the truth, I have not installed it because I'm confused by all the updates and service packs for Texture Direct. :blush: Anyway, I'm quite content with how my simulator looks, and I use some freeware sky textures, so...

The drivers work great for me on Windows 10 (build 10130), no problems. Also, I have no problems with Ezdok on Windows 10 build 10130. Actually, I have yet to find anything that does not work on Windows 10.

Just checked, and it's happening on my system too. I'm running P3D 2.5.12945 on Windows 10 Pro Insider Preview build 10074 (slow update setting) with a Titan Black on driver 352.84 (latest driver for Windows 10). The PCIe Link State setting is off and the Nvidia driver is set to "Prefer maximum performance". Not sure what impact it has, but worth looking into.

I notice that you have four display device lines in your cfg: [DISPLAY.Device.NVIDIA GeForce GTX 780 Ti .0.0] Mode=1920x1200x32 [DISPLAY.Device.NVIDIA GeForce GTX 780 Ti .0.1] Mode=1920x1200x32 [DISPLAY.Device.NVIDIA GeForce GTX 980.0.0] Mode=1920x1200x32 [DISPLAY.Device.NVIDIA GeForce GTX 980.0.1] Mode=1920x1200x32 I don't know if it has any effect on SLI, but you should probably delete the 780ti lines.

Well, the airport lights issue seems to be fixed (I only did a quick check, not an actual flight). I don't have SLI, so I can't check that.

It works just the same as before. Just start TrackIR first, then start Prepar3D. After Prepar3D is loaded and you're sitting in the cockpit, FSUIPC will start EZCA, which will then connect with TrackIR as usual. The only difference between this method and starting EZCA via exe.xml, is that EZCA is not started until the simulator is finished loading.

If you have FSUIPC, you can add the following lines in your FSUIPC4.ini file in the Modules folder: [Programs] Run1=READY,"C:\Program Files (x86)\EZCA\EZCA.exe" If you already have other programs starting in this manner, use the next available number (Run2, Run3, etc...). Also, you might have EZCA installed some other place, so make sure that it points to the right location. Then either disable or remove the EZCA entry in exe.xml. Now FSUIPC will start EZCA after the simulator has loaded.

G-sync is great, but it does not work in windowed mode (or full-screen windowed mode), so it will be of no use if you just want it for P3D. I tried it in FSX (full-screen mode) and it really made everything very smooth (as long as the FPS is over 30) and removed any kind of micro-stutter, so we will either have to hope that LM implement a proper full-screen mode for P3D, or that Nvidia makes G-sync work in windowed mode.

No, as I understand it the shared cockpit feature is an experimental feature that they were planning to add to the coming A330. They are adding it to the SP3 for the A32X to test it.

SP3 will be free.

I don't think the current version of the Airbus supports that, but SP3, which is being released next week, will support saving the state. See here: http://forum.aerosoft.com/index.php?/topic/91620-airbus-sp3/

It can be done, but it is not as easy as using EZCA. Take a look here: http://www.prepar3d.com/SDKv2/LearningCenter/getting_started/view_system/custom_camera_ui.html I'm using EZCA 1.18.5, though. It is a beta version, but it works. You can find out about it here: http://www.simforums.com/forums/ezca-1185-beta-available-for-download_topic51089_page1.html

Thanks for the heads up, Rob. That's perfect timing for me as I will be installing 2.5 tomorrow. :smile:

It's very easy and fast. Check out this link: http://scruffyduck.screenstepslive.com/s/help_docs/m/20268/l/199756-how-do-i-set-taxi-link-draw-flags-to-default-values

Excellent news! Very much appreciated. Have a nice holiday.