gregda

I took this opportunity to try the 12 buck upgrade to EZdok 2.0 and am loving it so far. Mouse panning is buttery smooth and the effects are great. I've had enuf of this one for now at least till its stable without the constant intrusive updates that breaks things.

FG Global mesh messed up KDVT which is in the ORBX global airport pack, as well as KTUS which is default. I ran the AFM2 elevation correction tool on both and it corrected it nicely.

Same here with BAD airport elevation problems since installing FS Global Ultimate mesh. Ran the vector elevation tool with no fix. Check KDVT and KTUS for examples. Former is raised above surroundings and latter is sunken...and have never seen before and I fly a lot in these areas.

I'm trying to run the networked setup, but it gets stuck in 'Initializing'. On the server side, the client connected and server running messages are green, and server connected is green in the network client on the sim computer, but when 'Enable'ing in the sim the 'Test..test' voice is heard but it just stays 'Initializing'. Anybody else having this?

This is some good news! My favorite twin piston and can outfit it with the GTN750 too!

I'm comparing to another (unnamed) mesh product I currently use, but I found the best way was to just fly around in areas you know well and it should be obvious. Around Phoenix, Camelback Mtn truly has a more 'camel like hump' visible, and Four Peaks is incredibly rugged with sharp peaks and ridges compared to the slight roundness from the previous mesh. Loving this product so far!

Has anyone else had problems getting the GTN 750 installed? I run the PA28Switch utility and select 'Flight1 GTN 650-750 Model' and it is also showing installed in the GTN configurator, but no GTN 750 in the VC.

Be careful with Pilot2ATC if you think a PC reformat is possible. Couple of us reported license registration issues on the forum after reformatting and the developer is eerily silent...though has been active answering bug reports. Not trying to bash...but thought this may get his attention if he sees it. No biggie though I'll just stick with PFE otherwise.

I just found this also. My Windows 10 got into some unrecoverable state so i had to reset windows. There has to be a way to resolve this right being this is a common issue?

Thank you Greg. I missed the extra step to select Menu again after Catalog.

Sorry to revive an old thread, but could someone that has uploaded the .gfp Garmin flight plans in into the GTN 750 give a few steps on exactly how it is done? From the "Creating Flight Plan and User Waypoint Files for the flight 1 GTN.pdf" guide from flight1, it says to select 'Flight Plan' -> 'Menu' -> 'Catalog' -> 'Import' then the list of .gfp flight plans will show. But there is no 'Import' button! It is the same in the GTN trainer itself which I guess is expected since they should be the same. I am very perplexed by how you guys got yours uploaded. The .gfp was generated from Little Navmap. Thanks for any help...appreciated... Greg

Wow I have the same thing! It seems to happen at transitions between snowy and non-snowy areas and is was wandering the same. Unfortunately, I have the feeling also the land-class 'blocks' are just that so gives that aweful look.

Flight Plan Go will.

Literally got chill bumps looking at that pic...my brain cannot distinguish it from reality. Well done!

Is anyone having problem with version 1.04? As soon as I select 'ON' from the xEnviro menu dropdown X-Plane locks up then crashes.

Not sure this is the same but my download of the libraries are extremely slow and it keeps timing out and asking if I want to continue the download. If I select 'Yes' or 'No' a huge page of errors appears. This is some progress as we are all tied to the 'mother ship' now and at the mercy of her moods.

Um no this is not an opinion. When clouds are rendered as studdering razor thin slices in the sky when flying near tham, this is clearly a product not ready for prime time...and certainly not worth a $70 beta. That being said, however, the long distances visualls are stunning. I can't get past the close up clouds though so it will be shelved until improved.

Yes! It is 'EZDOK' of X-Plane but much better and without all the hassles.

Yes just got this same error on a flight from KPHX-KTUS...right after i landed the error happened and with a screen listing the error. Could not close the screen so had to kill the X-Plane process to exit. Hope they fix this soon!

Thank you Adam. I am enjoying your previous preset and look forward to trying this one.

Agree also from Bob's comments I just tried the PF3 demo version and VFR flight is very immersive just like I remember ATC getting my PPL.

Hi Bob...thanks for the command line as this is definitely the way to go for me also (less clicking and opening things). But I can't get AS16 to launch. I hear a 'bong' then P3D launches normally. I copied your lines to the .ini file exactly. Anyway I'll keep trying as there's not good reason I can see it shouldn't work. Thought it might be spaces in the path string but yours works. Thanks, Greg

Bob...the only affinity related info in Task Manager I can find is in 'Details' then right click to 'Set Affinity' which shows all LPs being in use. I can't find any place just to see the currently set affinity, or is this the affinity in use also? In that case the .bat file isn't working. Here is the command I'm using based on Steve's link: start /B "" /affinity F8 "C:\Program Files (x86)\HiFi\AS16_P3D\AS16.exe" Thanks Greg

Steve...I have the .bat file running and it launches 'FSWeather', but how can I verify the correct affinity (248) has been applied? Process Lasso (which I'm trying to get away from using with the .bat) still shows all cores (0-7) being used. Should I just ignore Process Lasso and assume it is runnning on 248 LPs, or is PL overwriting the affinity set from the .bat file maybe? Thanks!

Steve...I'm wanting try your recommended AM of 253, but have a question on allocating AS2016 (or 'addon exes' in general if you like). I noticed improvement in AS2016 when going from having it using 8 LPs to only LP 0, 1 and 3, and allocating P3D to 2 and 4-7. But this is giving me blurries now. Based on above don't think this is correct as P3D needs the 1st core (and only one LP of it) to run best? So given that the AS2016 documentation says don't spread it out over too many cores due to latency concerns, how many and which LP cores would you recommend to run so it operates best with P3Ds 253? Thanks for your great explanations of this complex topic...hopefully I am understanding it better now.