RafaPolit

For what is worth, following this post: I now have done two attempts, in MT, but with Auto Start once and then with Stored Heading INS alignment, and, it works! Smoke stays at angels 17, goes 55NM East and calls Tape's On as expected. The full INS alignment always ends up with smoke just going to Angels 1 and heading south. Maybe this should be included in the designer's notes in the briefing and / or PDF? Thanks to the community for this inputs.

Thanks Thanks so much for this! I have flown this mission now about 20 times (not exaggeration) Indeed, I tried two times now with Auto Start (not my cup of tea!), and Storage Heading on start instead of the full INS align, and lo and behold, Smoke stays at Angels 17 and calls Tape's On, perfectly when he is 55NM from WP4. Thanks again for this input, maybe this should be included in the designer's note on the Briefing and PDF?

I tried today with ST version as that is the recommended version by the author. No joy: “cut away” and Smoke just dives to Angels 1 and start slowly going south and then just lingers there.

Just to expand, I did a fairly fast refueling this time, one minor disconnect and back on the basket. Still, same problem: - Reach WP4, call on mother - We call the "split" call (sorry, don't remember the exact term) - Smoke breaks formation, dives steeply south and settles at about Angels 1!!! (that's right, one!) flying really slow... never gets more than 15nm of separation and never the tape's on call Could this be also part of the MT vs ST problems? Really seems crazy to have to play in ST, maybe I'll give it a go. On a completely unrelated issue (and probably not mission related either) I then do the Case III recovery (even if the mission is a bust, just to practice an get into the habit of good practices in the F/A-18) and everything goes perfectly smooth in CPL P/R mode right up to the deck, I touch down perfectly, and then it's always "bolter, bolter, bolter", as if I'm not garbing the cable with the hook. I do a fly around, no fly manually (as CPL is no longer an option) and I "manually land" perfectly grabbing the cable on my "manual" pass. Weird. Obviously this is 99% sure NOT mission related, but ED's issues with the carrier, but just wanted to mention as this entire mission (with the wrong radio calls I mentioned in another bug report) is really a test of one's patience and nerves! Thanks again for looking into this! Best regards, Rafa.

Thanks for your fantastic campaigns! I whish I could move forward on this one. This should be really simple: - Jump into the plane, start the engines - Press space bar to check with Two: - first call is made ON COMMS 2 CHANNEL! (not on one) to which there is a reply, - second call is actually made on COMMS 1 (saying Comm 2 check, of course) and there is no reply back - During flight, some calls get my COMMS 2 changed to M As for the last part, Comms 2 changing to M may be the Easy Comms settings (which was on at first!), but the other two problems are true, even if Easy Comms is turned off. This may also be problems to more bugs like the "Tape's On" never getting called (as I may be on the wrong channel, inadvertently). So, basically, the automatic communications are trying to use comm 2 when comm 1 is expected. And then, if Easy Comms are on, it's actually not finding the right channel and changing it manually on Comm 2 and not using Comm 1. The triggers are checking on Comms 1, so things seem to keep on moving along, and I am missing important radio communications. I do have SRS installed and a single push-to-talk button, but I think that we all have that. Any suggestions? I really would want to NOT have to uninstall SRS for the campaigns. Thanks, Rafa.

I have just flown this mission a couple of times, and have this same problem: Smoke splits at WP4 as expected and dives to about 2000 feet and just lingers there, never the tape's on call. I do have SRS (don't we all? :P) which "may" be doing something, but I doubt it. The other "potential difference" is that I took me quite a bit to refuel... maybe time constraints may present issues (Smoke did refuel perfectly fine and rejoined with me, no issues there). I'm also creating a separate bug report about radio channels and comms, it may or may not be at all related. I'm using VR and I'm using the MT version. Thanks for any insight. Rafa.

Good evening friends! Thanks for this thread. I was wondering, if the SuperCarrier can modify the hangar... can we actually have a way to specify the Hangar per-module background? If I select the F-16 as background have one for that, if I select the P-51 have one for that one? I'm sure this is possible since it's happening with the SuperCarrier. Before I go on reverse-engineering the luas, I was wondering if this has already been achieved and I am missing the resource? Thanks.

