slaxor

Yeah, I did and I do and FFBeast Controls are game changer! You may take a look here why: lol see my yellow emergency switch on the floor in the above video. Never used that though...

Check this out. It's already there and I'm already flying it https://ffbeast.github.io/ https://youtu.be/LoItIl4WB3Q?feature=shared FFB support is must have for the aircraft!

The same with Quest 2 controllers. They are just absent as control devices completely. Refresh devices has no effect.

It sounds actually a bit controversial. The worst performance drop in FPS AFAIK we get when playing online missions, e.g. servers like Enigma. My understanding if above was the case then Online servers would be faster than single missions which is not the case. Am I missing something?

Hey guys. I was very puzzled with this situation too but in relation to IL-2. It appears that DCS and IL-2 have the same issue because they are single-threaded. CPU bound scenario occurs at 50-60% CPU load (per core) which sucks. So there is no way to identif/see it because windows will roll thread across all core without any gains though. Actually, the only way to see it is CPU-frametime, for example in fpsVR. Before fpsVR I could not see any reason why I'm not getting 90 fps. Take a look at this IL-2 forum with very good explanation: https://forum.il2sturmovik.com/topic/82991-is-it-worth-upgrading-my-cpu-and-ram/?do=findComment&comment=1256972 It also has a sheet with CPU bound performance (See 1080 test). Basically, CPU performance of both games can be predicted on "Single Core Performance" of a CPU. Dev do have to fix it. It is definitely software problem and it is getting ridiculously critical in achieving 90fps in VR. BTW do we have similar sheet for DCS. I'd anticipate that DCS will be less performant.

The solution to the trigger is here. I managed to go through after fixing it. https://forums.eagle.ru/topic/276498-mission-2-fix-for-missing-trigger/?do=getNewComment

Yeah, I got the same issue. Actually, the mission flow is a bit confusing. After taking off and when on route to NDB 525, ground says enemy aircraft in the air and then pursue them though I could not see them at all and they are pretty far away so there is no way to catch up with those enemy Mig-19s. So the confusing part is should I keep going to NDB or follow them.. actually the only way to do it is to use F10-Map which is kind of cheating to me. In any way I got though I got hit by SAM. However, I did read that S75 can hit only above 3km high so I went low (below 1km) with 6th group and managed to fly close to Tbilisi airfields which are the mission goal. Although, the mission trigger did not work out so mission has not been accomplished. I'm wondering if the mission needs to be update to a newer version of DCS or something.

I've captured video and pretty sure it is at least mix up Mode 1 is Mode 2 and visa versa. The lamp is also not working as per manual and working only when the screen is off (assume it is mode 1). The range of mode 1 is a bit too long 2km instead of 1.2km as per manual. Explained that in the video. https://youtu.be/CA5E4NWQqzs

Yeah, I'm pretty sure. It works in Mode 1 with no issues. I assume if it was not warmed up properly then Mode 1 would not work too, right? Also interesting, that Izumrud Radar indication lamp (Next to mode switch), which as per instruction indicates that Radar is operation correctly, lights up when I switch to Mode 2 but the screen goes off at the same time. The lamp is off in Mode 1 though.

Hi guys, Trying to figure out if it is a bug I am missing something. With radar on and set to mode 2 (above 2000 m altitude) and track antenna (Ar-18-16) is ON the radar screens is switching off. I'd assume that it is main radar mode though it is not working. Anyone has experienced the same or it is known bug? Thanks!

+1