Wali763

Thx for you input. I used the setup-guide from Thud but that did not help. He is always talking of frametimes in the low teens. Well, if I have those I dont need ASW anyway. Because, then Ill have 80fps all the time. My frametimes are usually 20-25 fps, just that I stay below 25ms most of the time to get smoothing from ASW. About the CPU Im pretty sure, Im ok there. On the tools you mentioned and also on Afterburner or AorusEngine I have always low overall CPU-usage like 50-60%. But if I crank up PD (which is a GPU-task), fps goes down, so Im pretty sure, my system is GPU-bound. My reasoning is, that if the 208oTi increases my frames by 25%, than I could use that to set a higher PD. But as I said, 1.7 vs 1.3 for me makes no difference. I could also "invest" that higher GPU-power into more fps with my current 2xMSAA and PD 1.3 and therefore "iron out" the rest of my sub-40 drops and maybe get more time with 80fps. Still both instances for me would not be worth the extra money to be spent. Better to wait for the new generation later this year.

Stupid question: a rtx2080ti gives according to many benchmarks about 25% more fps than my rtx2070super. When I up my settings, so I get 32fps instead of my (min) 40fps I aimed for, will this give me the same imagequality I can expect of a rtx2080ti at 40fps? That would be very little like going from PD 1. 3 to PD 2. 0 (2x MSAA on). Generally I have so say, that I dont see a real difference between PD 1.3 Im using right now and PD1.7 or 2.0. Its marginally sharper but has actually no impact on legibility for me. Im very new to VR and the imagequality for me is pretty shitty compared to 2D so those tiny differences from different PD-settings dont bother me much. I did already do quite some testing and I cant do without ASW and therefore accept the ghosting. Looking outside and everxthing stutters is way worse for me. Still the biggest complaint I have is the (partly massive) shimmering (aliasing). Trying as PD 2.2 also did not change that. MSAA helps, a bit but still not satisfactory. But Im slowly accepting those shortcomes and cherish VR more and more.

Not trying to mock you, but the first thing I thought reading this was, how easy it is to pull 7g while checking my 5 (Im too old to see my six) and only wearing socks! :smilewink: You may be right in saying "as real as it gets" but thats still miles away from the real thing. There is nothing in any sim/game that can reproduce the Gs being pulled or the stress of flying above enemy terretory and having a RWR singing to you.... Being a recent convertie from monitor to VR I still badly miss the resolution and general imagequality. Eg closing in on a S-3 tanker 0,2 miles out the S-3s wings still look like they are only made of two rows of pixels.. But Im getting used to it. But the 3d-experience of VR of course has its great sides (like being a better pilot) and that why Im not planning on going back to only monitor. Still because of some of its deficites going to VR overall has not increased my experience with DCS drastically. Maybe once we have 2x4k HMDs and dual RTX4080Ti-setups in DCS 4.0.......

I think its great to get a new map. And one for free. When I checked the area I right away thought lots of ocean and little landmass. But as stated before, this für ED is a perfect map to test new things, probably easy to build and to service. And those new things will also benefit the exiting maps in the future. And its something different too. Then we have NTTR with only land and Marianas with mostly ocean. About realistic scenarios: since Im often taking off a US-carrier in the black sea, I actually dont bother about this anymore. And I also almost exclusivly fly in the Normandy-map with jets. All of that does not take away the fun (and frustrations) DCS has to offer.

Hi. Could you plz post the video, since I do not understand why someone would need a WYPDSG for the IR-Mav. Only thing I could think of is to get a general idea, where to look for the target and not you is doing the lasing. Much like the coordinates a JTAC gives you. But to aquire the target you need an active laser on the target anyway and from 5 miles out, looking at the searching triangle in the HUD the scan-area seems to be way larger than the mentioned 300-500m, so even being that far off, it would normally result in a lock. But I got another (slightly off-topic) question regarding the Mav: Is there a button to initiate a tracking-attempt of the Mav like the TMS-forward in the A-10? When I do a TGTDSG with the Targetingpod the Mav (non-IR) will slew to that point (eg tank) but will often not automatically lock onto the target. My guess is, that actually the Mav tries to lock automatically but (as in the A-10 often too) only get a lock very close to the min range or sometimes even fails to get a lock. But I was not able to confirm my assumption yet.

