RafaPolit

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.

Thanks @NineLine. In my case, they were not shooting at all. Nor respecting any of the the Reaction to Threat settings. I could fly in formation with them, no attack. I shot them, they just kept on going until the plane could no longer fly. I was spawning almost 80 miles away from the planes and "reaching out" to them. My comment you quote was due to someone else's comment that tracers could be getting fired, but maybe not seen. So I mentioned that if they were fired and not seen, then "they must have worst aim than me", because I didn't feel a single hit on me. It was kind of an "ironic" comment to mention that no, I wasn't shot at all. Sorry if this caused confusion. I could test again with the newer versions, haven't returned to that mission as it proved really frustrating to just arrive to the bombers and be able to dance around them without them posing any threat. Thanks for looking into this.

Yeah, I am always eyeing the M2000 for purchase, but haven't yet gotten to it. I either fly the Warbirds or the newer Jets (up to F-14 included, which, also, does not have the "full" advantage of link16). Yeah, maybe I'll grab it during this sale? Who knows. Thanks

Yeah, it's the same servers we are talking about. Less than 200nm, but still, some 15 minutes to cold start, align, input coordinates, etc. Then the flight itself. With other airframes perhaps even an in-between A2A refuel (luckily the F-15E bypasses that on most cases), so yeah... 30 to 45 minutes of sortie. Yeah, we are talking about the same servers I guess. I try to avoid F-10 as it feels like cheating, but yeah, may be that, in this case, it's required. I try to communicate as much as possible, but I have found out that there's less than 50% of pilots that use SRS, and from that 50%, about half are on the wrong channel or talking by themselves on their group. Human GCIs has been very rare in my experience, but when it happens, yeah, the experience is completely different! Exploiting bogey-dope, as you put it, could be a good middle ground approach. I need to get re-used to those flows, as having the F-16 SA page has been my bread and butter reference to avoid unwanted missiles in the but!

Yeah, this more or less summarizes a reasonable approach, except for the bugging out part . I'd prefer not to lose my last 45 minutes of flying just to start over again. But yeah, I guess it makes sense. So, taking DCS out of the equation, do you think that is how it goes IRL? A flight of F-15 invest millions of dollars and human hours to go into a remote location to strike a strategic target, and at the smallest blip on the TEWS they are instructed to just turn around and run back to SAM coverage and throw the mission off the board?

Are you serious? That could be more than a hundred miles. I hope you are joking.

So, just to understand the process, if you have "ping" on TEWS from behind, you would turn around, try to find it on the radar and do an IFF interrogation? I'm talking about practical scenarios in our MP environment. I understand that, in real life, you would have notions like: "we have guys behind you" and you could probably coordinate and talk through radio. In our MP environment this is not always the case, and I am wondering how to move around without having to react to every warning ping. Also, in real life, the type of aircraft would give you a huge amount of info. Again, not so much in our MP environment. I'm not complaining, I'm not asking Razban "why didn't you give me a fully fledged product", I'm genuinely asking what are people doing to be "effective" as you so aptly put it. Thanks for any feedback.

This is kind of important. How do you get threat awareness? Only with the TEWS? And do you react scared to every blip not knowing if it is friend of foe? What are people doing on MP servers to know what to be aware of and what to shoot? Thanks, Rafa.

Thanks for the replies. Much appreciated.

Yes, but in the loadout configuration in the PACS menu, you have two options, maybe I didn't make myself clear, I'm sorry. I have edited the original post, maybe now it's a bit clearer. Thanks. This is a good hint! I have not done a hot start yet, but it's a good hint. Thanks a lot!

I'm trying to find when should I select the B or C variants of the GBU-12 A/G Loadout configuration on the PACS menu in the F-15E? The rearm screen can only select GBU-12, it does not distinguish between A or B (like is correctly distinguished in the AIM-120s or AIM-9s, for example). Which should be used for what? I don't seem to find anything relevant in the manual either. Thanks for any insight, Rafa.

I was coming to request this very same thing. For those that have throttles with detents, this is a non-issue. For us, owners of non-detent HOTAS, this is a complete MUST. All aircraft I fly have this: - FA-18 and F-16 use a similar strategy: you push the button and you are "free" to move the throttle forward. You push it again and you are constraint up to mil power - F-14 uses the "while depressed" strategy, which also works depending on your setups The lack of these options is critical as this, in combination with little feedback as to when you are in AF, leaves us almost always depleting your gas reserves. I believe this is one of those places where making a sacrifice of "fidelity" or "realism" in favor of playability is very much appreciated. Since it could always be disabled, I don't see the harm in implementing this. Please give us this feature. Thanks, Rafa.

Hello guys! Really enjoying the F-15, thanks! I have encounter an issue that is half reported elsewhere, but not the exact same issue. My main issue is with the different key binding options for the Weapons/Mode Switch option and the fact that, with the CYCLE option, the Throttle (at least visually) and the Mission "triggers" are not being triggered when using the CYCLE bindings. My problem is somewhat related to the following thread, but not entirely. My main bug report here is about the Mode state with the different binding options. - If you bind the AFT, CNT and FWD switches, the value is actually "set" and you can see the switch move in the throttle. Most critically, the training missions also ONLY recognize this situation as valid to move forward (hence the essence of my report). As noted on the link above, this allows you to move from GUN to MRM without going through SRM, which is not correct (but, again, that is not my bug report) - If you bind the CYCLE AFT and CYCLE FWD, the HUD more or less responds as expected, but the switch on the Throttle is not cycling through its states, and more importantly, the detection mechanisms used in training exercises DO NOT recognize the mode as being set. Therefore, you just "correctly" entered MRM with your bindings via CYCLE, yet the training mission is STUCK because it's expecting you to activate the mod which is already on. - The las mode is for always-on switches which my HOTAS has none with two positions, so it's useless for my setup Hope this is clear, I'd be happy to provide more feedback if needed. Thanks. Best regards, Rafa.

Oh, I missed that on the patch notes. Thanks for pointing it out.