Silver_

When I'm loading a mission or an instant action, it doesn't matter, when I get to "spawn objects" the loading freezes, it only works again when I open the task manager window with CRT+ALT+DEL, at this point I don't do anything , I don't stop any process, I simply leave the administrator window open and DCS magically continues loading until the end without problems, I have no idea what could be causing it. It only happens to me in VR with meta Quest 3. Some help would be appreciated. Thanks autoupdate_log.txt dcs.log

Thank you for your response, it has been useful to me, but the representation on a radar of an object with a lot of screen persistence is not well programmed, that is not how it can be seen, I assure you. In fact, if that were the case, when you put the cursor on a phantom contact, I doubt that the system will select it as happens in my video. In any case, it could be useful to get by until they program it better.

I was flying a mission and I observed that in RWS mode multiple echoes were caused on my radar like a string of echoes from the same plane and nothing except the tanker was there. When you select the target anywhere in the string it becomes to a single contact. https://1drv.ms/v/c/d748c16240d10095/EWqR6yHoyztEisKMIpwKla8Bf8htmUYZDhh-fbz2wxVkfA Edited: Updated video for clarity.

Same here. To this day there is no mod that convinces me for NVG.

I have stuttering even with a stopped image , I press ESC and with the menu view the graph appears with lots of peaks. The only thing that saves me is ASW on my Quest 3. I don't understand why this happens with these latest versions. The FPS are crazy going up and down.

In a previous post I also complained about the points but to be honest, now I no longer have them. It looks more natural and not exaggerated as I saw them. Before I was moving away from a plane and there would come a moment when the texture and the plane would disappear and suddenly a huge black dot would appear; now, after the modifications I made, I don't have that problem, now I move away from a plane and it gets smaller until a small point is made that if I continue moving away it fades with the background. For my part everything is perfect. At least on my system and with my VR glasses. What I did, strangely enough, was to completely uninstall OpenXR Toolkit, it had two layers, the first Quadview and the second OpenXR toolkit (which is no longer there). I have applied DLSS and I have added supersampling (so as not to see it too blurry) through the Quadview config (focus_multiplier) in my Oculus Tray tool config (I go with cable link) I have applied the unit (1) in both eyes and supersampling in 1 (I already applied with Quad) Now it's perfect, my RTX 3090 and Quest 3 system, 5800X Ryzen processor. I hope it helps you, it has worked for me.

But that is corrected with prescription glasses, not software.

Please, DCS team, I won't be the one to tell you how to do things, but when a plane moves away it gets smaller and smaller and there comes a time when it fades into the background. In your programming logic it would be, as I can see, "it gets smaller and smaller and when it is about to fade into the background, suddenly, it grows like a magnificent black square." If you see logic in this, let God come and see it because, no matter how hard I try, I cannot see your logic. I would have allowed you a black dot that degrades in color tending, finally, to resemble the background but a SOLID BLACK POINT!!! is inadmissible. In my programming days I have not seen anything like it. Excuse me for the criticism but you have more than enough financial means to at least try to do things well and have a good team. PS: By the way, this option is not useful for much, it stopped working. Thanks for reading me.

This is basically what I want to say. .

This is not my personal preference, it is perfectly explained in the USAF HANDBOOK regarding the F16, you can consult it. Anyway, I think they have a hard time understanding me. I know the current logic is a bit silly and passes the SOI to the second MFD (with WPN selected) as soon as you first press TMS UP on the radar screen. What you would do is enable cursor mobility, then we would search for the target (now that the cursors are moving) and a second press of TMS UP (once the target is located/selected) would do what you say, pass the SOI to the second MFD (with WPN). Not exactly because you, on the second MFD, do not have the WPN screen on it (you have the HSD). (the SOI must be on the first MFD, the radar, with SP activated)

I don't want to leave SP mode, I think you haven't understood it, what I want is to enable the cursors in SP mode within GM. If you do TMS DOWN you exit SP mode and go to WP (waypoint) tracking mode. I already knew this, but let me tell you that with the first press of TMS UP the cursor is enabled to slide and with the second press of TMS UP what you say here happens (obviously the second press, once the cursor is enabled, is to select the target and the SOI changes to WPN as normal). This is what should not happen, LET THE SOI CHANGE!, it should only ENABLE THE CURSOR and nothing else.

When I am using the radar with targets of opportunity in SP (snowplow mode), when I enable the radar cursor with TMS UP, so that it begins to slide, the SOI jumps to the right MFD where I have the Maverick's WPN screen and I have not yet selected no objective so I have to change the SOI again manually and thus be able to select it. This should be corrected. The SOI should only change if I make the target selection, or at least that's how I understand it. I send you a Track as an example. SOI_problem.trk

Yes it is true but it does not allow you to regulate the amount you see below or the size of the binocular, this is always the same. Anyway, don't worry, I'm fine the way I am.

Before there was the option of being able to move the NVG image up and see the cabin below, I don't know if there is any option of this type now.

It would be good if it incorporated, like 3DMigoto, the possibility of activating and modifying NVGs. It worked very well in VR.

DLSS gives better performance because in the end it is at the cost of losing definition and everything is blurry (small letters or distant or somewhat camouflaged planes are difficult to see). There is a technique that consists of increasing the pixel density in DCS and using DLSS, in the end you can see better but at the cost of performance, which results in a performance similar to or less than MSAA x2 as @speed-of-heat suggested. In the end I prefer to stay with MSAA and not waste any more time, everything looks clear and how I like it, and the performance is not that bad either.

In real life you can ask the tanker why you want to enter to refuel regardless of what may be more orthodox, which is to enter from the port side.

I would like exactly that, to be able to refuel any Refueller probe by requesting it from the AI operator (similar to real life) and for the basket to move according to the relative wind just as it happens in reality. I hope DCS takes note of my wishes. Thank you.

I would like if it will be possible to copy the fuze configuration to another bay of the aircraft as is currently the case with the laser code. The interface would be much more comfortable. I have also observed that on the F18, when mounting the FMU-152 fuze, it does not allow me to configure the parameters of this fuze from the cockpit as this type of fuze supposedly allows. It's not the case of F16. Thanks.

Interesting, but is it on github?

The problem is that I don't even know how to follow the code on Github, this is more advanced than what was available in my time. Let's see if one day I read an adaptation tutorial.

I got it to work by editing the text as you told me. It finally reads me correctly the call to the ATC from P.e. Gecitkale in Syria (verified). Back in the day I programmed the C++ language and the Assembler at a fairly high level and I suspect that for some reason pressing "Fininsh" does not update the database indexes and simply sends the original copy of the database without additions. I've gotten older and it would be very difficult for me to return to the topic considering what's new.

Good idea !!! THANKS

Thank you very much my friend for your response. I was about to send you a PM because I saw several of his posts and noticed that you had the same problem as me, but in the end, you contacted with me. I don't quite understand what you mean, but I imagine what you will do is use a text editor and add the missing aliases, checking the new ones that are generated with VSPX on off. I did the following: I tried adding new aliases with VSPX disabled and this works perfectly, they are also added to the list for voiceattack, I applied changes and closed. I opened voiceattack again, pressed CTR+ALT+C, opened vaicom and changed VSPX to on; After this, the list that it generates no longer has any of the changes (even though I have given it a list with changes) so the only method I see is by manually editing the list (as I think you refer to in your post). Although in my humble opinion I find it somewhat tedious. I think that this is the methode that you apply. Or maybe not?