I also had problem with the Rift S not being recognized by Windows correctly, which resulted in only one "Rift S USB hub" in the device-manager instead of two. I then got 10 days ago an USB-PCI-card, but that did not work either. But I also did not take enough time to find a solution. The card was from Digitus and quite dated (came out 2012) and has a Via-Chip on it. Since Win10 only recognizes one device (should be three) I had to install also the drivers from the CD and then also the USB3-hubs were recognized. But then OculusHome said USB not compatible, even having most lights green. Uninstalled the drivers again and only use them as standsrd USB2-ports for keyboard mouse etc now. Also did not try more, since I got on the same day the powered USB-hub, that solved it for me. That powered USB3-Hub is from Anker (https://geizhals.eu/654288778) and except for one occasion the Rift S works without problems now. Maybe 15-20 hrs DCS and for sure 50+ startups now. I have it always connected, though stored in a closed and cushioned box when not in use. As said above, the related Oculus-services are not started at Windows-startup, but only with OTT and also get shut down, when I close OTT. Only problem here is, that OTT cant startup OculusHome by itself. When doing so, at OculusHome startup it says something like "checking system" and after 1 or mins recommends a repair of Oculus home. So I start Oculus Home manually after OTT. The one occasion, where it did not work, was when I installed a new .M2-SSD exclusivly for DCS and transfereed all 170GB to the new SSD. At the next (or one of the next) bootup, the Rift S was not recognized. But since that all is ok. Im far from being a fan of Amazon since I think its along with Microsoft, Google and Facebook VERY problematic (and as a sidenote more problematic than Huawei), but my statement I always made, when my wife again ordered somthing form them seems to really be true: "There isnt a problem, an order from Amazon cant fix!" :doh:

The annoying thing about those Oculus-background-services (OVRServer_x64.exe) is, that they are running all the time; even if Oculus Home is not running/started. And looking at the tastmanager its using quite a bit CPU. Usually in the range of 0,2-2%.... I now change those services to be started manually and let OculusTrayTool do the start. So the services only run, when Im actually using the headset.

I have kind of the same setup as you do and I currently run PD 1,3, 2x MSAA 16x AF and textures high, cic traffic low, shadows flat, trees 90% and most of the other tings like lensflase etc off. If it looks shitty compared to monitor get used to it. Thats VR in 2019. Maybe 2025...... The small FOV is almost no problem for me anymore, and Im getting used to he low resolution also but Im still struggling with the aliasing/shimmering big time. On the carrier the island quite often looks like a christmastree! :cry: Other than than, VR of course gives you a (remote) feeling like your sitting in the plane. EG when I close the A-10C-canopy I want to pull my right hand back to not get it squeezed since Im have my stick on the right side. So VR really makes it feel real a bit! BTW: My Rift is now running without need of several hotplugs: I got a powered USB-hub, that solved it for me. I also tried a USB 3.0-PCI-addon-card, but that did not work. But I guess the card was too old since it came out 2012.....

Havent got my USB-hub yet and still am fighting to get the Rift S being correctly found by the system (having 2 "Rift S USB Hub" entries in the device manager). Yesterday I had to try for one hour to achieve that. Usually its takes a few minutes. Which of course is still a few minutes too much. Anyway, Ive done a lot of testing the last two days and Im not sure, if I have learned much. It seems, that yesterdays 1,5 SS in OculusTrayToll or PD 1,5 give other frametimes than todays. But contrary to some other people opinions/experiences ASW for me makes a big difference. Ive made two missions for testing: F/A-18C low (300-500ft) over a city in Normandy and Caucasus. I think both of them are rather extreme and normal flying higher up, will render much better fps. Trees in Caucaus eg (set to 90%) dont do almost nothing to me, which tells me, that my two scenarios are a good referencepoint. With ASW looking outside at my three during a steep banked turn gives no judders, only if the system drops beneath 40fps, which in Normandy it does a few times flying so low. Without ASW I get up to 60fps in the Caucasus-mission (less in Normandy) but looking outside its all juddery. Going to Auto (or without OTT) is kind of the same as ASW on. About SS/PD Im not sure yet. There is a difference between 1.0 and 2.0, but its not big at all. Im referencding some buttons/labels inside the cockpit and those seems to be a bit clearer, but IMO not worth the performance-impact 2.0 has. Outside Im not sure, but seeing the ball still is hard for me. At maybe 2miles I see some green dots, that get easier to see, the closer I get. At maybe 1 mile I can see the balls red/orange dot. But I cannat understand somebody claim, he can see them clearly. Right now Im on 2x MSAA and PD 1,3 without OTT and probably will leave it that way. Yesterday when testing eg ingame PD 1,5 vs SS 1,5 in OTT had a much better output in fps for ingame PD (~20ms vs ~24ms) Today this difference was not obvious; most time in my two testing-sceanarios Im scratching just below 25ms to get 40fps and therefore a "smooth" ASW experience. Of course this findings are personal and with my specific system. But I dont see, a RTX2080Ti giving me MUCH more room to up things. But next years RTX 3080Ti is definitly on my list. Also my IPD of 66,5 might not be beneficial; maybe at 64 I could see the ball a bit better. Anyway, the testing also had the result, that Im more and more getting used to the visual deficits compared to the monitor. :megalol: So going back is getting unlikelier. But it hasnt change my opinion that VR in DCS still early Beta-quality

Hi. The patch from today solved my problems. I flew over all of the seven new airfields and textures were fine.

Im hoping too. But right now, Amazon-tracking says, the hub is south of Milano, which would be way wrong...... The new M.2-SSD for DCS is also in that parcel! I can follow your reasoning and also think its a USB-problem, but more powerwise than bandwith-wise, since I always plugged the Rift S directly into a Mainboard-USB-port. Ive read, that some USB3-ports before the OS has loaded completly only offer USB2-functionality, therefore less power and bandwith. And my USB-Ports on the mainboard also are under power also when the PC is shut down. Thats why I have a hub for the Warthog/pedal and TrackIR, that I can turn off. When I build the PC ~ 6 months ago, I was not able to turn those USB-ports completly off when I shut down the PC, neiter in the UEFI (where there is no option for that) nor in the windows-settings. But I thought by plugging in the Rift in only after complete Windows-startup, would circumvent that.But in fact it does not work every time, so there has to be more to this. This evening I will try to find the solution to turn off those USB-ports. Maybe this will solve my problem, even before my Hub from Italy arrives....

@ Chapa Thx for the advice. I also tried to free up all four backside MB-USB3-ports with the Rift being the only pluged into such a port. Keyboard and mouse were on the other USB2-ports. Front-USB3-ports were also unused. Still did not work. Normally I have the hub (with a on/off-switch) for Warthog and pedals plugged into a back USB3-port BUT switched off and one pair of also switched off Minispeakers. Only after correct start of the Rift S I power up the hub for the Warthog. But Ive ordered a powererd external USB3.0-hub (chipset unknown) that I hope to receive by Saturday. Lets hope for the best.... If that also fails I might test your proposed pcie-card. https://geizhals.at/logilink-2x-usb-3-0-pc0054-a503423.html?hloc=at&v=e This one seems quite similar to your proposed....

After 5 months of deliberating if to go with VR and twice rejecting the thought after testing the Rift S and than the Reverb I finally decided to keep my second Rift S I got last week. I still firmly believe VR in general and VR in DCS especially is far from matured and has many cons but after maybe 10-15 hrs its just too hard to go back to only monitor so I guess Ill have to get used to the things I dislike (poor resolution, lots of edge-shimmering, poor performance, overly complicated setup (eg for a WMR headset you need WMR, Steam and SteamVR running; for the Rift only Oculus Home with an optional tool) and a higher strain on the eyes). I just hope Oculus can resolve those connection problems. It usually takes me 2-3 attempts (up to 10 min) to get the Rift S running, usually un-/reconnecting the USB-cable very often.... But it seems, that Im still lucky since once connected I did have no problems even during 3 hrs playing. Just on restarting the Caucasus F/A-18C 9X-mission tracking is going wild. But Oculus wont see any further money from me (for other apps/games) unless theyre able to resolve my connection-problems... Still the greatest thing in VR for me s GoogleEarth-VR. This is constantly giving me wows! :-)

