ASW?

[njaynl]

Hi Guys,

just updated to 1.7 with oculus 1.10.

how do i activate asw ? because the simulator will show 25/92 when at an airport and in the sky it goes to 45/92 ... shouldn't asw be /45?

[admin]

Oculus ASW requires a constant 45fps or higher to work correctly. Because if this, if your FPS drops below 45, FlyInside disables ASW. You'll need to tune your sim to reach 45fps at an airport if you want ASW at that airport

[njaynl]

Aah clear ! thx

[jimh20]

Oculus ASW requires a constant 45fps or higher to work correctly. Because if this, if your FPS drops below 45, FlyInside disables ASW. You'll need to tune your sim to reach 45fps at an airport if you want ASW at that airport

Hi Dan,

I've just seen your explanation. If Flyinside disables ASW below 45 fps, then the problem I have since the latest Oculus update must be something else.
As advised when originally setting up Flyinside, I have P3D limited to 30 fps, and have been seeing a steady 28 fps outside of areas such as London or New York. I have a high detail configuration in P3D for all low to medium density areas and see a steady 28/93 in Flyinside for months past.

Now I'm seeing fps as low as 9/24 with nothing changed in Flyinside or P3D. I've now re-configured P3D, no traffic. no lighting nor reflections, extremely sparse scenery, stripped down to far lower than I would wish. In Flyinside I now have 24/73, and it's flyable.

People in Oculus forums are up in arms about this latest Oculus update. I don't know whether Oculus can do something which will get me personally back to where I was, or whether it will fall to Flyinside. I know you are on your own, Dan, so everyone like me will have to be patient if you are going to be our saviour.

Sorry about the long post. I just wanted to make my situation clear.

Best Regards, Jim

[admin]

Jim,

Could you check whether reverting to FlyInside 1.62 from the website, and then using Ctrl+NumPad1 to disable ASW makes a difference? I've been trying to track down a possible performance regression in 1.7.

Thanks,
Dan

[Britjet]

I did try a re-install of 1.62 and it didn't seem to make any difference BUT back with 1.71 I am now finding that I CAN change the ASW setting by using CTRL and NUMPAD 1 - it doesn't seem to be a toggle back and forth but as soon as I use the keys the frame rate shoots straight back to 90 or so and basically stays there, no more reductions to 45. I haven't done any registry hacking at all.

There is no doubt as far as I can see that in a fast PC if you are flying in a high impact area that it is better to have it switched off. For example I just flew over the Manhattan V2 scenery at highest density with initial startup, and all I got was 45 fps, all the time. Then I used Ctrl and Numpad 1 and it shot straight up to 90 and stayed there for an hour..

FWIW..

Brit.

[jimh20]

Hi Dan,

I'm back on 1.62. Registry hack ASW enabled. In Oculus Home press Ctrl+num1. Enter Flyinside-P3D, press Ctrl+num1.
The key combination seems to work, and the results are better with 28/65 in Flyinside. These figures are with P3D graphics at my "Very Very Very Low" settings. If I change up to merely my "Specially Low" settings the figures plunge to 11/30.
I repeated the sequence, pressing Ctrl+num4, with very little difference.

Brit can use Ctrl+num1 to regain his 90fps, while I can only reach 65fps at best, and only with extremely low P3D settings. I am becoming convinced that I have suffered something in addition to, and simultaineously with the introduction of ASW. Previously I had a steady 28/93 with very high P3D settings. I don't want to be posting about ASW woes, and clouding the issue with some problem unique to my sytem.

Would it be sound advice for me to do a complete re-install before further comment on the present ASW conversation?

Jim

[jimh20]

Problem solved by reverting to nvidia driver 172.90.

Jim

[Tony]

Hope you mean 372 lol

Tony

[jimh20]

Driver 172.90 was the latest version in 1816.

I really must look at what I type, but right now I'm too happy to care!

Cheers, Jim