Hilkiah

When you say you can't access the Pro ATC menu, what exactly do you mean?

Try disabling hyper threading in your bios. This is what worked for me. I too use lasso and have gone through soooo many tweaks. Only after disabling HT did I get rid of 99% of micro stutters.

I use Pro ATC

Also got this error too: couatl v3.2 (build 3894) panic log started on Wed Feb 14 22:51:30 2018 problem raised by engine or unspecified addon {'Airport': 'EGLL', 'Requested assistance services at': 'Dock 702', 'User Pos': (51.47416444365317, -0.4299749410914424, 27.7668 m, 2.46876 m, 139.42448031614194)} Estimated number of passengers = 80 Estimated number of passengers = 80 Traceback (most recent call last): File ".\common\addon.py", line 55, in <lambda> File ".\GSX\__init__.py", line 400, in <lambda> File ".\common\youcontrol.py", line 231, in showMenusWithSameTag File ".\common\youcontrol.py", line 86, in showContainer File ".\common\youcontrol.py", line 210, in show IndexError: list index out of range {'Airport': 'EGLL', 'Requested assistance services at': 'Dock 702', 'User Pos': (51.47416444365317, -0.4299749410914424, 27.7668 m, 2.46876 m, 139.42448031614194)}

btw, this is what the couatl log looks like: couatl v3.2 (build 3894) panic log started on Wed Feb 14 22:49:01 2018 problem raised by addon <unknown> Traceback (most recent call last): File ".\GSX\__init__.py", line 400, in <lambda> File ".\common\youcontrol.py", line 231, in showMenusWithSameTag File ".\common\youcontrol.py", line 86, in showContainer File ".\common\youcontrol.py", line 210, in show IndexError: list index out of range {'Airport': 'EGLL', 'Requested assistance services at': 'Dock 702', 'User Pos': (51.47416444365317, -0.4299749410914424, 27.7668 m, 2.46876 m, 139.42448031614194)}

Not sure about the FSUIPC being the cauase. I did some tests and found the following : First I tried removing FSUIPC 5.122 (i.e. moved the FSUIPC4.dll and FSUIPC5.dll from the modules folder as per the instructions), fired up P3D, loaded EGLL and the piper airplane, then loaded the PMDG 737. Let it initilise then tried accessing the GSX menu and immediately got the vanishing menu problem. I exited the SIM, uninstalled ProATC, rebooted and started up P3D to repeat the test...same result. Exited, uninstalled GSX, rebooted and started P3D again and tested this time using Active Sky menu....same result Exited, uninstalled Active sky, rebooted, downloaded latest version of GSX and reinstalled it (so now both AS and ProATC were uninstalled). I then started P3D and repeated the test. It APPEARED to work ok, but then COUATL kept crashing every now and then. However thus far I haven't noticed the vanishing menu with GSX....just the COUATL crash every now and then. Will do some further tests and revert.

Hi Rob Do you have Hyper Threading enabled or disabled? For me I found that disabling hyper threading significantly reduced my stutters and I’ve been running without hyper threading ever since (4790K).

Yes I have a registered version of FSUIPC v5.122. I only use is for the comms switch functionality for my FSL A320X (so it can work with Pro ATC). Stephen (ProATC) suggested trying P3D without ProATC which I will do later tonight. I suspect, however, that it is related to SimConnect which I assume makes the menu work for ProATC, GSX and AS (correct me if I'm wrong). I will uninstall FSUIPC and see if that makes a difference. If it does then great. If it doesn't then I'll trying uninstalling Pro ATC, GSX and AS (in that order) to see and report back.

I have this exact problem. Also happens with the GSX window.

Since upgrading to P3D v4.2 I'm having some weird menu selection issues. The below video shows the problem when selecting the GSX menu (also happens with Pro ATC menu). First time menu simply appears and then disappears a split second later without giving the user a chance to select anything. However an option is selected! Second time, the menu stays on screen awaiting selection. Problem can be replicated a few minutes later. Anyone else seen this?

Everything should be just fine. I updated client, content and scenery. All my addons work just fine and didn't have to reinstall anything. These 2 links helped give me the confidence: https://www.avsim.com/forums/topic/522254-ftx-orbx-scenery-prepar3d-updating-reinstalling-troubleshooting/

Made the plunge Following these 2 guides to the T: All my PMDG planes are ok along with their liveries. My Ultimate Traffic Live works ok (can see AI planes). I fired up AS and ASCA and simply had to install ASConnect. ChasePlane is working perfectly. CRJ workes (with its liveries). The A320 doesn't work (Unsupported P3d version)....but that has already been confirmed on the FSL forum. Can't say much about performance as I haven't done a flight yet. However I loaded up EGLL, LFPG and KLAX both during the day and at night and FPS seems a bit better (can't quantify though). My config remains the same SSAA 2x and High on all other settings. Note there may be issues with Envtex/envshade: https://fselite.net/news/toga-projects-envtex-envshade-issues/ ** edit ** I fired up envir and install my settings to sim (same as before), except the option to use envshade (kept it off0. Then I fired up P3D and it looks amazing. Gonna do some night flying to see if the DL tweaks have made a difference.