Hi. Already did two repairs of DCS, but it did change nothing. When Im starting a IA-mission the new airports have no textures. See pic. Right after entering the misson, go to F10-map, than chosse Sat and you cann see, the missing textures for the mentioned airports. If theyre not there, there not their either, when you fly over them. I did a ME-mission once, just open the map, place a A-10C above such an airfield and started it. That way, only the textures for one, the most soutern airport were missing. IA-missions in the A-10C, F-14 and the F-86 all resulted in the mentioned problem. Also some creeks seem to run uphill sometimes. ;-)

No shimmering trees anymore!! Only made one brief flight but had some missing textures around three airfields in the south. Looked like a chamoflage patch with 'textures missing' written over it.... Made a screenshot but did not save it.. Will recheck and maybe try a DCS repair. Performance lower down still seems to be a bit problematic. Still this is a great and unexpected update. Looking forward to Syria, that a sure buy for me.

Didnt they say sometimr in summer release "this year"?

I personally cant follow the argument buying a module to help ED. Even thought I did this once. All other modules I bought out of interest and actually theyre too many for me to learn anyway with my personal situation. I perferred if ED made modules so good that people wanted to buy them. I think, even this market is a niche, if you deliver a great product, many will buy it and that should keep the developer healthy. Personally the carrier (if decksliding is solved) is such a thing; but also new maps would be a must-buy for me. Still at release in EA it should have some decent standards, not like the F-16 (that I wont buy for now) I consider myself poor average but Ive sent north of 500 Dollars EDs (and its third party companies) way only in the last year and will do so willingly in the future if new DLCs are interesting for me. Niche or not, this should be enough to keep a company away from the need of "support" buys.

