vpwebsvc

Appreciate the detailed info. This is very helpful.

I may need a little clarification as to what the definition of a "job" means as it relates to P3D. Could that term be equivalent to a particular unique task that is being performed by P3D? Can only 1 "job" exist at any time on a specific core assigned to P3D or can multiple P3D "jobs" exist on the same core? I'm assuming the latter unless there are only 4 unique "jobs" produced by P3D which intuitively I would suspect unlikely. Appreciate any clarification that would increase my understanding.

Got it. We can easily use the Calculator to see what the Hexidecimal equilavent is of the AM decimal we intend to use when utilizing a batch file.

SteveW: I think the proverbial lightbulb may have finally gone off in my head after reading your most recent post. All the various discussions about the AM issue were causing me confusion and I instinctively knew I was missing something. When I first read your statement about using a 248 AM I initially thought you were referring to inside of the P3D config file which made no sense to me. As it was obvious that you know quite a bit about this subject I went to the link (Starting apps with a batch file for affinity) and I realized that was not the case. So I think I'm now starting to grasp this subject much better. I do have some questions regarding the link but before going there I want to ensure that my current understanding is basically accurate. Under the assumption that we are talking about a 4 physical core processor with HT active and one has additional add-ons with the desire to keep them off some of the first few cores that P3D will use and we wish to have P3D use 4 of the eight cores available, it becomes necessary to use an AM=85 in P3D config file (01,01,01,01). It's my understanding that the reason for not using AM=15 (00,00,11,11) is that placing P3D on the first 4 logical cores created by the first 2 physical cores is not as efficient as putting P3D into the first logical core created by each of the 4 physical cores (0,2,4,6). We then could create a batch file to set an affinity mask = 248 (11,11,10,00) for one or more add-ons which keeps them off of core 0 and core 2 which are the first two used by P3D. Hopefully I have gotten this correct. Assuming I do I have some questions: In the specific assumptions above is starting the add-ons on core 3 going to cause any significant reduction in the effectiveness of P3D on core 2 inasmuch as they are both controlled by the 2nd physical core? Is there any merit to shoving add-ons to just cores 5, 6 and 7 allowing P3D exclusive use 0, 2, and 4? Perhaps the answer to both 1 and 2 is it depends on the add-ons in question and their particular demands. With regard to the batch link you provided I wasn't clear on a few things: In that post there is the following: I will use a fictitious weather program called FSWeather.exe found in the folder "C:\Program Files (x86)\FSWeather". Rename it FSWeather.bat. If I take it literally this seems to imply to change the extension of the fictitious program from .exe to .bat which didn't make sense. Perhaps it means that we are to create a batch file that will be given the name FSWeather.bat?? One the lines for this potential batch file reads: C:\Windows\System32\cmd.exe /C start /affinity F8 FSWeather.exe. Below that batch example it then reads: "F8=248= . . . ." How did F8 become = to 248? Is there something else required to make F8 mean 248? I think that's it for now. Let me know if I'm on the right track and if you can help clarify the batch file confusion I'm having. Rick

I get the exact same result when I installed REX Essential Plus and use it with Prepar3d v. 3.1. Regardless of which REX wave animation I select the result is always the same similar to the photo attached above. The black bands appear to be waves and depending upon where you are in relationship to the sun (or in this case the moon) the light is reflecting off the top of the "wave". I've tried unchecking the REX wave and ocean water settings but nothing changes. Nor do using different REX wave animations if I leave them checked. I do not have this problem with REX Essentials and FSX. I will note that a file is created each time I start Prepar3d labeled WaveConstantsV3.xml in the same location as the Prepar3d config file. I've tried to change the name to a .bak file and even delete it and a new one is always generated. I suspect this may be the culprit but not sure.