I I found the shaders folder....had to restore original shaders in pta! I''m following your updating guide to the T. Also will go throug the orbix guide you posted above....that makes 4 of your posts I just bookmarked!

I read through Poppet's very thorough update guide: He recommends deleting doing the following after an update: ""These actions are recommended But not required Delete the Prepar3D.cfg file and the Shaders folder after you update with the Client Note: This file and folder will generated again when you launch Prepar3D These actions will not effect your 3rd Party Software (Add On's), You will need to readjust your graphic and scenery settings to your preference again via Prepar3D > Options after you delete the Prepar3D.cfg file Right click and delete the Prepar3D.cfg file and the Shaders folder, These will generate again when you launch Prepar3D ----------- Local Disk (C:) ► Users ► You ► AppData ► Roaming ► Lockheed Martin ► Prepar3D v4 - Prepar3D.cfg Local Disk (C:) ► Users ► You ► AppData ► Local ► Lockheed Martin ► Prepar3D v4 - Shaders ----------- I have found my Prepar3d.cfg file, but the shaders folder does NOT exist in the above location. All I have in appdata\local\lockheed martin\prepa3d v4 are: - Controls (folder) - Effects (folder) Prepar3D_Default.fxml (file) Prepar3D_Default.wx (file) Where do I find the shaders folder?

You mean http://fsuipc.simflight.com/beta/Install_FSUIPC5122.zip

Didn't read in in that link...only posted the link to confirm that ORBX is indeed compatible. The last time I upgraded from 4.0 to 4.1 I had to reinstall all my ORBX addons. I think only those addons that utilise the add-on.xml files because they reside outside of the p3d install directory. I may be veryyyyyyyyy wrong, but that is how I understand it. Pls correct me if I'm wrong.

https://fselite.net/news/orbx-ftx-central-updated-p3dv4-2-x-plane-11-compatible/ So do we have to uninstall our entire orbx library ... and reinstall after we upgrade to p3d v4.2?

update...I opened a ticket where the support personnel suggest uninstall, reinstall and disabling FSUIPC (haven't tried the latter). However after reinstalling no difference. The support personnel suggesting using the 2d MFD (instead of the 3d MFD) which apparently does work. Thus I am able to enter a flight plan using the 2d MFD. Does anyone know how to import a flight plan from PFPX or Pro ATC? Thanks. Hilkiah

Hi all, I have a problem where by the flood lights in the FSL A320X vanish depending on the angle I'm viewing (see video below). Also the same thing happens with the taxi lights on PMDG's 777. Does anyone have an idea of how to solve or further diagnose?

Ok Thanks Kevin!

Hi, This is an old topic, but I'm experiencing something very similar. The below video shows the effect with FSL A320X but I get something similar with the taxi lights on PMDG's 777. Does anyone have an idea of how to solve or further diagnose? Thanks. Hilkiah Lavinier

Hi all, I have this weird problem when trying to enter data into the G1000 of the Phenom 300. When trying to enter a value (e.g. an airport), sometimes (i.e. most of the time), the characters keep changing automatically (rapid scrolling through its list continuously). To stop it, you have to shutdown the plane (batt 1+2=off). I am using P3d v4.1. Note I have already changed my mouse and still same thing. Video can be seen here:

I would suggest the 737 or the FSL A320x. Both are quite fun tbh. The A320x seems a bit more complicated but I spend my time equally between the two. Note I also own the 717 which is quite fun, however it suffers from the CTD when switching views.

HI all, Just picked up the Phenom 300 and decided to try a flight EGLL/LFPG. Read through the G1000 pdfs and have some familiarity with the G1000 from the Phenom 100 which I used to fly earlier in the year. My main issue is when selecting the departure most times the airport field keeps rapidly changing...as if in constant scan. The only way to stop it is to press the inner knob, but then I cant use the outer knob to select the departure (as nothing is highlighted). I then have to press the PROC button to to back to the Procedures page. Selecting Departures again does the same thing. The workaround is then to go back to the PROC page and select approach, use the outer knob to select approach or transition, press PROC then go back to selecting Departure. Its as you have to gingerly handle the G1000. I think this was the same issue I had with the Phenom 100 which is why I stopped flying it. Has anyone had a similar experience and is there a way to fix it? I really wanna love the Phenoms!! Thanks. Hilkiah

Darnnn. Thought I was on the exp. channel already. Anyway I am downloading 0.4.41 now (via my mobile hotspot....since hurricane Maria killed ADSL/cable modem access on the island....hence the need for offline mode ;-) Thanks again!!! HL