Icebeat

nope but thanks

do you know if the wheel input is analog or encoders? what happens when you pressed two buttons at the same time? could you dim the backlite ? Thanks.

throttle without detent?

HP has licensed Valve lenses but Valve lenses are significantly bigger and are canted outwards by 5-degrees

The thing is, The Valve's Index doesn't have this problem, the Image consistency is the same across the screen. I think they are only using valve speaker but not the lenses.

I just removed the face gasket and use the face padding of my old HTC vive, the Fov increment is similar to Index now.

I honestly find very difficult to control the Viper in ground (Take off and landing), I dare to anyone to maintain the plane straight during take off, it is impossible.

Conspiracy theory: ED needs to finish the F-18 before they can announce their new secret EA module otherwise navigators are going to be very angry.

Congrats, this is a fine work! Add some G-seat motion cues and it will be perfect.

I have the same problem. I found the error in my log: 2020-11-07 05:31:26.965 ERROR Lua::Config: load error Config/main.cfg:[string "C:\Users\xxxxx\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:5: '=' expected near 'there'. After removed the autoexec.cfg the communications menu is working again. Try rename your C:\Users\xxxxx\Saved Games\DCS.openbeta directory and see if the problem is configutration

After the last patch DCS 2.5.6.57264 Open Beta, I can not open the communications menu with any of the planes, (I tested F16, F-18, F-15). I tried with easy radio and normal radio options, and I used '\' and Com 1, Com 2 of each plane. without the radio menu, the game is completely unplayable. I found the error, my autoexec.cfg was wrong: 2020-11-07 05:31:26.965 ERROR Lua::Config: load error Config/main.cfg:[string "C:\Users\ice_b\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:5: '=' expected near 'there'. Close it.

MSAA and flat shadows are hardware techniques and shouldn't tax the cpu. Given that the GPU is a freaking monster, he should have this for free.

The problem is not Vulkan or how slow the engine render (actually it is not bad), my Index at 150% running on my 2080ti give me a stable 90 fps in single-player (install dogfight maps), but if I load some scripted map/mission or multiplayer, the game goes to 35-45, the gpu has nothing to do here because the units are not even visible. What is happening here is that the CPU is wasting time calculating whatever ED decided that needs to be calculated in the same thread. Why the game decided that the pathfinder of a unit miles away every cycle from me needs to be calculated in the same thread all the time, I don't know.

I don't know if this is good for us.

:thumbup:

I will recommend to everyone thinking in pull the trigger to wait until October 28, AMD is going to show their new graphics cards and NVIDIA is going to announce the 3060TI and 3080 with more memory (this is a leak).

I am able to refuel the F-18, it only took a couple of days to learn it. The physics of the basket seems to be a bit unpolished.

just wait a bit. https://www.tomsguide.com/news/new-nvidia-rtx-3080-upgrade-just-leaked-and-it-could-crush-amd-big-navi

skip DCS BIOS and just use MMJoy2 easy and pain less

+1.

:thumbup: +1, DCS needs to fix their CPU's problems first or the bump from 2080ti to 3090 is going to be marginal.

No anymore,https://www.theverge.com/2020/4/1/21203414/activision-wins-humvee-call-of-duty-trademark-infringement-lawsuit

is that a real seat?

:thumbup:

I fixed the problem deleting _download and backup folders in my DCS World OpenBeta and launching the updater again.