

warmachine79
Members-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by warmachine79
-
Hey guys, in order to play with my Pimax Crystal Light on 72hz stutter-free, I want to lock/limit the DCS FPS to 72. However, the game menu only allows 5 fps increments. Any ideas?
-
Hey guys, I currently have a single rig for sim racing and I fly on the desk. I want to build/buy a dual rig. Requirement: some solution that allows to have both rudder pedals (Winwing Orion) and racing pedals (Fanatec Clubsport Pedals V3) without having to switch around something. Of course, the wheel will be in the center, thus the Flightstick (Winwing F16EX) will be on the right and the throttle (Virpil CM3) will be on the left. I also want something where I can place mouse and keyboard and both platforms need to be movable. And in case you think I am not complicated enough, the seat should be in a lying position for racing (so Formula seating, not GT3 like a truck driver). I am also fine with the seat being in that position for flying, though. Currently, I have this seat and it would be great if I could use it for the rig or get a comparable one when it comes to the lying position (in particular with regard to the comfortable hip flexion angle): null
-
It is extremely comfortable; I have both for Q3 and PCL third party comfort straps and the PCL is more comfortable; I can wear it for hours. Also with the factory strap - which is a catastrophe on Q3 - the PCL is more comfortable by far. I never tried the OG Crystal, but the PCL is also lighter as far as I know, because it has no battery pack. I do not have any chromatic abberation in DCS, but in AMS2, there are some infoboxes where the edges show slight chromatic abberation. The first pair of lenses I had for the PCL had an unachievable sweetspot, because if I had the sweetspot for left eye, the right eye was distorted and vice versa. I contacted PCL support and recevied a new pair of lenses. The sweetspot now is great on both the horizontal and the vertical plane, whereas you have to move the headset to a certain positiion in order get to the sweetspot on the vertical plane (for me, it is that I have to move it rather down). With the Q3, the sweetspot is bigger due to the pancake lenses. However, there is a sweetspot for the PCL and I think it is not a problem that it is smaller than the sweetspot of the Q3 once you have found the sweetspot.
-
I used G2, Q3 and now PCL and the Q3 is ahead of the G2; but if I had only a G2, I would not spend money to upgrade to Q3 as the difference is not sufficient to justify the additional money to spend on the Q3. I would save it and go for the PCL. The PCL is in another league when it comes to the overall picture quality. Plus, it is the most user friendly headset when it comes to setting it up as the Pimax Play software is easier to adjust than going through all the hassle with OTT and Virtual Desktop. However, if I had to buy a new headset without already having one, the Q3 is an option.
-
I works for me now, but I think Devs should make a small update to DCS that implements the new DLSS so that you do not have to manually copy DLLs and so on.
-
Ok, that is confusing now. What do I have to do use Modell K? The .dll I downloaded some days before only has Modell J.
-
OK, so DLSS probably not going to do much for you tbh. Can still use DLAA far better than MSAA especially in VR Now this is starting to confuse me. I started without VR in UHD (all cranked up) and now I am GPU bound. How can I be CPU bound in VR and GPU bound in UHD? I also checked whether the correct cores are parked (the X3D issue) which is the case. It also confuses me that you play with DLAA and Aero and I play with DLSS and PCL; if I play with DLAA, it becomes to slow, although PCL has a lower Res than Aero. nullSettings below. I also Pimax set to Central Priority Rendering Balanced and otherwise to its default resolutio. nullnull
-
It jumps between "Rendering Thread" and "Main Thread", but both CPU bound (7950X3D).
-
So I use "Quality" in order for it to use Preset J? I cannot exactly see by the graph what is limiting me, the stat screen is somehow "cropped".
-
Ok, I did it; then I went into the Digital Combat Simulator Black Shark Profile and selected "Force Profile J" - do I need to copy the customnamesettingsfile anywhere? And in DCS, which DLSS level to I select or is that irrelevant since the NVInsp setting take precedence? Also, is there an Overview of the settings/parameters that apply to each Preset? Edit: I think it works but I hope this is not a placebo ;). Looks even sharper, 60 FPS on a Pimax Crystal Light with all eye candy on, 90hz upscale mode. Frametime is constantly 11 ms, and it does not seem to be CPU limited, the 4090 is sipping ~410 Watts.
-
Thanks Zildac, the new link contains the xml!
-
In the archive is no .xml with that name. There is a "reference.xml" but it does nothave any string that includes "Preset".
-
@Zildac do you have a link to the NVPI? Is it this one? https://github.com/Orbmu2k/nvidiaProfileInspector/releases And where is the "CustomSettingName.xml"-file?
-
So preset "E" is the good, it is still part of the downloaded DLSS 4 DLLs but DCS will use C instead E? I just looked into the NVidia Profile Inspector, I cannot find any references to DLSS.
-
What is the "J" profile and how does it compare when I the new DLSS and switch DCS ingame to DLSS "Quality"?