I currently also run 2x MSAA and 16x AF with most things on high (except civ traffic), shadows low and heatblur, depht of field, lens effeect, motions blur and SSAA off and get mostly 40fps in single player, which is good for me. I found out (also on monitor) not to look a the fps. If it is ok for me, its ok, no matter if its 32 fps or 95fps. About the shimmering: its kind of like the shimmering of the trees in the Normandy-map. For sure comes from edge-smoothening. Next time Ill try to delete the shader-folder after changing settings. Maybe this will make a difference. Especially since from 2x MFAA to 4x MFAA it dont seem to be a difference... I also think, the Windows not recognizing the second Rift S USB Hub is probably a driver (conflict?) thing, because once ok, I was able to use it for two hous without any hassle (except for my Warthog to go dead for a few seconds twice.....); its plugged into one Mainboard-USB-outlet, whereas the Warthog is on a 4-way-hub with the pedals After all I guess, I will have to do a complete system-reset; I already hate thinking about that!

After buying a Rift S (in August) and a HP Reverb (in late September), but sending them both back, I out of an impulse bought a Rift S again last friday. I just thought, last time I did not give it enough time to test everything, so maybe I missed somthing.... Well, after putting in quite a few hours now, most of my concerns I had back in August, still seem to hold true. The thing, that right now annoys me most is, that I cant get it to run without hassle. I reinstalled and repaired Oculus home multiple times and removed and reinstalled the drivers also a few times (in all this took quite a few hours), but it seems, that my system does not want to see the second "Rift S USB Hub" in the device manager after startup. Sometimes its ok, if I just unplug the USB-cable and reconnect it, someting I have to swap to the Admin-Account and manually remove the device with the yellow exclamation-mark called "unkown device; link in compatibilty mode". Anyway, it usually takes at least 5 -10 minutes to resolve this situation to get the green lights in Oculus Home. But thats not my question: I really do dislike all the shimmering going on. Using 2x MSAA helps a bit (with 4x I dont see a difference). Especially the sea looks very bad. Going to low water quality, resolves the sea-related shimmering, but then again, the sea looks boring, not to say bad. Is there a solution to this problem? I tried 4x MSAA or 2.0 PD, putting everything to low or high, but nothing did help. One thing I like about DCS is its visual fidelity. Especially the sea looks IMO quite stunning on the monitor. But VR takes that all away... The other two things I had concerns about, firstly the poor visibility/resolution into the distance including SDE and the small FOV I could get used to. Well, the FOV already isnt a real problem anymore. Still Im not sure, if I will make the move to VR. After a few hours playing in VR I reverted to monitor again, which felt strange at first but I quickly got used to it. Still chances are higher for staying then reverting right now. If I decide to stay in VR it will be for sure the Rift S, since I do not expect much better experience with the Index, let alone my Hardware would be to weak for it anyway for reaonable settings. The Reverb I will not touch anymore for its bad cromatic abberation.

