All Activity

I haven't had chance to do the testing I wanted to. The main reason to use XRFrameTools was to measure game performance. I miss-typed in my previous message. I meant frametimes. I played with the two headsets comparing them at the same resolution and same settings in QVFR. As like-for-like as possible. PSVR2: Steam resolution set to 160% for about 3200x3200 pixels. Refresh rate 90Hz. QP: Virtual Desktop set to Godlike (3027x3216) pixels. Refresh rate 90Hz. I tried to use Steam link for this but had issues running QVFR. QVFR for both PSVR2 and QP: foveated region 0.25x0.25 at x1.5, periphery at x0.5. DCS settings were the same for both. I can post them but they don't really matter as I am not including any performance numbers. The PSVR2, even in the sweet spot, is not as sharp as the QP. Not by a long way. Cockpit resolution with the QP is near perfect. With the PSVR2 it always looks slightly blurred. I can read most things in the cockpit without leaning in too much but it never gets as sharp as the QP. Landscapes and distant objects look soft, even mushy in some cases. I have tried AA-off, MSAA, DLAA and DLSS (quality and performance; latest version; preset J and K) and varying degrees of sharpening but it just makes the landscape look very artificial. I just cannot get an image that compares with the QP. The colours on the PSVR2 are very oversaturated. To the extent that there is some colour bleed between objects. There is also a lot of chromatic aberration which can make some objects in the peripheral vision look quite garish. I know I could use Open XR toolkit or Reshade to reduce the saturation but this would not help with the fringing. It is also another XR layer and I prefer to keep these to a minimum. There are other more minor issues that I am not keen on such as the overall build quality, the face gasket (a magnetic one would have been much better), the lack of integrated lens protectors for glasses, the design of the controllers and the Steam VR interface. I realise that the display port connection should give a better experience but for me the Quest Pro has much better image quality. I wish they had released the QP with a Display Port. I think I will send it back and save for a Pimax Dream Air SE.

Very interesting thread because I have the very same problem since a few DCS updates!

Republic of korea army (JGSDF) remove (JGSDF)

Wait!? ALREADY? How is that possible? Not even TWO WEEKS? Congratulation! I'll test it Today.

Unfortunately, I have no idea. But I’m envious. I measure DCS download times in days, not minutes.

We could do with some Turbulents, water balloons, flour bombs and gates to fly/limbo under too . eta: The smell of fried onions. Mustn’t forget that.

In the last picture overlooking the Merlin we see someone has his head in the cockpit, eyes down. I’m taking that to be Sq Ldr Scoobiedoobs, BriantheBrain, Loki or someone on the team and that they’re busy tinkering and humming happily away to themselves while they work. Holding on to ‘no news is good news’ is sketchy but it’s what I’m going with for now. Trust everyone and everything’s all good. Best regards .

Just installed this app. Aircraft are showing, but not seeing any ground units ?

Anyone can confirm whether it still works in the current version?

Hi all, to my knowledge the only airshow objects mod for DCS was the GrinnelliDesigns Air Show Scenery ( https://www.digitalcombatsimulator.com/en/files/3302379/ ) It appears this mod no longer works in DCS. Is there any talented mod makers out there that would be keen on creating something similar? Or perhaps there's an alternative mod I hadn't heard of before? Certainly can't find anything on the DCS user files

Понятно спасибо!

Thanks, this is fantastic!!!

When there are multiple carriers, they all have the same name (Essex class carrier) on the comms menu, ordered by distance to the player. So, contacting the intended carrier in the group for reporting inbound is a bit problematic. This may be relevant to the problem you're describing.

Yeah, it looks like that's a (weird) error code inside of DCS. Was misleading, that's why I looked at Onedrive first.

В этом на 1:50 показывают.

hello. post your latest dcs.log. also, check windows event logs. make sure all you OC is off for testing.

DCS isn't even remotely a good software for handling complex graphics. In fact, even if you have the best graphics card and the best processor, it will always present these kinds of problems because, I suspect, everything hasn't been synchronized properly in its programming. Furthermore, when you connect to multiplayer, all the frame rates are thrown off. This last point shouldn't be the case. DCS shouldn't influence a user, no matter how bad their connection is, and slow down my FPS. Having said all that, your problem could come from where your data disk is located; Windows access, other interfering programs, or external software accessing the same disk could be the cause. Here's what I can think of offhand based on what you're saying. Best regards.

Probably none of them, but engine management wise it's obviously something relatively close to P-47 and F4U. I don't think any of the others would be anything even vaguely similar to compare to.

ED post a teaser on your discord some weeks ago:

Is there any way to stop the constant spinning view in encyclopedia? I know it stops when you click on the view but it starts again when you view the next model. I would like to stop it by default.

the upcoming version 1.2 has a proper radio and so can communicate with the carrier in the same way as the f-18. Here is a recording I did while testing v1.2:

No. If you've read the thread title, it should be obvious that the thread is about the issue of taxiing with diff breaking. Relevance of wind to taxiing and how it inaccurately aggravates the issue, as discussed at length above, is clear. Feel free to disagree, but unauthorized thread policing is not appreciated. Edit: For further clarity, crosswind is raised as a contributing factor to the problem, not as the sole cause of the issue. Just in case it is not crystal clear.

Actually just checked the mission and in AG2 the laser code is set to 1686 on the APKWS 151's so they wont hit the targets as well. Change it to 1688.