#Process lasso fsx windows 10
#Process lasso fsx Pc
#Process lasso fsx windows

One interesting comment someone made was that P3Dv3 worked better. If it was my computer or graphics card DCS would bring the FPS to its knees. It has been the case with the new 2.5 version as well as previous Alphas and Betas. Even with shadows and water on DCS is excellent. I can fly DCS ships in very high settings in my Oculus Rift with excellent results. The framerate never changes whatever I do high/low - whatever. I'm familiar with all the graphic sliders in P3D and now Flyinside. I've been using P3d for many years and flight sims since they came out in the early 80's. I understand the big impact CPU and sceneries have on FPS. My biggest concern is that I HAVE set ALL the sliders in EACH app to the lowest setting possible, then the HIGHEST levels and and the FPS is always the same. These are all great replies! Thanks so much for taking the time, really.

I find FI to be able to handle the 30 FPS it needs quite well and my experience is very good.

#Process lasso fsx Pc

Oh I also included my Active Sky settings but remember I use a networked PC for that. The spreadsheet is connected to a Dropbox link that hundreds of people have downloaded from.

I also setup profiles under graphics and switch to each depending on how I’m going to fly that session. Here’s a link to a post I made on the P3D forum where I created a spreadsheet to track settings for monitor, Native VR, and Flynside flying this way you can see or share how things differ when optimizing for each type of flying. Also I run Active Sky off a client PC since it can be too demanding on the host PC. I find Flightbeam airports to be less FPS demanding.īottom line you have to turn eye candy down and I and others find Process Lasso indispensable to set CPU useage and priorities which help the demand on the first core tremendously. I only run Orbx Base and Land Class and a few airports like KSAN but go into the setup tab for that airport in FTX Central and turn some stuff off. I have pretty much all the Orbx stuff but have found through a lot of testing the worst offenders are Orbx Vector and Orbx Regions because they deploy everything (base, land class, and vectors within them).

Another thing is that Orbx sceneries can be very hard. Settings are key particularly autogen buildings and vegetation, dynamic lighting, shadows and others obviously. The use of Process Lasso, an addon optimization tool, also helps greatly. I have a system similar to you but have a CPU clocked to 4.5, the CPU clock speed is the critical link to FPS in P3D. The framerate is STUCK at 18-20fps! I've read just about everything to fix this, reinstalled both P3d and Flyinside.

I have tried lowering ALL the settings in BOTH P3d AND Flyinside. Flyininside is showing 18-20 FPS in just about any area of Orbx areas. Anyway, I have a work around for the time being, but am willing to try anything anyone might suggest, I will make a image of my HDD so I can restore if it gets broken again.I have P3dv4 running on a computer at 4ghz, overclocked i7-4790 CPU, 32gigs ram, GTX-1070 graphics card. I understand it is a small set of people who have this problem but there has to be something in common. Also, Spad>next has no bearing on the issue as I can load or not load it. The problem occurs with or with out the second computer powered up so I don't think it has anything to do with that. I use Spad.Next and simconnect on a second computer networked on the same AD server, I use this for running AirHauler, and Active Sky.

#Process lasso fsx windows

I7 6700K CPU, 32G memory, Gforce 970 GPU, Samsung SSD EVO, Win 10 build 1703 administrator rights on a networked AD windows server 2012R2 with roaming profiles, but my documents folder is maintained on my FSX system.

#Process lasso fsx windows 10

Could it be something to do with windows 10 and permissions or security settings? I am using the latest version cant remember the ver number. What about simconnect could that be causing the problem? Maybe an earlier version would. I can't help but think it might have something to do with the camera sets, or maybe the order that EZCA loads, that is to say if it was to load last after everything else loads or maybe be able to load EZCA after your in the cockpit. I have tried launching the C207 first and I get the lock switch to C172 still locked, even after restart, switch back to the C207 still locked and restart does not clear.

If I switch back to the default C172 the lock stays clear. If I then switch planes to the Alabeo C207 and restart application EZCA the lock goes away and everything works fine. What i have found out as of late yesterday and again today is that if I load the default C172 I get a lock. and over the weekend I was able to reload windows and FSX with the acceleration pack and the SDK's. Well, I now have a week to play with this.