Zap

One of the huge advantages of Tileproxy to me is that it creates the water mask that's necessary to display rivers, lakes, oceans, etc. properly as water. With FSEarthTiles this has to be done manually and creating a water mask for even a fairly small local area is very tedious and time consuming work.

I'm running W7 Pro by the way and my Asus motherboard does the same as yours. When I reboot and press F8 I also get the which disk to boot from initially and then I select my OS boot disk and press enter. I then keep pressing the F8 key as the boot process continues to get the "Advanced Boot Options" menu I mentioned in my earlier post. Good luck!

The Tileproxy driver is not digitally signed for use in W7 so Windows won't allow it to run. The solution is to disable driver signature enforcement by re-booting and pressing the F8 key during the boot process to enter the "Advanced Boot Options" menu. Scroll down using the arrow key to "Disable Driver Signature Enforcement" and press enter to select and complete the boot process. Hope this works and stick with it because Tileproxy is certainly worth the trouble!

Mike and Steve, I just wanted to add that this is also true on my setup - the waves always travel the same direction regardless of wind direction. In regards to water and waves I'm using only original FSX texture and effects files by the way. Mike, I see you're just ahead of me in the competition for fewest posts per time as Avsim member! :wink:

This extremely thorough analysis of SSD vs. HDD performance in FSX posted by Avsim user SAAB340(Lars) will completely answer your question: http://forum.avsim.net/topic/447702-the-differences-between-hdd-sshd-and-ssd-for-photo-scenery/

This is a significant discovery for users of DX10 who use more than one monitor. Having followed the sound advice found in your excellent guide, Paul, Single screen vsync has been functioning perfectly well for me in DX10 , but I could not find a way to eliminate the ugly tearing from lack of vsync when using three monitors until this fix came along. I actually reverted to DX9 for the last couple of weeks due to the ugly tearing in DX10 when using my multi monitor set up. With this fix I'm thrilled to be back running DX10! I'm simply using D3DOverrider set up as described in this thread with separate views(not Nvidia Surround) on each of three monitors for a wide panorama with fully functioning vsync. Thanks all!

Impressive Rick, and thanks for posting it. Is that the default zoom and eyepoint for the NGX or have you modified it? I ask because it just seemed like a very natural view especially with the panning and zooming via your Track IR.

Here is a post by Tabs(Ryan) from a while back that addresses this issue:http://forum.avsim.net/topic/341886-fps-drop-when-mouse-cursor-visible/page-2#entry2047611 Edited to add this post I just found by Capt. Randazzo earlier in the same thread:http://forum.avsim.net/topic/341886-fps-drop-when-mouse-cursor-visible/#entry2046514

Looking good! In light of the advantages that DX10 brings to the table, such as significant VAS savings and the associated prevention of OOM errors(clearly a serious issue plaguing many of us FSXers), I hope that PMDG have recognized this and made the 777 DX10 compatible. Along with the performance advantages, DX10 also has cockpit shadowing in the VC in compatible aircraft which adds incredibly to immersion. So along with having fingers crossed hoping the 777 is DX10 compatible, I would also love to see the NGX get a DX10 update.

Jim since it looks likely you're doing some methodical testing during the development of FSXAssist, if you haven't already, would you mind giving AM=244 a try?

Thanks pH, I have yet to try setting affinity using anything external to FSX but seeing your positive results I certainly will give it a try. PieEater, my system was very much like yours concerning max stable overclock and temps being about the same with or without HT. If and when you try AM=244(00101111) I hope you will also try AM=252(00111111). It will be interesting to see if you get the same flaky fps/stuttering I mentioned.

PieEater, what I observed when setting an AM that caused thread collisions was an unsteady frame rate that would drop from 30 down to around 18 quite regularly. This issue was eliminated by not allowing Hyperthreading on the core assigned to FSX's main thread via the AM I talk about in my previous post.

Interesting discussion. I'll add that most of what I know of the affinity mask variable is thanks to SAAB340's excellent analysis posted elsewhere here on avsim. I get the best performance using AffinityMask=244. With that AM setting the cores of a quad core processor run like so (00101111). Setting FSX's main thread to run on core 1 with no Hyperthreading on that core seems to be the key. The texture loading threads run on the remaining two cores with Hyperthreading on which seems to result in the best performance. I tried many other options and found, just as you state SAAB340, having a Hyperthreaded core associated with FSX's main thread caused periodic stutters and an unsteady frame rate. One example of an affinity mask that caused stuttering from thread collisions is AM=252(00111111). So to answer the OP's question, yes HyperThreading on, but with the caveat of using an AffinityMask set to allow a "hybrid" of both HT off for the core with the main thread, along with HT on for the texture loading threads.

I had to do just as TurboTomato mentioned to eliminate a ring of ugly yellow tinted tiles in the distance when flying around Florida by altering the level mapping line in my ProxyUser.ini like so: level_mapping=9,10,12,12,13,14,15,16,17,18,19 In your case I would suggest you start by trying: level_mapping=9,10,11,12,13,14,15,16,17,19,19 then: level_mapping=9,10,11,12,13,14,15,16,18,18,19 etc. until hopefully you find the zoom level that is giving you the trouble. Best of luck!

You're right Jim, that was a fantastic video for all the reasons you said. Thanks very much for posting the link.

You'll find some more good answers to your questions regarding this specific ILS approach in this thread too: http://www.flycay.co...-ILS-12-at-MKJP

Which stress test (IBT, Prime95, etc.) did you run? Also in CPU-Z what is your Core Voltage while running a stress test?

To add another similar mistake to watch out for that I'll admit to with my build: I noticed in GPU-Z and Nvidia Inspector that my video card slot PCI-E spec was shown as 1.1 rather than the 3.0 I expected. I went in to the bios and found the setting for the slot was on "Auto". Setting it to "Gen3" allowed it to run at the correct PCI-E 3.0 spec. My board is an Asus P8Z77-V Pro and these settings were found under "Advanced\ System Agent Configuration\ NB PCIe Configuration" in the bios.

I think typically your cd/dvd drive(P6 in your case) should be at the top of the boot priority list. This allows you to boot to your Windows or other system repair disc in case of trouble. Your OS drive, P1: M4-CT064 should be second in priority. In your second screen shot that lists both your SSD's if you click on the P2: M4-CT256 line you will be given the option to disable it as a boot drive. You should do this if you're using this as your FSX/data/etc. drive and it doesn't have an OS on it. Sorry you're running in to trouble and need to reinstall, what a pain. Do you have a larger HDD to back up your system to once you're eventually up and stable?

You're on the right track with starting with just the one SSD with your OS. I hope you plan to get your system up and stable at stock speed before you delid or overclock your cpu. Walk then run!

In pursuit of reality, anyone know how this part of planning is typically handled by real world commercial jet pilots? Are they doing it themselves, or is dispatch responsible for this?

Gizmo I would love to see some Florida Keys/Miami shots if you are able to do it(different thread I guess might be best). Really want to see how the water was handled down there before buying Florida v2...

Then you did the same in the first sentence of your review, ha ha!

Hi ugo, Yes, start tileproxy first and then FSX. Tileproxy does need to be running to supply the tiles to FSX. It will use the tiles it needs that have already been downloaded and saved to the cache.

I'll add my thanks to you also Ricardo for taking the growing DX-10 user base in to consideration as you move forward. I'm hopeful you are also planning to incorporate DX-10 compatibility in to the rework of your KMIA.