mac22
-
Posts
196 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by mac22
-
-
On 5/29/2022 at 9:55 AM, Ala12Rv-Tundra said:
you need to buy the sound module addon, and unsing simshaker for aviatiors, go to settings tab, output mode, simultaneous output must be checked.
then you will have two columns, to assign effects individually for the jetseat and the BKjust about to set both of these devices up and run them together also(buttkicker and jetseat):
1)will try first with the simultaneous output enabled - can see this enables for both the jetseat and soundmodule 50:50 sounds for all the effects - can you provide
any suggestion for how to configure this for the best result? (note mainly flying the apache)
2)can see in the output section there is also a usb tick box for the jet seat - what does this do?
-
just about to resinstall my simshaker sound module/aviator across to a new PC -does order of install matter and also
have a jetseat just wonder the best way to set it all up ?(does the jet seat have its own software) -
just about to reinstall my simshaker sound module (after getting a new PC) - but noticed there is another software hapticonnect - just wondering if this works with Andre's software - of do the 2 do the same thing and you really just need to install/choose one? (I use it for DCS and MSFS)
note i also have a jetseat...
-
have the jet seat (not set it up yet) - also have a buttkicker that I use with andre's sound modules for DCS - just want to know the best way to set everything up so it works together? (mainly be using it with the apache) - can also see in the aviator software settings there is an output mode usb jetseat drop down?
-
40 minutes ago, zildac said:
I've not noticed that, only when first rebuilding shaders.
interesting as I have never deleted the shaders so not sure why I am getting it before the cockpit rebuild!
what folders do you need to delete to reset the shaders?
-
24 minutes ago, zildac said:
I've cleared out the cache every update and it still happens..it started somewhere back in 2.7 and before MT as I recall.
how about the black screen before the loading screen - are you getting this also? (note am running it from an SSD).
will try and clear the cache anyway to see if it helps - what folders do you need to delete?
-
11 hours ago, zildac said:
This delayed texture load has been around for a while now.
means clearing out the shader cache might not fix it?
-
6 hours ago, Qcumber said:
I find that I get a lot of blurring/smearing of images with DLAA at headset native resolution (3120x3120 for me with Pico 4). If I set PD to 1.5 this reduces the blurring/smearing a lot but tanks performance. Set DLSS to quality and this offsets the performance drop but gets pretty good visual quality. Overall much better than MSAA. I also use QVFR to reduce GPU load. I know things are different depending on your setup but this works very well for me.
getting much better frames now 60-70 running with DLSS and PD of 1.2
unrelated question - when I start a mission now getting a long pause where usually there is a black screen then get a non detailed outline of the cockpit which builds up into full detail and eventually the missions starts - get the feeling it could be a shader cache issue - would clearing the cache solve this and how do you do it?
-
1 hour ago, MIghtymoo said:
It is easy to get lost in all the settings...
The reason for your poor performance is most likely this:
You have both set a resolution of 4200x and and in additon added a PD of 1.5. So effectively you are asking the GPU to render at 6000x(!)
You should easily see 72fps with your setup if you use settings in my post and the DFR (eyetracking):
1)assume by your settings you mean that ones posted on tuesday with the screen shot?
2)yes already using the DFR but can scale back the PD
3)have you concluded the DLSS quality is worth using with some additional PD or is it better just to run DLAA? (assume when you use DLSS then DLAA is disabled or greyed out)
-
On 11/1/2023 at 6:47 AM, MIghtymoo said:
The PD can be confusing as it is a multiplier for whatever resolution is set for DCS elsewhere.
It is probably better to set the desired resolution in relevant application (for me either SteamVR or in OpenXR toolkit).
I have a Pico 4 headset and for that headset it seems to be optimal to set the resolution to around 3850x3850.
Start with default resolution and review the image sharpness. If you think the MFD text is a little blurry, increase resolution 10% and try again (I delete fxo and metashader folder each time since I change resolution). Repeat untill you are happy with sharpness vs performance.
When it comes to graphics, there are a few settings that make a major visual impact in VR.
1. Visibility range (High is the best option as on Medium trees and buildings are not drawn/visible until very close).
2. Flat shadows give that extra depth and make the flight «more alive», without the heavy GPU hit of Default (which also does not look as nice due to flickering/artifacts, IMHO).
3. DLSS quality is golden for VR. Tests on a busy Syria map yesterday with the Apache got the following results (averaged):
- No AA: 70 fps
- MSAAx2: 60 fps
- MSAAx4: 40 fps (!)
- TAA: 65 fps
- DLAA: 60 fps
- DLSS Quality: 85fps
Other than that I like to have shadow quality to Medium as it gives a very nice effect in the cockpit.
Clouds to High.
Rest is honestly just minor impact eye-candy that I can not afford to get a stable 72-90 fps.
Good luck getting the optimal settings for your setup!
1)interesting I am running a crystal already with resolution at 4200x tweaking the PD separately has a huge impact on the visuals (particularly in cockpit) - but my issues is just getting a few more fps to make sure 45 is maintained - so I will try some of your suggestions...
2)in terms of AA which one are you actually using with the best results? - and if you running DLSS Quality is it actually disabling DLAA or can both be run together?
3)really with DLSS and quad view enabled was not getting the fps I was expecting but maybe because I am running 4200x and a PD of 1.5......
-
2 hours ago, Dentedend10 said:
Hi! How do you find motion smoothing in the Pimax at half refresh rate? (ASW equivalent)
do you mean would I select it as an option - I never have and heard various stories that it is broken.....
in terms of just the half refresh (not sure if this contains any kind of smoothing?)but actually find it very smooth as long as your system can maintain the 45 its an good solution.........
problem I am having now is even with quad views and also DLSS may frames seem to move around the 45/50 level - not sure why this is but will try tweaking the PD and also visible range to see if it improves things (have had the range set to extreme most recently)
-
12 hours ago, MIghtymoo said:
Depends on your GPU. You have a pretty beefy GPU.
I am running PD of 1.9 and can have both MEDIUM visibility range and FLAT shadows ans still stay comfortably above 72-80 fps flying low over a big city in Syria in the Apache (mission with lots of active AI units).
When I go down to PD 1.8 I can increase the visibility range to HIGH.
interesting results.....do you find tweaking the range is the main thing to give you fps and what does flat shadow give you if you enable?
I am running a 7950x3d and 4090 - tried DLSS on quality with quad view running and range of high or extreme and PD x1.5 and I am getting fps of around 45-50 on a crystal - cockpits
do look amazing though I am trying to get FPS to always be above 45 so I can run 1/2 refresh rating setting - what would you suggest tweaking or should tweaking the range give me a big boost? and wondering if its worth moving the PD from 1.5 up to 1.9?
-
56 minutes ago, Hiob said:
Just leave it untouched. But honestly - with your setup, I would run DLAA instead of DLSS. If necessary tune down the PD.
actually the pixel density of 1.5 was just a recommendation I got to get rid of the 2.9 blurrys and it certainly works (cockpits are amazing!) but not the fps (guessing this is what might be impacting it......)
assuming if I select DLSS all it is doing is potentially giving me extra fps? (but by selecting it assume I will get no DLAA or AA?)
-
5 hours ago, Qcumber said:
Try pushing PD up to 1.5 and try QVFR if you are not already using it. It can produce some very good results depending on your CPU/GPU combination.
so am running a 7950x3d and 4090(with the crystal)
selected PD of 1.5 and running DLSS and DLAA with SSS disabled with Quad - visually the results are amazing have never seen such clear cockpits - only issue is with my FPS which stays around 45/50 - was expecting the DLSS with Quad might give me a FPS closer to 90? (note pre 2.9 quad was giving me an extra 20 fps!)
2 minutes ago, Sile said:No. Only DLSS is running. Cannot run both. If you want only DLAA, you need to disable DLSS.
Ok so if I run DLSS do I need to disable DLAA or can leave it untouched and it will simply not run(greyed)......
see my post above for my results - visually the result was amazing but I don't seem to be getting much benefit from DLSS or quad?
-
8 hours ago, Sile said:
VR tab of the settings. „Pixel Density“
Oh and I learned its only DLSS then, since DLAA gets greyed out once DLSS get‘s selected.
found it and set it to 1.5 (looks very good) - so do you mean U have to run DLAA when DLSS is selected?
-
18 hours ago, Qcumber said:
Has anyone noticed any differences in the DLSS artifacts depending on the map?
For example on the Marianas map I can get 72fps in the "Lagoon Patrol" mission with P47, P51 or spitfire. In all situations, the Zeros have a lot of "smearing" at a distance and pronounced ghosting close up. I get this with DLSS and DLAA alone.
In contrast, with the Normandy 2 map I can get 72 fps with the BF109 dogfight mission, there is little ghosting and no smearing. I have the same settings in both situations and very good quality.
I have not yet tested other maps with similar combat situations.
DLSS quality, 0.5 sharpening.
PD 1.5; QVFR default except periphery set to 0.3.
DCS settings. High texture quality, high scenery, extreme range, medium for most other settings.
I solved the blurry issue by increasing pixel density to 1.5 and also now not getting the artifacts and the visuals look amazing now ( so running DLSS and DLAA and quad but have SSS disabled) - only issue is my FPS is around 45/50 - so this definitely taken away the fps improvement I was expecting from DLSS and quad - how much I lost is difficult to tell......
-
I solved it by increasing the pixel density to 1.5 (looks amazing now but it hits your fps - now getting around 45/50 even with quad and DLSS on) - also disabled SSS....
-
On 10/24/2023 at 2:53 AM, Sile said:
i am using DLSS with DLAA at PD 1.3. Oculus Res Slider full right at 72 Hz.
Sharpening 0.3 plus 65% oxr toolkit CAS.
Very happy. I think trading DLSS performance gain für more supersampling is the key here.
giving these settings a try - where are you tuning the pixel density?
-
On 10/28/2023 at 2:26 PM, Qcumber said:
Try setting pixel density to 1.4 or 1.5 and then default settings in QVFR. This gives a good balance on performance and quality with DLSS. The cockpit is sharp for me and landscapes look good. I do however notice differences between maps with regards DLSS artifacts. What CPU and GPU are you using and what headset?
managed to get QVFR working with the update - but how are you tweaking the pixel density? (think you can do it in the pimax software and also there might be a slider in the the in game menu - which is the best way) - also out of interest are you disabling sss?
-
4 hours ago, f14billy said:
I'm assuming you meant DFR instead of DSR. To check if it is working correctly you can create a settings.cfg file in C:\Users\<your user name>\AppData\Local\Quad-Views-Foveated and set the parameters debug_eye_gaze=1 debug_focus_view=1 as explained in the quad views online documentation. Then you will only see the high resolution area and the surroundings will be black. If it follows your eyes then you will see it is working correctly.
Here is an example of my current config file: Those two settings are commented there, remove the # in front and they will be enabled. These settings work great with DFR and DLAA with the crystal and a 4090.
***** begin of file *****
# Common settings for all headsets (unless overriden below).
smoothen_focus_view_edges=0.35
sharpen_focus_view=0.75
# Fixed Foveated rendering settings for fallback when eye tracker is not available.
horizontal_fixed_section=0.5
vertical_fixed_section=0.45[PimaxXR]
# Dynamic Foveated Rendering settings (for Crystal)
horizontal_focus_section=0.3
vertical_focus_section=0.35
peripheral_multiplier=0.25focus_multiplier=1.25
#debug_eye_gaze=1
#debug_focus_view=1[app:DCS World]
# The settings are specific to the app "DCS World".
vertical_focus_offset=-0.1***** end of file ****
With DFR enabled you can pretty much max out all of the other settings in DCS and get acceptable performance then tweak to your own preferences.
About of PimaxXR settings of the crystal, it is a matter of personal preference. Some people prefer having it locked at half the frame rate and others would rather get as much fps as possible.
thanks for the reply and yes I meant DFR!
1)note your comment on DLAA - assume despite some of the previous comments your running DLSS/upscaling as off and DLAA enabled and you find this gives the best results combined with DFR?
2)In terms of settings was mainly referring to the in game ones - for example was reading different combinations of things such as SSS, flat shadows ,secondary shadows give better results in VR than others......
3)will test with and without the half frame rate lock - not sure yet if my system can maintain the full 90fps since the update - also will need to give DLSS a try and see if I can maintain the full 90fps or if it creates the blurriness many people are complaining about.....
-
22 minutes ago, f14billy said:
Yes 1.13 will fix it and you can just run the installer and it will replace it. Your settings should remain.
DLSS and DLAA can't be used together. You chose one or the other. I prefer DLAA because I have the pimax crystal for it's visual clarity and DLSS reduces the quality significantly.
Also make sure you set sharpening around 0.6.
ok thanks - will just update it over the top then - also is there anyway to tell if DSR is running correctly? (apart from an improved frame rate)
1)In terms of the in game settings had concluded the best results were achieved with just DLAA running (DLSS off and sharpening of 0.6 in game) - out of interests does anyone have any other recommendations for the other in game settings?
2)prior to 2.9 was also running my pimax with the 1/2 refresh rate setting selected - so it was trying to achieve 45 fps (which it usually did) - just wondering if this is the best approach now for smoothness or is it better to uncheck this option? (note running my crystal with a 4090 and 7950xrd)
-
On 10/20/2023 at 5:21 PM, mbucchia said:
I can't use partial logs. Need full logs.
You don't need to uninstall anything. Installing a new version overwrites the previous one.
> Just released a new build 1.1.3 that fixes the remaining issues with DCS 2.9.
so just to clarify - I am running a crystal and just updated to 2.9 and noticed the fps has dropped (assume DFR is not working now) - so I just need to download and run the quad views
1.1.3 and it should work again? (dont need to uninstall anything or reconfig) just install 1.1.3 over the top of the existing install? (existing settings should remain untouched by the update?)
also final questions whats the general advice in terms of enabling DLSS and DLAA together? (before this post I was running DLAA by itself with good results)
-
58 minutes ago, silverdevil said:
hello. though i do not fly WW2 missions, i suspect you need to check the ROE (rule of engagement) of the ground AI. just placing the units does not do this. they are essentially just targets on the ground. try with one unit and see what happens. also give the Mission Editor sub-forum a breeze over. there is a lots of good info. also open a mission you know works and compare settings. good luck.
thanks for the reply - note these are the "official" instant action missions for each plane - so is it possible they would not have been set up correctly or you think they might be simply targets?
so how would I load up an instant action mission in the mission editor? (specifically where can I find the file) - assume then I just need to ROE section of the unit?
also read somewhere previously there might have been a bug where flak was only active between certain hours (but guessing this must have been fixed!)
-
Running the latest DCS open beta version (using MT) and finding when I run some of SP instant action missions for the WW2 aircraft (such as spitfire, P47 or Mustang) and over Normandy map seem to be getting almost no ground/flak fire even when I fly right over the enemy (german) positions? (even thought in dogfights the enemy aircraft are firing) - just wondering what might be causing this and if there is a setting I need to change to get this working properly?(AI level for example)
cat launch animation
in DCS: F/A-18C
Posted
Just noticed a promo video where the pilot seems to grab the handle above the cockpit on take-off - is this now a standard animation or a mod? (have never seen it before when flying the f18).