RealDCSpilot

No surprise to me. And these are no private matters, it's about professionalism. I totally understand each of the team members who had to choose to leave.

You have to bring the hardware of course. Next year comes the 5090... However, i'm currently running 4Kx4K per eye as render target with the PSVR2 (DLSS 2776x2832 -> 4164x4244) with DCS settings on max. Getting 50-90 fps depending on the situation (depends on airframe and close to ground or not).

Sad.

Yeah, definitely hold your horses on this guy. However, this HMD is real and i actually think that ShiftAll will deliver this time. And this is actually the first time i'm really convinced that this is the form factor of the future. It's all i want from a VR headset: small, light, good resolution and FOV. It still will take a couple of years, but yes - this is the way to go. No more bulky bricks on foreheads. Go go go MeganeX (XX whatever). The Beyond couldn't convince me because of the small FOV, but the future looks good seeing two companies working in the right direction already.

Only possible with H.264 atm but at least you have the option. I tested this only with other VR games. I'm back to wired PCVR with PSVR2.

Some Vulkan .dll files already sneaked into the /bin folder...

With a good USB-C 3 cable you can get a 1000 mbps connection with it. Looks very good in terms of compression quality and sharpness. Definitely worth a try.

S76 is just a bit more than half the weight of an AH64 Longbow. When it comes to maneuverability it really depends on each type and it's construction how it can and will react to inputs. Different models are very different on how they react to control input. It's design, specs and usage that define the end result.

A lot of the hardware is more advanced and newer than in the Q3. Wifi7, the iToF 3D sensor, bigger amount of LPDDR5 RAM, Bluetooth 5.3, 32 MP cameras, Quick Charge 4.0... It's the overall much better device.

Just to add: "Without springs and FFB" is for mechanical joystick/cyclic bases like the Komodo Base with hydraulic dampers or simply modded joystick bases with their springs disabled/removed.

PSVR2. When i need screen recording i use the Pico 4 Ultra.

Don't forget that the CPU/GPU is up to 2.5x faster than in the Pico 4. Since VD and Pico Connect do VR compositing on the HMD, this process also benefits from the performance that the Snapdragon XR2 Gen2 provides. All in all the Pico 4 Ultra is a great upgrade. (However, i'm back to wired PCVR with the PSVR2)

The problem is that they forgot to add trimmer modes for pedals. They now run on central trimmer mode which is totally counter intuitive to realistic helicopter flying. Usually, each helicopter in DCS has trimmer options for pedals too in special options. Why they did forget this for the Chinook is a mystery for me. Atm the module is kind of unflyable for me.

Having FFB now is nice, but we also need the pedal trim disable option like in the other helicopters as well. It makes flying with FFB totally unnatural if you have FFB trim on the cyclic but the pedals act like the central trimmer mode and always need to be re-centered after trim. I have the Virpil ACE pedals with damper and my usual pedal use for choppers is holding them in position as needed manually with my feet.

You still not understand. If i could bind the VR spyglass zoom to an axis and just move the lever from 0% to 5% or something, i could demonstrate the issue perfectly.

I have my doubts. The appearance of the moon in my headsets leads to the conclusion that something is off. First suspect is a slightly bigger rendered FOV than the screenspace demands for being 1:1 with real world perspective.

No, this doesn't affect any far away object. Rendered FOV is something very different than eye distance.

Sadly this only works for 2D monitors, for VR there is no option to access such a setting.

Don't know but... It seems that you have only 6 cores assigned to the game. IO cores: zero. This is how it looks like on a normal 24 core machine: 2024-08-31 14:53:45.801 INFO EDCORE (Main): system affinity mask: 111111111111111111111111 2024-08-31 14:53:45.801 INFO EDCORE (Main): process affinity mask: 111111111111111111111111 2024-08-31 14:53:45.802 INFO EDCORE (Main): common cores: {2, 3, 6, 7} 2024-08-31 14:53:45.802 INFO EDCORE (Main): render cores: {4, 5, 0, 1} 2024-08-31 14:53:45.802 INFO EDCORE (Main): IO cores: {8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23} --- In your last line it actually says that the game only runs on 3 cores only (6 virtual threads). I guess that's simply not enough. It may need at least 4 cores or more.

For production quality, another topic is audio: Echo 19 just announced they started working on a real Bell 407 for audio recordings. Where i get question marks floating over my head is how this will end up. Do we need to install a mod to get those (obviously) better sounds? Or will they be integrated in the module? For DCS modules, developers usually already provide the whole finished audio production on release. The effort for sound production was made during production phase, not after release. And it's logically included in the price i've paid.

And now playing the drama card, sheesh... What @dresoccer4 meant is to step away to get some distance to the point you are circling around here. The thread is about technical issues on the whole bandwidth of a product and you are trying to tell us that same price range but much lower quality doesn't matter for a customer. There is nothing else you did contribute, but blowing up the thread with the same personal stuff all over again and again.

Craft is not a matter of opinion. It's a matter of attitude. And PC's attitude makes me upset since 2016. From all 43 modules i own, why does PC always need to stand out with such avoidable issues?

Oh, i have no trouble understanding what you are trying. Only the info that you are in lawyer mode makes a bit more sense now. Looks like you are often in a situation where you have to create justifications out of alternate realities to try to defend a guilty defendant. Desperate measures as a last try to convince some simpler minds in the jury when the evidence is already telling the truth? But your two "precise" points show that you actually don't understand the core of the problem. It's not about eye candy. It's how 3D graphics are made the right way from start to finish. The way how the Kiowa is made and sold - IS NOT HOW WE WORK. Let me try to find another analogy which describes the situation better: Let's say you want to give your car a new paint job. In your town you have two options, both offer the same price for the job. Shop A simply takes your car, a couple of spray cans and let it dry in the backyard. Shop B goes through all the needed surface preparation, sealing parts that don't have to get paint, grind off the old paint, deep cleaning each surface, prepare the right amount of color and give a good amount of stirring to make sure that the end result has a consistent color tone, use a sealed cabin for the actual process and drying, do polishing at the end to finish the job. Well, you chose Shop A, your neighbors try to tell you that something went pretty wrong there, but you try to tell everyone that you like the "spray can" look. I think the majority of people looking at this thread do have a sense for quality and know what state of product they want. It's common sense. And it's no coincidence that there are certain aspects wrong again with a module from a 3rd party dev that sold a helicopter module that had no flight model for 7 years. PC needed a long time to learn one important lesson, unfortunately we need to get to the next lessons (graphics, sound ...).

Actually no. I can't follow you since a couple of posts. It's getting really weird. You seem to get a bit entangled in strange thoughts.

That "logic" doesn't work well for DCS. We won't get any other 3rd party developer doing another Kiowa, this slot is taken. And for me the OH-58D is the right fit. That's why quality standards needs to be kept (and controlled beforehand).