targetpractice2

Any way to turn off the transparent background? For me its awful. The writing is yellow and blurred now and very difficult to see when on top of other applications, it now looks like its got a submit button but its the forum submit button.. not a fan Im afraid.

just update on this, for me its fsuipc / p2atc order of loading that impacts it.. so just have to load fsupic a couple of times for it to connect after I load p2atc, it doesnt see it if I load it first.

Thanks for the message, 1 - 7 everything as suggested.. it actually connected once last night and I was able to use it ... weather was set to NOAA yesterday and tried different today. I launched this morning and again would not connect.. however I restarted FSUIPC 7 and it connected right away so it appears that there may be some disconnect for me depending on the order I start the various programmes. Will update accordingly, thanks for help.

I am using Win10 MFS 2020 . With a trial version of P2ATC. I am connected to P2ATC with FSUIPC 7 with Simulator Connected and com1 nav2 and power button green (although Im using a320 neo FBW which didnt recognise the buttons so assume that just an indication of the checkboxes in p2atc) I have US English installed as the default language (I assume no need to change region etc for the PC itself) I have run P2ATC in administrative mode I have used call sign beech and no. N431VB, as an airline and as GA, I have tried the call sign EZY 255 However only seeing Simulator Connected line in right hand box. Error message when selecting freq.. Aircraft position not found. Successfully filed a flight plan. Not sure what to try next other than a reinstall of p2atc. tks

SLC.. knowing that its his 10 year old daughter doing the cabin calls is funny, she did a great job.

found my house..the area is pretty accurate ... even showing the waterworks although it looks like a bunch of swimming pools... I might invest in a modelling crash course!

I am ashamed ..but now flying and guess what trying to find my house....my god it looks good though.

lmao I figured out what I was doing wrong... I was assigning my joystick as a button rather than an axis in the settings.... the sensitivity was exactly what I was saying ..so user error...its stupid but easy to do ... you may not be as dumb as me but for those that might be having the same issue... make sure in setup under your game controller that you assign throttle, elevator, rudder and aileron in AXIS .. not for exampe (aileron left (roll left)....

I havent been able to take off in the cessna yet because of control surface sensitivity.. but it seems to act like a press of a button not a smooth axis.. If I quickly pull back and not hold it (as if pressing the button once), it moves out slowly and stops.. if I pull back and hold it the sensitivity sends it through the roof and immediately into a stall.. but in each case I have to move the joystick fully to get any movement at all. Its the same with the throttle ..it doesnt move until fully pushed to top. However the rudder reacts immediately .. but when I go into sensitivity it is reacting as it should i.e slowly moving as I pull back or push forward on the joystick

Thanks for replying guys...I did check majestic forum (have not posted there yet) that specific issue looked like it was a key mapping issue to switch the autopilot on/off. (I don't do that) ...the other was a calibration issue using the majestic profiler..I'm using fsuipc...I'll jump on there....

Hi, am an avid user of the training vids think they are fantastic and will be dipping into the most recent soon (cant wait for 737 or airbus)..anyway. I have one issue which will not go away.. I use Saitek yoke/throttle/pedals configured through FSUIPC (latest version).. have also the latest version of the majestic dash8.. On approach and disconnecting the autopilot the plane becomes almost uncontrollable without a fight, yawing left and right and nose has a distinct drop ..I appreciate that it has a slight drop but this is down and right/or left I have followed and also viewed other landing vids and no one seems to have this problem (all looks very smooth with small adjustments on disconnect). Things I have checked:- Yaw Damper.. is on I click autopilot off with mouse don't use assigned z key etc Elevator trim is at times out dramatically during the landing phase and given I am coming down on a 3 degree angle seems odd should the autopilot be moving the trim so far out of sync prior to landing? The aileron trim appears centred. FSUIPC is calibrated.. Weather no turbulence and wind is sub 10 knots. (I use FS Global).. The only thing I can think of is the weights and balances but all are within tolerances however it is perhaps the cargo /baggage positioning (front to rear) rather than the weight? I also configure through FSUIPC and it appears the flight controls tool supplied by majestic never works (no movement).. so should I type in certain tolerances into it or is FSUIPC over riding this? So it sounds like something is out with my calibration of yoke / pedals or I am doing something wrong in the setup for landing .... Lastly I started practicing with FSIPanel but find that I end up with the same result... no matter what I do... any help would be much appreciated. tks

I had a similar issue and started another thread where EZdok would not find the steam path correctly in the users folders.. the solution unfortunately was to do a complete clean and re-install of my OS. Which was also mentioned by another user. When I installed Steam on its own then EZdok 1.18 (after 1.15 ) it worked .. I only got one option (steam) vs the usual two

I have done a full re install of OS, after cleaning registry there was still something there that EZdok did not like and was continually looking for the FSX route.. complete clean and reinstall of my OS and EZdok worked first time.. normally it would give me two options to click on FSX Boxed or FSX SE.. now on install it just provides FSX Steam option... its fixed now.. pain in the rear to do but solved the issue..

I have updated to 1.18.6 but I have exact same problem.. however it still works it appears in my addons . I have yet to put in new cameras however. but still have the issue where it cannot write to the folder as the folder does not exist... apparently the only time the FSX-SE folder would appear is where you are running both FSX and SE versions on the same system. So where you only have steam edition it only creates FSX folders in the same way as the old boxed version.. would suggest the EZdok is looking for a file that will not be there for the camera.cfg .. no idea if EZdok can be changed to point to the correct USERs folder... Ok it actually does not work now I have tested.. just keeps crashing FSX.

Hi did a full uninstall and cleaned the registry etc.. have a clean version of SE now on the system. no addons.. have tried to install EZdok and once again its looking for the FSX-SE/camera.cfg file which does not exist as FSX-SE creates an FSX folder in USERS not an FSX-SE folder (due to only one version being on the system).. on reading some other forums this is the norm where there is no FSX on the system. So it may have worked before because I had two versions of FSX on the system and if you do, FSX SE create a folder called FSX-SE apparently.. could not find it though.. so I am thinking there must be a way other than changing the name of the folder to FSX-SE to point the EZdok installer for the camera.cfg at the FSX folder... cheers