October 8, 201510 yr Author I gave up. I have clean v3.0 install, no traces of v2.0 and nothing helps 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
October 9, 201510 yr Hey G-Y, If you are starting from scratch, you have to fool EZdok into thinking you are installing the product into FSX; for the install of 1.15 and I think also the 1.17 update. Once you've updated to 1.17, you can download 1.18.x and copy it over the installation. Then you should be able to run the configurator, which will really clean things up. I'll uninstall EZdok, and reinstall it clean into P3D v3 and if I'm successful, I'll let you know how I did it. Regards, Graham Derreck CYMM
October 9, 201510 yr I didn't watch the video or read the simforum post so this might be the process they discuss but... 1. Install 1.17 2. Download and copy/paste/overwrite the 1.18 beta files into program files (x86)/ezca folder (as per v2.5 instructions) 3. Create a dummy folder called Prepar3d v2 next to your Prepar3d v3 folder in users/appdata/roaming/lockheed martin 4. Open users/appdata/roaming/lockheed martin/prepar3d v3 and copy the camera.cfg and controls folder and paste them into Prepar3d v2 dummy folder. 5. Run the 1.18 EzDok configurator. 6. Copy and paste the camera.cfg and controls folder and newly created exe.xml back into Prepar3d v3 overwriting the files 7. Enjoy Six steps takes less than a minute. I recommend backing up your camera.cfg and controls folder first. Ryan
October 9, 201510 yr One note: before install of 1.17, you need to install 1.15 out of the Software Wrapper file for EZdok from Flight1 Regards, Chris -- PC: Intel 13900K, Gigabyte Geforce RTX 4090, 64GB Fury Beast DDR5 RAM; Display: Varjo Aero VR
October 9, 201510 yr Author Ok - two steps forward, one step back. I was able to install EZDOK into P3Dv3.0 (clean install into new SSD). Now EZDOK is loading together with P3D, but neither VC, nor side cameras work. The joystick and the mouse are both dead and non-responsive. I also added section "201" camera definition into my aircraft.cfg, but I received an error message upon exiting from P3D about duplicate cameras. Would appreciate suggestions. 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
October 9, 201510 yr Author I think i know the reason of my troubles - for fresh v3 install I had to reset F1 licence. Will check it tomorrow In the meantime, i ran into troubles with modifying the original P3Dv3.0 cameras.cfg file and I would REALLY appreciate if someone post the default cameras.cfg content here. It must contain 20 positions. There should be no traces of EZDOK camera at all. Thank you in advance. Dmitriy 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
October 10, 201510 yr Hi all, I understand the described step-by-step to install EZDok that was working in 2.5 over to 3.0.The problem I have is, while there is a exe.xml file in my 2.5, there is no such file in 3.0.Camera.cfg are there for both 2.5 and 3.0 What do I do about the missing exe.xml for 3.0? Kay Nemoto Prepar3D version 3Win7-64 bit
October 10, 201510 yr Hi all, I understand the described step-by-step to install EZDok that was working in 2.5 over to 3.0. The problem I have is, while there is a exe.xml file in my 2.5, there is no such file in 3.0. Camera.cfg are there for both 2.5 and 3.0 What do I do about the missing exe.xml for 3.0? If you have FSUIPC4 you could try copying this into the Config file. :- [Programs] Run1=READY,"C:\Program Files (x86)\EZCA\EZCA.exe ( acknowledgement to the member who first posted this ) bob
October 10, 201510 yr Bob, Thank you, hmm this is new. I do have FSUIPC4 installed. Which config am I to add this? Kay Nemoto Prepar3D version 3Win7-64 bit
October 10, 201510 yr Bob, Thank you, hmm this is new. I do have FSUIPC4 installed. Which config am I to add this? the fsuipc4 one in the 'Modules' folder. bob edit just add it at the bottom.
October 10, 201510 yr Bob Maybe a dumb question, but do I configure my aircrafts again for 3.0 using EZDok's configuration? I had it done for 2.5 and wondering if I have to do it again or what I did for 2.5 gets carried over automatically. Kay Nemoto Prepar3D version 3Win7-64 bit
October 10, 201510 yr thanks Ryan used to have to manually start ezdok every time.now autostarts. cheers steve REX SKYFORCE 3D steve howlett
October 10, 201510 yr I think i know the reason of my troubles - for fresh v3 install I had to reset F1 licence. Will check it tomorrow In the meantime, i ran into troubles with modifying the original P3Dv3.0 cameras.cfg file and I would REALLY appreciate if someone post the default cameras.cfg content here. It must contain 20 positions. There should be no traces of EZDOK camera at all. Thank you in advance. Dmitriy This is from cameras.cfg in V3 [CameraDefinition.202] Title=EZdok universal world camera Guid={607C4520-CA6F-4135-AE10-8BF288380691} Description=EZdok universal world camera Origin=Fixed SnapPbhAdjust=Swivel SnapPbhReturn=False PanPbhAdjust=Swivel PanPbhReturn=False Track=none ShowAxis=No AllowZoom=Yes InitialZoom=1 SmoothZoomTime=1 ShowWeather=Yes XyzAdjust=True Transition=No ShowLensFlare=TRUE Category=Custom ClipMode=Spot PitchPanRate=30 HeadingPanRate=75 PanAcceleratorTime=0 HotKeySelect=5 cyclehidden=Yes FixedLongitude=37.910548752051 FixedLatitude=55.4228687612085 FixedAltitude=54.9846757716455 Michael Moe Michael Moe
October 10, 201510 yr Bob Maybe a dumb question, but do I configure my aircrafts again for 3.0 using EZDok's configuration? I had it done for 2.5 and wondering if I have to do it again or what I did for 2.5 gets carried over automatically. Prior to ver 1.18 you had to run the config utility for every new aircraft, in the new ver 2.0 it isn't necessary unless you are setting up for the first time. However all I did for P3D v3 was to copy over the [CameraDefinition.xxx] (files .201 - .203) and put the program call up into FSUIPC4 config file. if you now run the EZdoc utility it will put the necessary input into the exe.xml file, therefore you will have to decide to go with the FSUIPC4 program run command or the exe.xml run command. bob edit if you don't have an exe file it should set one up.
Archived
This topic is now archived and is closed to further replies.