peachmonkey

my pet peeve with the current naval assets is: - no damage modeling - extremely difficult/impossible to destroy/inflict any damage whatsoever Because of it I completely ignore them in any mission hosted on any server. There's no gratification whatsoever in fighting them. They are simply static undestructable objects and any mission objectives against them are completely pointless. My simple ask was to introduce a "game" damage model for them at least for now. Add a modifiable "hardness" or "ruggedness" or "strength to them so the mission maker can include them in the achievable objectives, etc. DCS is a sandbox. Give us this sandboxness in the naval warfare as well.

heck, I'm so in love with the Anton that I built this 30 momentaryOn-neutral-MomentaryOn toggle (60 button) deck so I can start the bird up as quickly as possible.. in VR... hah.. Difficult? totally.. Practical? maybe.. Fun? 100% YES

going in to the weeds here... I feel I will lose some of you here.. like any computer game out there it is to stimulate your imagination. The older you get the whole fantasy machine in your head changes the requirements for its operation. Those "requirements" are in this case known to you only and it is you who consciously and subliminally sets them based on your life long experience sprinkled with the expectations of dopamine generation during the whole "fun" portion of the interaction with the game. And on top of it, just like in the real world interactions with objects/light, your brain is really good at filling in the gaps within the presented simulated "reality" in order to deliver the immersion that you desperately seek. During this trade-off/filling the gaps game you can make conscious adjustments, i.e. force yourself to accept the obvious discrepancies within the presented simulation. Sometimes it's very easy, and sometimes it's very hard and/or impossible. But the main key here is that extremely subjective and it is YOU who are fully in charge of it. Hence the questions you raised are addressed to you for the most part. Personally, ever since I got in to computer gaming in the late 80's and with the advent of the cockpit based flight simulators I longed for the full scope interactivity with the buttons presented on the screen as it was one of the most important immersion factors necessary for me to experience the elusive immersion of the powered unadulterated hard-core flight (I'm in to WWII stuff up to my eyeballs). IL2 offered enough for it to be my focus for 5 years, but not anymore. Now it's either DCS warbirds or go home.

hheh.. obviously a royal capital VR is much better than just a mere peasant vr .. noted! glad you got it working, @Darpa!

this was the topic I was referring:

there was a topic where Bignewy was commenting, it was about the very issue Darpa is experiencing.. looking, need to find it

short of reinstalling everything, see if you can get DCS running with OpenXR instead of OpenVR. My suggestion here is not fixing your current problem, but rather reconfigure the current corrupted config to try OpenXR. Check this topic out, it's a pretty simple config, however it needs a 3rd party build of the openVR 'interceptor' to funnel it in to OpenXR framework.

you can run the dedicated server on the same machine where you play. In some instances it offers an increased performance since the CPU load is split between 2 or more cores, i.e. core1 for server and core2 for client, vs. a single core processing everything in SP. Give it a try, it's definitely a plus.

I'm not ridiculing anyone specific here, Don. I'm ridiculing the whole topic because all it has is how everybody 'feels'. I feel great today. I'm sure you do too. If this is a technical correction/configuration/modification etc, then there must be a way to show the Before and After state of the matter. Until someone produces the visual evidence this topic will continue be met with some hefty dose of skepticism. Everyone's dying to get to the bottom of this. It's that serious.

and here's the religious talk I've talked about..

this whole topic is getting pretty comical now. without ANY empirical evidence in the form of screenshots showing the introduced delta's it's akin to some nerdy religion at this point. - but how do I know it works?? - Have faith, my brother, as God in his everlasting wisdom and power will bless you with additional stereo vision within an already stereo scene!

I tried it yesterday, modified the global profile, then modified the "Digital Combat Simulator: Black Shark" profile.. (per the youtube video) launched the game couldn't tell a difference at all as far as the "seat of my virtual pants" go, did notice a bit better color contrast on the buttons in the cockpit, but that's about it..

I've never seen A8 this beat up. "We are currently working on visual improvements to the external models and cockpits of the Thunderbolt, Anton and Mosquito. The Mossie is also receiving an updated set of Level of Details (LODs) that will improve performance. " (https://forum.dcs.world/topic/290972-official-news-2022/?do=findComment&comment=4941329 )

currently, the only bomb with an acceptable delayed fusing so you can do a low level bomb run is on the Axis side, specifically a 500kg J bomb, it has either a 5 or 8 second delay and is .. awesome..

unless it's a "spy/diversion" mission done at night.

There you go! I'm glad you're on board. OpenXR indeed brings that much needed smooth VR experience in DCS, there's no other way.

