Mischung

Hi, just found this one: http://www.prepar3d.com/forum/viewtopic.php?f=6305&p=129345&sid=a40affda934b08c5a8d58e3592570dc1#p129345 So it will not affect us, as P3D is part of Lockheed Martin Mission Systems and Training (MST) :wink:

Ok, I agree :wink: Then it's only true for part of software around. :smile:

Yes, you have to buy V6. Only incremental updates for a major version 5.x would be included. That's the normal case for almost any software out there.

Can confirm that there is no DME in the current data for RW 24. Maybe you can use ScruffyDucks airport editor or you can decompile the corresponding .bgl file and add the DME information. That's what I did some time ago to add some navigation data. KCRQ is inside the file APX16200.bgl and you can decompile that into an xml-file with ScruffyDucks decompiler (http://www.scruffyduck.org/download/i/mark_dl/u/4012602701/4609204440/Bgl2Xml%20160.zip). Inside of that XML finde the airport, here is the original part for the ILS/DME 24: <Ils lat="33.1268276274204" lon="-117.288922816515" alt="100.888M" heading="259.119995117188" frequency="108.700" end="SECONDARY" range="50017.0M" magvar="-14" ident="ICRQ" width="6" name="ILS 24" backCourse="TRUE"> <GlideSlope lat="33.1300305202603" lon="-117.275864034891" alt="100.888M" pitch="3.2" range="50017.0M"/> </Ils> And here is the DME added: <Ils lat="33.1268249452114" lon="-117.2889085114" alt="100.888M" heading="259.119995117188" frequency="108.700" end="SECONDARY" range="50017.0M" magvar="-14" ident="ICRQ" width="6" name="ILS/DME 24" backCourse="TRUE"> <GlideSlope lat="33.13003487885" lon="-117.275844812393" alt="100.888M" pitch="3.2" range="50017.0M"/> <Dme lat="33.1262432411313" lon="-117.28874489665" alt="100.888M" range="50017.0M"/> </Ils> After adding the new data you can use the BGL compiler (incuded in the P3D SDK) and rebuild the .bgl file. Just replace it within the corresponding P3D-folder and the DME should be there :wink: (don't forget to backup of course). You can also use the tools provided on this site to update the NavData to the latest AIRAC: http://www.aero.sors.fr/navaids3.html There is an installer provided which will also add the DME to KCRQ :smile: (but read the FAQ, because it has other consequences as well). Good luck! Marc

Hi, thought it would be nice to have an overview of all P3D-releases in the past. Now we can guess what the release day will be...but I think stochastics will not help much in that case :wink: Version Date Day Days between 3.1 ??? ??? ??? 3.0 30.09.2015 Wed 232 2.5 10.02.2015 Tue 134 2.4 29.09.2014 Mon 49 2.3 11.08.2014 Mon 126 2.2 07.04.2014 Mon 55 2.1 11.02.2014 Tue 78 2.0 25.11.2013 Mon 467 1.4 15.08.2012 Wed 145 1.3 23.03.2012 Fri 182 1.2 23.09.2011 Fri 175 1.1 01.04.2011 Fri 151 1.0 01.11.2010 Mon - We didn't have a Friday since V1...ha ha...

Thanks Steve for your posts! Makes it very clear. I have also very good performance with 4 cores (HT=on) -> so logical 8 cores. P3D may use all cores except on the main threads core where one LP is masked out, to avoid the competing 2 logical processes. So the main thread must reside on one physical / two logical cores alone! I also set an affinity for all other processes in the background (with Process Lasso) not using the main threads core at all.

I think it should be much better when using Nvidia Surround with three or more monitors on one card. I'm just about to switch from a 780 to a 980 ti because I want to go for three monitors and performance was not too good with the 780 @ 5760x1080 Will come back to report :smile:

The only thing I use as a "tweak" is an affinity mask for my i4790K with HT=on: - Logic Core 0 is close to 100% as it handles the main thread - I just masked out logic core 1 for P3D, to give the main thread the complete physical core 0 (which is logic 0 + logic 1) - I use process lasso (you can use any program you like), to give all other programs an affinity to use the remaining cores (logic 2,3,4,5,6,7) To give the main thread priority over all other tasks does help a lot! (Steve W helped a lot to open my eyes in that case :smile: )

Using hard-links was the thing I also thought about :wink: Unfortunately I had no time to try this at the weekend As it seems they will not longer support the CBE for P3D in the future I was thinking about switching to ProSim anyway. I'll come back here if I have some news... Maybe it's worth trying the Estonia Migration Tool for that purpose, but therefore I would have to deinstall the iFly from 2.5 first ...and I don't want to do this right now

