warmachine79

What will I have to do, as soon as I have the files from the official source ? Yeah, although I do not associate that "blast" with gaming.

Hey guys, under this link the DLSS 4 DLL are uploaded. How do I get them to be used in DCS? removed link

Thnak you Rudel, that worked.

I have the same problem (Steam Version). I cannot find any references to the .dll file mentioned above in the Defender history. I added an exclusion for the whole DCS-Folder, but to no avail: null

Thanks, worked like a charm.

Hey guys, when I am in VR, is there a way do get fullscreen on my main monitor? I have a Pimax Crystal Light and I only get a window on the main screen when in VR and it is cut off to the left and to the right. Which settings do I need to get fullscreen on main monitor in Full HD, so "spectators" can watch?

Hey guys, is there is a sticky or something that just sums up what to do to get the best DLSS quality and how to potentially decrease the amount of upscale? There are multiple threads on exchanging .dll files, what version of DLSS to use on what version of DCS and on using tools like DLSStweaks. DLAA is too slow for me, DLSS Quality is fine FPS wise but could look better, so I am looking for something in-between.

What is a "civil operation"?

@SharpeXB: maybe I have been spoiled by the 3090 over 2080TI and 4090 over 3090TI releases. Plus, 30-40% is optimistic. It has 33% more CUDA cores, but at a lower clock. As that is unlikely to scale in rasterizer performance 1:1, the "IPC" (do not know if that term is appropriate with regard to CUDA cores) has to increase about which there is no information. Sure, the bandwidth massively increased (memory interface increased and GDDR7 presumably at higher clocks used), but I do not think that the bandwidth was a bottleneck before for rasterizing power.

Frame Generation not working is a major problem with VR. Rasterizer power is the thing you need to create "native" frames which apparently are the only option for VR. But rasterizer power will not increase in the future as it did in the past which is indicated by NVidia marketing AI heavily and is also indicated by the 5090 only (likely) providing a slight increase in rasterizing power (maybe 30-40%). So that is a bottleneck for further increasing headset resolution. A 4090 can be brought to its limit with a Crystal Light, a Crystal Super thus will totally abuse a 5090. Headset manufacturers will have to get their head around that and ditch their proprietary space-warp-and-whatsoever technologies and instead implement DLSS frame generation properly.

TMS-Fwd is a real smart circumvention of the problem.

I have a question regarding the TGP. They are extremely annoying in the F16, in the F15, I am fine with it. The thing is: it is either in Snow Plow Mode where I cannot control it. Or if I disable the Snowplow mode, it immediately slews to the active steerpoint which is somewhere offscreen. I want to slew that thing manually when it is boresighted and be able to reboresight it, when I lost it. This is what I do in the F15. The only way how I get it semi-comfortable is selecting a VIS mode weapon, slew the HUD TDC somewhere I can see it, designate and then make the TGP SOI. And how do I autolase once I released a laserguided weapon? In the F15, ALAS is on by default. The other question relates to steerpoints. Do I have to manually enter them? Or is there a way to make a point I am looking at with TGP/HUD TDC to steerpoint?

Hey guys, I just want to fly missions and a lot of the are cold start. So I use the autostart procedure; however, the alignment step consumes time, is there a way to skip it without ruining the autostart procedure?

I think I solved it, there is some constraint, if I hover and turn a little bit, I get the "Prim Chan Tracking" display and the missile will hit. This is strange, I am facing the target, it is 3000m away and I am at a similar altitude.

I do not even get the big box.

Hey guys, I have a problem with the Laser Hellfire. In the mission mentioned above, a SA-5 radar is to be taken out. In the beginning of the mission, you have to enter some TG coordinates which I do. Then I fly to the Navpoint from which I have sight on the target. So I enable Master Arm, Laser is on (checked), I lase the target (and hold the button pushed), but if I then fire the Hellfire, it just flys straight and does not "lock on" the laser. You also can see that as if I lase, the "Primary Channel Tracking" message does not appear and I do not get the big closed box, but only a distance reading (3000m). I think the laser numbers and channels are set up properly because I hit the "Slave" button on RHD, the TADS goes to the coordinate I enter in the beginning. If I lase the coordinate, "Primary Channel Tracking" and the big closed box appears and I fire a Hellfire there while lasing, it will hit the target. So what is keeping my Hellfire from tracking the laser of the SA-5 site? It is a little below my altitude, 3000m away and straight ahead. There should not be any firing constraint.

Okay, but that is only the case if I use modifiers, correct? I am not aware of any modifiers I use, but if so, does the whole configuration not work or only the respective function that is effected by the modifier combination?

Thanks, the renaming tricked works good. Would this also work when I upgrade my Winwing and Virpils Firmware and they receive some new ID number?

Hey guys, I "move" to another Windows installations, it is quite old now; to transfer smoothly, I will be operating both installations in parallel for some time. So, on my old Windows, my DCS is nicely setup, I have my Virpil, my Winwing etc configured for some planes and I do not want to do that all over again. So: how do I transfer my settings?

Now I am confused. Which suggestion in the thread leads to DLSS taking Preset F instead of E? And does the Preset already imply the scaling? So Preset F is a scaling of 0.66 and F is 0.9? Whhcih Preset has 0.8? And what do you mean by Scaling? The downscaling factor of the resolution?

What is the advantage over DLSS (Quality)?

Yeah I removed the lenses and cleaned the lenses front and back and also the mirrors behind. Still, there is hardly any improvement.

Hey guys, is there a way to modify the highest possible bitrate for AV1 in Virtual Desktop when using the VDXR runtime on the Quest 3? I have a stable 2.400 mbps connection (ASUS Rapture GT6, PC connected via Etherent, headset in a distance of 1,5m with direct los), latencies are great, but it only gives me have bitrate of 200 Mbit. This seems to be the maximum. I cannot remember where I read it, but I think there was some manual tweaking I can do to get to 500? I want to try to increase it to the point where latencies become impaired.

What do you mean with regard to "spotting"? Spotting planes? Are there specific settings to consider? I would have thought if you just max out, spotting is fine. However, I noticed a bug but not have been able to reproduce it. With DLSS enabled and some settings, planes that have been far away and would have been little, hardly spottable dots became quite greyish chunks. That was not very immersive, but yet somewhat...helpful.

I received my Pimax Crystal Light, too, and honestly, I am very disappointed. Even in terms of clarity, the picture of the Q3 via VXDR and WLAN is better despite the significantly lower resolution. Although I maxed out Gamma and Brightness, the picture of the Pimax Crystal Light is somewhat dark. Also, it is blurry and I only get clear letter readings with one eye at a time. It seems to me that the screen or whatever it is called in a VR headset has great potential but the lenses ruin it all. I can get a sharp picture for one eye if I close the other one and move the headset around. But this sweetspot is immensely small! No matter what IPD settings I tried (I measured my IPD, it is 65.3), the other eye wont get a sharp picture. For the right eye it is almost impossible to get a clear picture, only in a very weird headset position. I also tried "pulling" the headset away from my head as I read reports about the eyes being to close to the lens. The colors are distorted, too. The FPS figure from OpenXR toolkit companion overlay is yellow-ish-green with some colors around it, only if I move the headset so that the FPS figure is in the middle it becomes clear. I also noticed chromatic aberration from hell in Automobilista 2.