I have been running DCS in VR for a month now and Virtual Desktop without any issue. Today, I experienced this EXACT behavior described here: the Quest 3 stream, after a few seconds of working correctly, freezes in the current frame+space. I can turn my head and see black areas beyond the rendered and frozen area, but the PC seems to still be tracking the headset and rendering correctly the view. If I close VD on the Headset and open it back, I sometimes get a few more seconds of good tracking and then the freeze again. Sometimes it just gets back to the stuck section. This would indicate that this is a VD issue, but I tried SteamLink with SteamVR and, instead of the video freeze, it just crashes to desktop, more or at the same time it would freeze on VD (and it does work for a few seconds). The one "constant" between the two are: DCS and OpenXR. Has anyone found a solution? What could be causing this? This was working perfect until last Friday. The only different thing in my PC is that I installed WSL service for windows 11, but it's a really long shot that that is what is causing the issue. What other variables can we look into?

Since everyone is getting the South area in high detail, and there are no high details in other areas at this point, this simply is not possible at this point. Common guys, it's a new system, there are questions, let's try to give SOME benefit of doubt to ED that they have spent, at least, more amount of time thinking on this than the two seconds we have had to complain about it!

Actually, this is what I fly 95% of the time. The difference is that a WWII plane needs to be 300 feet away from you to shoot you, and you from them. Using your mk1 eyeballs is perfectly fine. On modern MP servers, the “others” know you are there 80 miles away. Also, I honestly think that reading comprehension should be a crash course before allowing posting in these forums: I clearly wrote that I am not complaining, that I am ASKING how do you guys do it and how do you compensate for the lack of datalink. Obviously you and others read: “please mock me as much as you can with your pedantic attitudes and your incorrect assumptions”. Thats nice.

Well, what do you know. One day after all these discussions, the people from VD have fixed the SSW "wobbliness" in today's release. All things mostly working as expected now, within VD and with SSW enabled to give some legroom to the GPU. Let's see. Thanks again, Rafa.

Just wanted to drop here to give a note of thanks! Refelcted, your campaigns are masterpieces with the perfect balance of action, skill, leisure time just flying and "preparing" for what's ahead. Of course, if the pilot spends 15 minutes crossing the Channel, and, when faced with the enemy, dives from 18.000 feet to 2.000 feet expecting compression not to kick in and die a miserable death, it's not the designers fault! Honestly, I have flown a lot of your missions, but today I tried mission 7 or 8 from BNBOF for the first time in VR! It was a blast. I enjoyed it immensely, and I scored 120 points of enemy planes downed, which is a first for me, so I'm extra happy. Not so much with my subpar landing, but a 100 score to finish it is a true gift to inaugurate the new VR headset. Again, just wanted to drop a line of thanks! Looking forward to the new campaigns in the upcoming map. Best regards, Rafa.

Yeap! This did the trick. SSW was actually the setting that was screwing the "temporal" wobbly behaviors. I appreciate the feedback. Now I need to know why I am having black flashes (more on one eye than the other) on certain meshes / textures, this didn't happen before. But it looks like I am getting more consistent results. Indeed, VD is the better tool with the better results, no matter the environment: productivity, games, maybe media watching is better achieved via other platforms. Thanks again.

Ok, thanks, then I have seen those. I thought it was in a different place.

Thanks! Those look reasonable, depending on the actual settings in DCS. But: maybe I'm missing a config screen: I know how to access the SteamVR settings, where do I configure the Steam Link settings? Within the Quest? Where? I don't think I have access to those. Thanks.