your description is spot on, but that's exactly why I like it. I feel the inertia of this 8 ton monster. Or I think it's inertia.. and it's quite responsive despite having such a serious 'bobbing'.. P47 simply soothes me. Flying it at dusk times calms my nerves...

p47 are very good for taking out large amounts of targets when fully loaded... and on the way back you can CAP in it, but you need to know how and where to fight with it. It's a very versatile fighter bomber, and its outside sound is simply music to my ears.. Had we have a working replay system I'd waste 50% of my time just by looking at its fly-by's..

Good choice. It's my favorite go-to plane. - D9 is great too, but is fragile, i.e. a single hit in the engine jacket and you're losing coolant/pressure. It's a great plane for dog fights and that's pretty much it. - BF109 - i tried to like this plane, but with it's being very tail heavy if you don't have a force feedback joystick (without center) with all other joysticks you'll end up flying with the stick continuously pushed forward and trim on nose-heavy to the max. Per devs its flight model is correct and apparently with Brunner and other ffb joysticks without spring-return-to-center it's fine, but with my VKB it's a <profanity>show. - A8 is awesome: a) it's an excellent ground pounder b) it's the only wwii with a bomb load (500kg J bomb) that has a delayed fusing available, so you can perform very precise bombing strikes without fear of blowing yourself up in the process. All other bombs on other birds are impact-blow. Supposedly the delayed fusing is coming.. coming.. coming.. coming.. and still coming since 2 years ago. c) you can still take on fighters but with this plane being a total underdog you are left with the boom/zoom tactics, which actually kind of make you adhere to the real rules of engagement as it was during the war. I see it only as a plus, it builds discipline. d) it's extremely survivable. Built like a tank. You can take on a flight of B29's and pretty much decimate the whole flight and still come home. Good luck trying it with any other bird. Even P47 is no match for its armor and survivability. e) damage model on it is tits, both visually and systems wise. Coming home with a blown generator and zero instruments is hotness. Coming home on 9 working cylinders out of 14 is that "build like a tank" I was talking about. f) take offs / landings are very demanding. And therefore interesting.

hi, @NineLine, do you know if the non-working instrument lights after the CB breaker reset are part of the reported bug list for p47?

yes, I've seen this post and I know about the pop-out "bug". The issue I'm referring to is that after the breaker is reset (pushed in): 1) the oil gauge starts working again - so this is OK. 2) the INSTRUMENT LIGHTS will never work again, regardless of how much I twist/turn the lights rheostat <---- this is the issue..

hi, all, I'm not sure if I'm doing something wrong or there's a bug. The instrument lights stop working after the a CB breaker "COMPASS LT" is reset (see picture). 1) I turn the #9 instrument light rheostat to the max 2) the COMPASS LT breaker pops. The oil temp gauge goes to 0. 3) I push the breaker back in. The oil temp gauge shows the proper temp reading. 4) instrument lights never illuminate after that... Anyone experiences the same behavior?

@Supmua thank you for doing all the testing! I'm running VB at Medium (33ppd) and my experience is very pleasant on my system. Heck, the DCS VR is so much better that I haven't played IL2 for about a week now, and have no interest in going back to it either... Vsync On = definitely need to maintain 90fps to get rid of the ghosting, but even with it's being Off the smoothness is still very much pleasant compared to openVR. OpenXR with SteamVr = if you figure it out that'd be awesome. In my tests as soon as you disable OpenVR in VarjoBase the SteamVR stops seeing the headset altogether....

1) yup, running it through steamVR framework, however it's using OpenXR renderer instead. For that OpenVR must be disabled in Varjo Base, however the --forceSteamVR makes sure the HMD tracking works through it. It's similar to opencomposite hack that was done for Oculus devices... 2) unfortunately, Reshade 5 won't work with OpenXR. If you want to get that additional color saturation + sharpening you must use the OpenXR Toolkit. Just download the latest v1.0.4 and install it, there's no need to replace DLL's anymore, it's working out of the box. https://mbucchia.github.io/OpenXR-Toolkit/ FFR doesn't really work with DCS in this toolkit version, or if it works it's very wonky, I wouldn't turn it on at all.

the 'mod' portion is replacement of the "openvr_api.dll" that DCS comes with another version (from the opencompositeACC) that performs the intercept of the OpenVR calls and sends it to the openXR framework of Varjo Base. The next DCS update will overwrite the openvr_api.dll so that file needs to be replaced/update after every DCS update. So, technically, you're running DCS using the native's Varjo XR framework, just hacked thru the openvr pipeline. edit: I'll stop replying here as to not highjack the thread.