Simjockey

Eagerly awaiting the patch then I'll reinstall my MCE and PF3. Gerald, how are your patches normally posted - I can't see a download page other than the main program on the MCE site? Regards. Paul.

Some really interesting career choices here. I'm a hospital pharmacist in the Mental Health sector in the NHS in the UK. Paul.

Hi Bob, The PF_Emulator.exe solution was suggested by MCE support - it did seem to generate the activation request so Ben from the FS++ team had me download an alternative exe they were working on and suggested I delete the 'copied' emulator files. The new exe and other alternative files seemed to clean that up and interface with PF3 but I still cannot get vox to work with PF3 - am now investigating PF3 required setup with Dave at PF3. Although I'll have used up my demo time with MCE, I am so impressed with the support that I will purchase a licence and pursue the solution further over this weekend even if it means moving PF3 onto my FS PC! Paul.

Not exactly solved as I had an ntd.dll error on the first attempt after the fix and had a strange request on my sim PC for the activation code for PF3 (which is legitimately activated on the networked PC) on the second. Support were concerned that network latency might make it difficult for vox to work properly, so that might be an issue. Anyway here was their immediate advice (and they're looking closer at this type of setup this week) ... 1 - Go to the MCE cfg file in user..... /Roaming folder and change the two entries to read ... ATC=PFE IgnorePFERegistry=1 This will prompt MCE to ask for your PFE.exe (browse to the PF3.exe) folder on next startup 2- This didn't work for me as I think it kept looking for PFE (seems logical?), so support then suggested the following additional alteration ... Find the PF3.exe and PF3.ini files and copy then save back into the PF3 folder as PF_Emulator.exe and PF_Emulator.ini. This certainly stopped MCE continually looking for the PFE.exe As I said I had a couple of problems thereafter (I haven't spoken to the guys about this yet) but I think my ATC terminology is also at fault so not sure what part that plays as I can get the odd communication going using vox. Don't know if that helps, but what I can say is that support is fast - even over the weekend, so please contact them if I've not been clear enough. Let me know how you get on. Regards, Paul.

Update - wasn't expecting such fast support, especially over the weekend but these guys have already been in touch and exchanging emails. Great support. Paul.

I can get MCE working OK on FS PC (P3Dv3) and PF3 working OK installed on a client PC, but MCE only sees the native ATC. How do I get MCE to see my PF3ATC? Regards.

Hi Brent - you can't take on any paid jobs but can still fly the bird. Just fly her to a field with a repair shop. Regards, Paul.

Have a look at FS Economy ... it has given me a reason for flying FSX and P3D for years now. You could end up 'buying' your Duke or C208 with the virtual dollars you've earned while flying people and cargo around your favourite stomping ground. The FSE forum is also full of like-minded, very friendly people too. Regards, Paul.

Hi Poppet, I've seen shots like those from P3Dv2 users who are running in SLI mode - are you by any chance? Regards, Paul.

Gracias Pablo, Thank you John. I'll experiment with this when I next run P3Dv2 - at least I know what to try next. Regards, Paul.

ReShade problem (I think): Hoping some of you gurus might help me out. I installed Reshade with master distribution to P3Dv2.5 and it defaulted to the dx9 dll - I think I selected dx10/11 but it reverted back to dx9. On boot up of P3Dv2 I see the text confirming the shading stuff is happening but I see no particular difference to normal - is that because I have to alter some settings, or is it because it is set to change the dx9 stuff? What do I do next? Regards, Paul.

... joined the cause. Nice initiative.

@Driver170, in case your question was for me - usually crashed on climb out. Prob MTX loading in an incompatible model or something.

@Driver 170. If your MyTraffic was ver 5.4c, go back to ver 5.4b. I had ntd.dll errors in both FSX and P3Dv2 with ver 5.4c whereas 5.4b was fine. Sim.

Hi Carob, I've just finished installing a new W7 64bit copy - I think you only need to worry if a program crashes telling you that a .dll is missing - this happened to me when running my Elite Dangerous beta for the first time on this PC - told me I was missing the dxinput1_3.dll file. I then went to the MS update site and found the DX web-based runtime installer (or something like that). Let it do it's magic and no more crashes - runs like a charm. Just about to install P3D 2.4, and my addons hope it goes as smoothly! Regards.