Hi Gerard, I didn't try to install or port the iFly yet, so I don't know if it's working, but I'm also very interested if it will work! Like you I also own the CBE and I'm very disappointed that they will not update it for V3 , because it's the base software for my homecockpit. (I know it's not because they don't want to, but I'm disappointed anyway) Unfortunately they didn't tell much about why it will not work. So I assume it's not only the change of folders. Let's wait for an answer and I will also look into it on the weekend.

Hi there, I use a touchscreen for my FMC (sorry CDU ), so don't need the right click, but I know can choose from several options how the screen should react when touching it. And as far as I know the right-click behaviour can be disabled when choosing the wrong option. I suggest you should check a standard right-click on the Desktop for example and find out how to change that option for your screen. Then I would assume it will also work for P3D :smile: Regards Marc

As far as I can see you set up everything correct. The white hand is correct in my opinion...I think it means something like "manual" setting of the weather :wink: Try to display wind data in the PFPX map and you will see there is data available. For me it works this way...also with the white hand :smile:

Hi, also have an i7-4790K with HT=on. I use AM = 253 (11111101) in P3D.cfg (just to mask the LP 1 of the first physical core - so the main thread can make full use of it) Then I set the affinity mask for (almost) all other processes running in the background, to get them off the physical core 0 (they use cores 2-7). I use Process Lasso for that purpose. This gives me a really fluid sim, because P3D can make full use if the first core without interruptions. The other cores are never at 100% and can serve all the other threads easily. Thanks to Steve for pointing me in the right direction :smile:

Hi Nick, I think that's not a topic to cover in a 2min video, so I hope you don't expect that :wink: The FMC is a very complex thing and is not only working together with the MCP. If you would like to learn about the systems of a 737 (in that case the PMDG), but that's adaptable in most cases, you may have a look at the training-videos from "Angle of Attack" (flyaoamedia.com) - it's not free, but you can have a free trial for 1 week and see if this is the right thing for you. They have videos in the Groundwork-section covering the systems of the 737 (of course the FMC too). In the Flightwork-section you can learn how that all works together in flight. They sometimes have some offers on their training packages, so maybe you should register for their newsletter. Marc

On my side the following worked quite smooth: HT=on P3D without affinity mask other tasks use all cores, except LP0/1 So I tried to give P3D room to breathe with the main thread using the physical core 1. After reading Steve's suggestions I would set P3D's AM to exclude LP1 which hopefully makes it even better. Best case would be if we can even select the core for P3D's main thread, but that's not possible AFAIK :unsure:

Hi Andreas, just checked that again and the service pack is in the works, but definitely not released yet. Marc

Hi Andreas, found the following in the iFly-Forum: Following the Service Pack, work on the Freighter and ER versions will be completed. So, as far as I know there is no service pack availabe yet and therefore not a freighter version unfortunately. Regards Marc

Absolutely agree! I read some posts only when Rob answered or initated it. Always very helpful and informative. Keep it up! Marc

I agree with Johnman. Don't go for many cores, but for the highest frequency you can get. The first core P3D uses will be at 99-100% most of the time (in my case 4790K @ 4.5GHz). The other cores will be around 50% (depending on conditions). I had an i7-2600 @ 3.8GHz before and I had the feeling the processor could not keep up all the time. So, go for the cheaper and take care to get more than 4GHz, that's much more important than havin more cores. The 4790K is around 300 € only, so if you want a dedicated P3D system why not go for something similar (and save money ). Of course more cores will be useful for other programs, but not that much for P3D. Marc

I also have a Spyder Pro and of course monitor calibration makes a great difference. One thing I noticed, that the Spyder Utility running in background induced some bad stutters (1/2 s stutters) when checking the validity of the current monitor profile from time to time. I just killed the process and after that it was smooth like butter. :smile: So take care when using the utility. I had problems with it, even after changing the process' affinity mask to not disturb the P3D's main thread.

Anyone can confirm that the new driver is working? Any improvements maybe?

Hi all! Just wanted to bring up that thread again, as I also have some FPS issues with the iFly. With the F35 for example I can easily fly around with 70+/-15 FPS and it's very smooth (I use the FPS-limiter @24 because I get some stutters otherwise) With the iFly I also see around 60 FPS max., but going down to 18/20 sometimes. So the variance is really high and that does not happen with the other aircraft. I believe this gives me some stutters from time to time @ limited FPS. I'm not using any tweaks and my HW shoudn't be too bad (ok CPU maybe) - i7-2600 @3.8GHz / 780Ti / 8GB. Maybe anyone has a clue. I really need a good 737 in P3D and PMDG is not available yet. But I expect also a noteable FPS-impact there.

Hi. Did some more tests and lowering the resolution of the gauges monitors helps a bit. But you're right, it makes no difference if the gauges show up on a secondary monitor or within the 2D-panel on the first monitor. FPS-hit is the almost same. I also tried to find a third party software for the instruments, but I would like to have also terrain,etc displayed (I'm using the iFly 737). Maybe then I would have to stick with the cockpit builder edition, but that's quite expensive. Other avionic suites too, I know :mellow: Hm, just reduced the refresh rate of the PFD/ND/DU in the iFly-menu, that looks promising. Don't know if you have that options, but result here is not too bad.

Hi Yang, I experienced the same problem. I also have a 780Ti and using 4 monitors in total (1 USB). System is an i7-2600 @3.8GHz and 8GB RAM. I use one touchscreen 10" for the CDU and the USB-monitor for the instruments. (It makes no difference not using the USB-monitor regarding fps btw) My frames are 20-30 with 2 additional views then. I closed them all and with only the main view I was up around 45-60 fps. Figured out, that lowering the resolution for an additional view helped quite a lot. Did that with the CDU and frames came up again. Will give it another try with the instrument, maybe this is a kind of solution. Problem is, that when I'm around 20 fps I get some bad stutters from time to time. Don't know where they come from, maybe loading some textures, will have to do some more investigation. But I really would like to understand why some instruments result in half the frames I had before. Anyone has an idea? Marc

Hi together, maybe this is of interest for some of you. I tried to change the settings within the NVidia control panel and all settings except "3D..." were missing. I figured out it was my USB-monitor attached (Asus MB168+), which I'm using to display some intruments during flight. Unplugging the monitor brings back all settings. Does anybody know if they will become effective also? Because plugging in the USB monitor of course hides the settings again. At least it seems so, because P3D is running quite fine here (after the coud.fx fix of course :smile: ) Regards Marc