Operation "Blue Flag Normandy" - 24/7 WWII PvP Campaign - ROUND 1

[JallieFR]

not available to participate today

 

computer crashed every time I asked for REARM on the P-51 ( in VR )

[xcom]

awesome stuff Schnarre!

[Schnarre Aggro]

not available to participate today

 

computer crashed every time I asked for REARM on the P-51 ( in VR )

 

 

i heard from several sides, that VR is broken in this patch for 2.1

[mia389]

I am going to have to get Normandy very very soon

[Schnarre Aggro]

Wait for a bundle with the ww2 assets, without this, youre not able to join most of the ww2 servers ;)

[xcom]

Update -

Server graphic settings have been lowered to allow for better FPS for anyone joining.

Please try it out and let us know how it goes!

[amazingme]

Hi! It seems a little bit better upon joining an aircraft.. the freeze is still there but shorter in time.

[Schnarre Aggro]

1.good morning

2.did you make progress on the "tf51 cockpit issue workaround" already ?

3.i will try the grafixsettings later this afternoon

4.have a nice day :)

[Schnarre Aggro]

performance increased pretty good .... was able to get the same FPS as befor BUT with groundclutter, flat terrainshadows, better groundtextures and even some more trees and smokedensity(chimneys)

 

i like :pilotfly:

[Schnarre Aggro]

i normally dont do tutorials, but when i do .... its horrible :D

[lemoen]

I modified my TF-51 last night to have a transparent windows. I unzipped the cockpit textures file for the TF-51 and for the P-51, then I copied the cockpit-refl and cockpit-normals (and maybe one more, you'll see the P-51 has some extra files, copy these) into the TF-51 folder. I renamed them to be tf-51-blahblah and I zipped the file again. That worked for me, I can now fly the TF_51 on Blue Flag Normandy without setting my head position all the way up and left/right :D

[xcom]

I heard some lags tonight, would like to hear feedback so we can identify where it is coming from.

[Schnarre Aggro]

I saw some lag/warping as well, but is wasnt all the time and not with every aircraft ... Cant say more, havent checkt the amount people nor the ping ... Sry cant help much

[Coxy_99]

I heard some lags tonight, would like to hear feedback so we can identify where it is coming from.

 

I found they were stutters, From the messages at the start, Did notice abit of warping later to.

[voodooman]

im getting lower frames in the server than other servers, like in burning skies. i have vsync enabled and i stay 60 fps on other servers, in blue flag server i get around 45 fps.

 

max cpu core load was 77%

max gpu usage was 80%

max gpu memory load was 7562mb (out of 8165mb)

max ram usage was 7550mb (out of 16000mb)

max pagefile usage was 13633mb (system managed)

 

i find that odd since these are same usages i get flying in burning skies.

 

edit.

tried with v-sync off on both servers. blue flag and burning skies.

blue flag fps was the same as mentioned before, around 45-55fps.

burning skies on the other hand i got 75-85fps. max gpu load 100% even avg was above 90% all the time.

cpu load was higher in burning skies, i believe due the higher fps. i got 2(!) cores loading avg 65%, their max loads were 93% and 94%

 

why isn't my system getting the same loads in blue flag?? about the same amount of people in both at the time of testing. strange..

Edited August 1, 2017 by voodooman

[xcom]

I modified my TF-51 last night to have a transparent windows. I unzipped the cockpit textures file for the TF-51 and for the P-51, then I copied the cockpit-refl and cockpit-normals (and maybe one more, you'll see the P-51 has some extra files, copy these) into the TF-51 folder. I renamed them to be tf-51-blahblah and I zipped the file again. That worked for me, I can now fly the TF_51 on Blue Flag Normandy without setting my head position all the way up and left/right :D

 

 

 

Thanks lemoen!

 

here is the fixed file for download - http://89.163.173.82/DCS/TF-51D-CPT-TEXTURES.zip

 

copy the file and overwrite in - DCS World 2 OpenAlpha\Mods\aircraft\TF-51D\Cockpit\Textures

[xcom]

I found they were stutters, From the messages at the start, Did notice abit of warping later to.

 

Thanks we are checking.

 

im getting lower frames in the server than other servers, like in burning skies. i have vsync enabled and i stay 60 fps on other servers, in blue flag server i get around 45 fps.

 

i find that odd since;

 

max cpu core load was 77%

max gpu usage was 80%

max gpu memory load was 7562mb (out of 8165mb)

max ram usage was 7550mb (out of 16000mb)

max pagefile usage was 13633mb (system managed)

 

these are same amounts that flying in burning skies, exept cpu load was higher (in BS it's about 65% max) but nowhere near being maxed out.

 

just curious, is it the sripts that are running in the server? seems to me it's a server side issue...

 

It is probably related to the amount of units in the mission.

We are going to try and help the FPS even further.

[Schnarre Aggro]

server down

[xcom]

up

[Schnarre Aggro]

down ...didnt come up after normal 3hour cycle

[JallieFR]

tried to connect two time this afternboon

 

DCS VR crash , evry time ...

[lemoen]

tried to connect two time this afternboon

 

DCS VR crash , evry time ...

 

 

Tooltips switched off?

[xcom]

Yes, we have an issue with the restarter that we are attempting to resolve.

Once the round starts this should be settled.

[JallieFR]

Tooltips switched off?

 

Yes Lemoen ; of course since the 2.1. last week update

 

into my DCS --> Tooltips is switched OFF

 

no problem to fly solo ... only on OnLine with this options not OFF

Edited August 3, 2017 by JallieFR

[Pheonix0869]

I concur with JallieFR, same issue... crash with local tool tips off. I think the server may have them enabled, or if not restricted the server maybe enforcing the tool tips from the hosts main settings. I think under "game-play" there is a check box that says, use these settings yada yada. This would override tool tips preferences in the mission unless the host DCS instance unchecks that box. However this may also be an unrelated 2.1.1 VR bug. I was really hoping for a fix today...