Thanks, I have been trying to toy with different settings, from godlike to even low settings and nothing helped... I thought that SSW was kind of a "must" to get good performance in DCS. Obvioulsy SteamLink (or SteamVR, not sure who's responsible) is not doing that, and FPSs are not capped at 45fps. So, yeah, this is a good thing to try and see if that "frees up" this behavior, as I agree with you that, for everything else, VD has just been the superior tool: much better text, much better desktop rendition (albeit only one monitor), passthrough of remote keyboard AND mouse (which no other platform does), so yeah... if I can get VD to work as I would like, that would me my preference as well! The other only *very minor* grip is that, being an amateur 3D artist, I wanted to create my own environment, to which the VD guys have replied "can't do it on the native app", and I have already made my "home" in SteamVR, so yeah... I like "visiting" my own creation to launch games, but I could do it the "other way around" and launch SteamVR from VD and not SteamLink and have the games run from VD as well. Yeah, thanks, I'll give it a try and report back. Again, I appreciate the help and the "patience", I know that guiding newbies can get frustrating, so I really appreciate this. Bets regards, Rafa.

This is going to be a "weird" thank you, but it is a thank you nonetheless! This, indeed, worked. I selected SteamVR as the default XR runtime, it opened... worked really weirdly with a black box around the area (like if I had less FOV) which was "stuck" in space (if I panned with my head the box will stay in space and only the middle would get rendered), then I reopened VD, it apparently reassigned the VD XR Bundled runtime, and then everything just worked within SteamVR and SteamLink. No "ghosting", a little higher FPS, I like it better than what I had with VD, but the fixed foveated rendering is a bit much and some screens are hard to see, specially on the F-15E. The warbirds are a dream! So, thanks a lot, not sure what process was different, it's working (mostly) as I would have liked it to work. I really appreciate your "into the dark" guess, it worked, even if returning to the previous state works as well now. No idea what's going on... but if not's broke...? Thanks again. Rafa.

Good afternoon friends! I have been a DCS player for a couple of years, just bought the Quest 3 recently. i have been able to play with Cable Link without an issue, but I think that wireless *may* be enough for me. I have used Virtual Desktop with almost complete success, but there are some “ghosting” or wobbly artifacts on planes flying at certain distances. I see this same “wobbly” effect on videos played in Steam Home screens, so I’m inclined to think there is something with Virtual Desktop that is sharpening or affecting this. I’ll look into that on my own. To discard Virtual Desktop, I’m trying to run DCS VR through Quest Steam Link. It launches as a 2D app. I have tried: - launching DCS through a desktop link with the VR flags added - adding DCS MT as an external program to Steam and launching through that (that worked for Arcade Time Capsule, for example) without any flags - adding the flags to the Steam “game” in library All these efforts launch the game in 2D from Steam, never go inside VR this way. What could be happening? How do you launch DCS standalone in VR through SteamLink in Quest? Thanks. Best regards, Rafa.

I have the same ghosting, I’ll be following this thread.

I was looking into that path, have conducted some, but those were my next tests: I don't see that on passthrough, not on video playback, have not tired other games either local or on PC. Still, the fact that this captures in the screen capture points towards a local Software related issue rather than a more global hardware related problem or general software corruption. As a matter of fact, the fact that it captured on the screen capture means it resides within the computer realm. Not on the Quest realm. But I will try with other games, it's just that I don't have many. Mostly only play DCS and every now and then MSFS.

I reverted to the original settings and the patterns remain. I'm connected via Oculus App, with original Meta Link Cable. Hope this helps with some level of troubleshooting so I can find a fix for this. Thanks for the input.

Good evening frieds! First day with the Quest 3 and trying flying in VR. The experience is AMAZING! After a few flights and trying to make some changes to test different refresh rates and resolutions, etc. at one point DCS started presenting some strange patterns on both eyes and I cannot seem to get rid of them. I deleted the xfo and Meta(? I did delete the right one, cant remember the name of the other folder now), same results. What else could be the problem / culprit? Here's what I'm seeing: null Ps. It happens on different planes as well

Not anymore, and I have not had this ever... this just begun happening with the new 2.9 open beta. I just tried another server and a different "weapon.shells" error appeared, now with 20x138B_HE . I have done a quick and then a long repair. I'm attaching the new logs and dxdiag. I do have mods, they have never presented an issue, that's why I was asking for help in possibly narrowing down where this error could start. I could remove all mods, but I'd prefer if an educated guess can point me into a more "laser focused" solution, rather than just uninstalling everything. dcs.log-20231103-043038.zip dcs.log dxdiag.txt

Good afternoon. So, every MP server I go into, the game crashes. Maybe they are all using the same "script" or something that is triggering the crash, maybe it's on my end. I'm attaching the crash reports. My half-educated research looks like there is a problem with "Descriptor not found weapons.shells.AK630_30_AP", but I can't find which lua file, script or whatever process is referencing that descriptor. Online search shows https://github.com/mrSkortch/DCS-miscScripts/blob/master/ObjectDB/Ships/MOLNIYA.lua uses that EXACT line, but I don't think I have that file in either the core installation nor my saved games folder. I'd appreciate any insight into where to begin looking? Thanks. Best regards, Rafa. dcs.log dcs.log-20231103-032230.zip

Yes `saved games` -> DCS[.openbeta] -> Config -> MonitorSetup It can go in the main folder, but it's cleaner on the Saved Games.