jeffhunter

Same here, but I got charged anyway. When I tried to get a refund, I was told that "Our refund policy limits the number of refunds for which customers are eligible within a year and you have already received the allowed number of refunds this year. Thanks for understanding."

Sorted. Pls ignore.

Hi, Today I finally ditched EZCA2 and bought Chaseplane, however I cannot set the hat switch on my joystick (T16000M) to tilt or pan in CP preferences, and I cannot tilt/pan - full stop. I don't seem to be able to post a screenshot. I'm running P3D 4.4 on a Win 10 build 1809 PC. I uninstalled EZCA before installing, and noted that during the CP install, it detected some vestigial remnants of EZCA and (presumably) deleted them. If I try to set the hat switch to tilt or pan, when I move the switch, CP does not detect it. I can set any other axis to tilt or pan, but not the hat switch. This happens whether I have the View (Pan) set to "Hatch switch 1" in P3D settings or not, and also whether I've got the input set to Raw or DirectInput. I note that someone else found that they had to move their joystick (saitek) before moving the hat to set it, but if I do that, it just sets the joystick X or Y axis as the tilt/pan... I don't have any joystick assignments set in FSUIPC, either. Weirdly, if I use named assignments, CP recognises my hat switch, but not the named assignment: ie, if I input "tilt up" the dialog says "affecting 0 presets"... Any ideas? I've searched the forum and elsewhere with no luck. thanks, jeff

Me neither. I've tried creating one in pfpx and exporting it, but it seems it has to be done manually. Jeff

No, they're not required. You just won't get the correct call-out re minimums. I can't understand what the problem could have been re VHHH 25R. Taking a punt, can I enquire about your navdata? I haven't got the -300, but did you get a navdata update with it? cheers jeff hunter

I'm sure he meant indicated airspeed. True airspeed of 299 at FL300 would mean an IAS of about 188, which is very slow. Using the most recent example from flightaware - which cruised at FL400 - 0.78 mach would result in a TAS of 447 kts, and a touch under 250 indicated (assuming a std atmosphere). jeff h.

I struggled with the virtual cockpit when I first got the NGX, but then I discovered the EZ-Dok camera aka "EZCA", which enables you to set up a series of different VC views that you access simply by hitting a specific key eg, Capt/FO, FMC, radios, lower/upper overhead panel, engine start, MCP, etc It makes life much easier, and is well worth it. You won't miss the 2d panel. cheers, Jeff Hunter

That solved it for me. I only ticked "suppress turbulence" and the problem was fixed immediately. thanks, jeff

Thanks also. Moving the view forwards solves the problem, but ezca won't let me save the new view, it just defaults to the original one. If I try to save it as a new view, as soon as I click in a blank slot, the view jumps to behind my left shoulder, if you get what I mean. Also, I move the view using the arrow keys, but a single press moves things a lot. Is there a key-stroke combination that allows for smaller increments? thx jeff

I used the profile posted above, but when using the default left seat view, I cannot click any of the buttons. Changing the view to other areas of the cockpit is fine.. Has me bamboozled.

The creation of an .xml file is: Open notepad. Paste the code into notepad. Save as "exe.xml" done The syntax of that file does not entirely accord with what I think is required. Or did the cut and paste into the thread go awry? My exe.xml is: <?xml version="1.0" encoding="WINDOWS-1252"?> -<SimBase.Document version="1,0" Type="Launch"><Descr>Launch</Descr><Filename>exe.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad>-<Launch.Addon> <Name>EZdok camera addon</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path> <NewConsole>True</NewConsole></Launch.Addon></SimBase.Document> Have you downloaded and substituted the "tweaked" EZCA.exe for the default 1.17 version? Have you added the code to the .cfg files for the aircraft you want EZCA to work in? cheers, jeff

Hi Lee, It's very straightforward. You buy a p3d key by way of the Configuration page, and then make sure that your "Simulator Folder Location" is pointing at your p3d root directory. cheers, jeff

I managed to get it working without trouble by following the steps specified in this post from the Ezidok SimForum, which I have set out below. I did not change the name of the p3d exe file to fsx, as I read elsewhere that that could cause dramas. I can't now be sure whether I also reinstalled Ezca using the FSX2P3D tool, but I think that I did. "This is a EXE file only with P3D support. 1. Restore original Prepar3D.exe file name. 2. Go to Program Files\EZCA folder and backup old EZCA.EXE file (rename ECZA.EXE to any name) 3. Unrar this archive to Program Files\EZCA folder. 4. Run P3D. Is this working ? Report back to me. I not make patch for configure tool! For configuration P3D , follow steps which has offered Jean-PauleM http://forum.avsim.n...60#entry2119760 Also i can not support P3D now because i have not P3D license bit in v2.0 i will support P3D."

Rex essential for weather, nothing for traffic as yet

I took the plunge this week. Using the FSX2P3D migration tool, I have installed the PMDG NGX and FSUIPC. The Orbx migration tool works as advertised, so I have retained my FSX installation so that P3D can get the Orbx scenery. Rex Essential with a P3D key works perfectly. The only tricky stuff I've found is the need to use the migration tool when installing navdata. I'm still trying to work out FSbuild - particularly in relation to the export function. Changing the default fsx location to P3D doesn't change the default "My documents\Flight Simulator X Files" directory to the P3D one. In any event, it's easy to find the exported files in the default FSX locations and to cut and paste into the P3D ones. I managed to get the EZDOK camera working yesterday, courtesy of a fix that you can find here. Scroll down to the 2nd post in the thread by Marnifftar, which has a link to a modified exe and also a link to a bit of cut-and-paste coding that has to be done. It's a bit fiddly, but it works. Note that I didn't find it necessary to rename Prepar3d.exe to fsx.exe. The AoA-recommended camera settings work perfectly. As for P3D, it works just fine. My only gripe is that I can't get the throttle on my joystick to work, so it's F1-F4 atm. All in all, a pretty painless exercise. I've got Win7 on an SSD, with P3D running on a separate RAID5 array. cheers, jeff