Thx for the input. I tried that and it was the solution. Stupid beginner-mistake! If you make a precise designation with the Liteningpod, MavF will accept (lock onto) the target when undesignating it on the run towards it. About ship-mode: I used both and both worked (when I did not run into above mentioned problem).

Hi. Seems I dont understand the whole thing. I did a mission (Exigent Riviera, Mission 4, nightmission) a few times, where I had to attack a Submarine with the MavF. Before that I searched for the sub with the Liteningpod and put a pointtrack onto the sub. I then seperately slewed the MavF to the sub and made the attack. But in some of my attempts to do the mission I (accidently FLIR-page on the right DDI still active and not the Mav-page) pressed the TDC-depress-button (needed to slew the MavF-seeker) and therefore did a targetdesignate, which was seemingly transferred to the MavF. That was nice, but I was not able to correct this tgt, since it was slightly besides the sub and the Mav-indicatior in the HUD was crossed out and not ready for an attack. After that I was not able to undesignate the MavF again.... I was able to change the tgt to another point (again depressing TDC-depress on the Flir-page), but I was not able to clear the tgt so I could do a manual lock on the sub for the MavF. And on uncaging the MavF it always went for the tgt-point and I was not able to override this and make the manual lock. Whatever I did, the tgt-point crept up; I even made tgt-designate to preset WP and undesignated it again. Still the MavF went for the last designated tgt and the diamond in the compass-band in the HUD came up again. I tried this on an other test-mission too. Once accidently pressing TDC-depress on the Flir-page made the MavF unusable. Anyone know, what Im doing wrong? If somebody is questioning, why Im using the Liteningpod before using the MavF: for me its just much better for spotting vehicles.

Looks great. But will only buy it, if the decksliding is resolved. Really annoying situation right now.... But Im optimistic, that ED want my money...

Throttle has to be on idle. Other than that Groundcrew will tell you "cant comply". Gave me some headaches....:lol:

Hi. I just added the CAM since in the description of the compaign it was stated nessecary. Did not add any planes myself either. Right now Im doing the campaign mission by mission, meaning I open a specific mission in the campaign-folder and not the whole campaign. I know of the possibilty to open the missions in the ME and remove items; did that with the InstantAction-missions quite often. I will try that, if the removal of the CAM does not help. Thx for now.

Hi. Thx for your help. Just did a cleanup and repair as suggested (which only removed 5 Tomcat-liveries) and did Mission 3 in Exigent Riviera again. Let myself get shot down by the SA and DCS crashed again. See pic. I then removed the Deckcrew- and CivilAircraft-Mod from the mod-folder, but then could not restart the mission. Put back in the Deckcrew-Mod but not the CAM, and let myself get shot down twice. But in both cases NO CRASH. I will do the other missions from Mission4 upwards and try to verify, that the CAM is the culprit, that is causing my system to crash. I attached the crashlog from the first try (cleanup and repair but with Deckcrew and CA-mod). dcs.log-20191124-213651.zip