Wali763

Hi. Thx for the tips, but I had no success. The first thing with the in-helmet I did not want to try since on all other modules it works just fine. Dont want to change something, thats ok for me. Second thing, was no sucess. I imported the mod-files but there was no change. I then removed the Mirage from DCS and also delete the Mirage-folders in the CoreMods- and Mods-folder. Then reinstalled the Mirage. After that when starting a Mission with the Mirage always the A-10C was loaded! I then did a complete repair and now I back to where I was before. Anyway. I managed to record a soundfile of the Mirage-Flight. Aber about 10 sec I put in the afterburner and after about 20s I extend the airbrakes, which are easy to hear. But overall I think, there has to be something wrong with my installation of the Mirage. Strange thing is, that its a completly standard installation with no mods and I usually have no problems. The Soundmod from above was the first mod in months that I installed. Digital.mp3

Hi. I bought the Mirage at a sale last year but dont use it much. Did sometimes a free flight and recently a few AAR-flights. I cant remember how it was last year, but in the few flights in the last weeks, the in-cockpit sound was very silent. I could only hear the wind-noise and NO engine-noise at all. Only the afterbruner was audible, but also rather silent. Is this normal with the Mirage? On the few vids on youtube that I watched, noise seemed considerably louder than with "my" Mirage. Some repairs of DCS did not change anything. Did not un- and reinstall the module yet, but actually dont expect much from that, since an uninstall wont remove the module from my drive anyway.

I see no reason why it should not work.

Yesterday I had (Im still in 2D) really bad stutters in MP on PG-map. Never have experienced this before. My system for 2D is quite ok. 9600K at 5Ghz, 2070Super and 32GB of 3600Mhz RAM.

On our Squads Trainingmap my RAM-usage is very high. Very much too much!

Hi. Just went back and retested my situation with the new patch. And - at least for now - it seems to have gone. After the intial loading straight 60fps with no stutters at all! Great!

Just tried the misson with the A-10C II (changed aircraft in the ME) and even though I killed all enemy units (with guided rockets its quite easy), the pickup-helicopter crashed. My guess is because of the trees in the LZ, that it hits.... Also strange is, that with the CBU I do not stand a chance killing the infantry in the forest; usuall have to use Mk82s or better the gun. But then again, I usually have trouble usting CBUs correctly or precisely.

Thx for the tip. Never tried that in the Viper, even I saw it on the INS-Switch. Saves quite sime time!

In MP I have to usually coldstart so in SP its 95% Auto u d FFWD. Also depends on the module. I see no reason to wait for 8 min in the F-16 to have proper alignement. Didnt know, that one can autostart the Tomcat as stated above. Have to check it out.

Hi. Actually that comparison was the reason for my question since most of the comments up to now stated a much larger sweet spot and according to some testers comments outside of this forum "my" problem should have been solved too. Same for the perf requirements, which should be quite the same. Thats why I just wanted to have some confirmation from within the DCS-community. About my attitude towards VR, Im sorry, I am not yet able to follow this religion. At least it seems, that it is religion for some. But Im not giving up on it (VR not the religion!); thats why I ordered the G2 in the first place, since it promised most of the things I did not like on the G1 to get resolved. Anyway, testing the unit for a few days will not render it worthless, so I will give it a try. That way I can judge for myself and can avoid asking phone typed stupid and unanswerable questions here. And maybe the G2 really will make me think, that Im a real Combatpilot in a real plane then! Only wearing socks!

Hi. Given your experience in VR you just have given an answer to my first question instead of telling us, how great the 3090 is. We all know that already. Thx

I got two questions. Im on monitor right now and find it quite pleasing. Owned the G1 in spring briefly but sold it pretty quickly. Hated the stiff cable and disliked the fact, that only the center was sharp, so a quick glance at some lower positioned instruments without moving the head was not possible. With the G2 is this now resolved or do you still need to move head which seems very unnatural for me? Second thing: I own a 2070S and for sure will not throw money on those GPU-manufacturers (especially Nvidia) for the forseeable future. May others let themselves get fxxxx over, I most certainly wont. With the G1 perf at 100% resolution/SS was not great but still ok. Ive seen comments, that G1 and G2 seem comparable perfwise. Is that common understanding? I should get the G2 in about 10 days but am thinking of giving it to a someone else before opening for the price I haved paid. As already stated Im happy on monitor and up to now neiter G1/Rift S/Index gave me a great experience since it seemed I was tweaking more than actually playing DCS.

After rethinking and retesting another mission (SyriaChemStrike, where I exchanged the B for an A and did not see a real difference) Im not sure, if my case is not too specific (maybe only on that special Trainingmap??) to justify a bug-report. My system is a i5-9600k, oc-ed to 5,0Ghz, 32GB of 3600/CL16 RAM, RTX 2070Super, Samsung 970Evo 512 GB M.2, 1440p 144Hz-monitor. Usually (when not capping for TrackIR I have up to 120fps higher up, and down to ~45fps low on Syria-Map. I had it in my bottom-line but after the forum-update thats unfortunately gone and I have not yet taken the time to look into this. Anyway, I will investigate this further and report back if I find something conclusive. If you say, getting a 9900K would solve the issue, Id surely do. They arent that expensive (330Euros) anymore right now. Actually much better value than the overpriced 5xxxX from AMD right now. :smilewink: Thx for your help/input anyway and sorry for the stress.

Hi. All this is rather unscientific, I know. Im on monitor/TrackIR. Plz see the pic. I did this a few times and the results are moderately consistent, but I would not call them conclusive. In the same scene, the Hornet had almost no stutters (=> spikes) at least none I would witness, but the F-14A had more than the F-14B. In tests done earlier, the difference between F-14A and F-14B were more obvious then in this "round" of tests. Still I can say, that I almost never experienced stutters with the older B-model and this only came to my attention when testing the newer A-model. Nevertheless, I found that exchanging the SC-Theodore Roosevelt with the non-SC John Stennis resolved the whole thing almost completly. I kind of feel, the deckcrew could be causing this, since often such spikes coincide with them doing something like giving signs etc. So my guess is, that the Supercarrier (known to be CPU-hungry) in combination with the Tomcat (also known to be a bit more CPU-hungry compared to eg the Hornet) might cause this. So my plan is to avoid these situations (on this big Trainingmap) for the forseeable future. I just used this one anyway to do some familarisation with the A-Model and to do some stresstesting to my system since as mentioned above some crashes happend on this map. Still, from doing this mission-start about 40 times now, I saw the A-Model being consistently more stuttery than the B-Model.

Hi. Im on monitor/TrackIR. In our squad we have some training maps, one for Syria. When spawning on the Theodor Roosevelt (SC-module) on that map with the A-model all is very stuttery on the carrier, meaning, that I have usually ~55fps but with big spikes in the frametimes, which makes the image stop every few seconds for a blink. Plz see pic. Looking at a E-2 taking off in front of me, it stops for a few times running down the catapult. Also the deckcrew is kind of brake-dancing.... After the E-2 and S-3 have taken off, Im alone on the deck and still when aligning for the catapult, the deckcrew is doing its brakedacing... terrible! With the Hornet or even the B-model, this does not happen and I usually have the 60fps (I capped it at for TrackIR) and only tiny spikes (which do nothing regarding stutter). I also had three recent crashes (Windows or only DCS freezing) on that map and Im still not sure, if this is realted to DCS/F-14A or a bad OC. About the latter I tested a few things and increades Vcore, but still had one crash since then. Also went to CPU-stock or even to 5,2Ghz from my standard 5,0Ghz. Stock did seem to make it even more shaky but 5,2Ghz did not help at all. I have a tracklog, but hat is 5,01MB, so too big for an upload. But I can easily provide another one, if needed. Once in the air, its not a problem any more. In general I rarely have witnessed stutters on DCS with my settings, thats why im reporting this. Its not a too big problem for me, since Im usually prefer other modules, that have not problems, but since the A-tomcat came out just this week, I spent quite some time getting used to it.

Is this correct? Yesterday at 20000ft with 2 XT, 4Phoenixs, 2Sparrows and Sidewinders I was unable to reach Mach 1. Just wanted to give the missiles some added speed....

When I got my I5-9600K Ialso had to check the bios on my (then) Z370-board. Did not need to update it at first but did some back and forth flashing without hassle later. Dont see a big difference to the current Ryzen5000 situation now. The last video from gamers nexus, where they found, that a 4xRamstick vs 2xRamstick on Ryzen5000 offers up to 10% more perf is quite interesting. Even Im a tiny Amd-fanboy Im a bit underwhelmed by the new genaration. The 10900k still looks pretty strong. I dont see, why Rocketlake should not beat Ryzen again gamingwise. Best solution for me right now seems to wait for Zen4. By then we also should have a clearer picture where DCS is heading (Vulcan/multithreaded etc). @LucShep I did not read all of your posts, but I think in your comparisons you forgot, that for a 10700k you need a new board, which is also some 130e+ for a cheap one. And also a stronger, more expensive cooling solution is needed. With AMD your chances are good, that you can reuse your current board and cooler, which is a considerable saving.

Not in the OB-Update changelog for today...... Getting frustrating. My bet is, that the Forrestal isnt included eiter... Need to do another search for the HB-statement that F-14A and Forrestal will come beginning of October. I know, its somewhere, but finding it wont help I guess....

What does suck here? HP stated that preorders after Sep 24 will be delivered starting in December, so you actually could get your device pretty early if you preordered last week like stated above. I did preorder like many back in July and still have no info of delivery date.

Common misconception I think. I had a Rift S for 2 months and an (2nd Hand) Index and a Reverb G1 for about 2 weeks either and went back to 2D in spring and am happy with that decision. And I had no problems with sickness, but only with SDE, unsharp image (could not read DSMS in A-10C well or spot an airfield 8 miles out) or an image being only nice in the middle (Reverb G1). But Im giving the G2 a try, since this might cure most of the concerns I had with the G1. Anyway, having a I5-9600K and a 2070Super, running the G1 with 100% SS was pretty fine; but I had som really bad stutters (~0,5s!!) now and then, which I did not have with the Rift S or the Index. Did not take the time to find out, what did cause this exactly since other problems pretty soon made it clear, I would not keep the Reverb. But my guess is, that the Reberb might have needed too much VRAM at times… Anyway, I think your setup will run the Rfit S with moderate settings quite well, but will have problems with the Index. Using settings on the Index, that felt reasonably smooth, gave me an image quality, that was very much like the Rift S, so no real gain here. Since I ordered the G2 back in july, Im positive to receive it in maybe 2 weeks. My wife gave me the order, to keep this headset for at least 2 months before reselling. But Im positiv that the G2 could be my final VR-brakethrough. But the prospect of staying in 2D is not dreadful to me anyway..

First off: this discussion IMO mostly is relevant for VR, since for monitor even my 2070Super (like I have) is ok. I "only" have a 1440p monitor, but have usally 80+fps (low in Syria down to 50, highs up to 130+); with a 4K monitor, fps are lower, but still above most peoples requirements and there is also the TrackIR-Stutter anyway.... New gen cards could let me set the rest of my stettings to max, which would make very little difference overall. As for VR (I should get a G2 in the next weeks) Id personally prefer a 16GB-card. As for the 256bit, from what I heard AMD did lot of internal comparisons (with 384/512bit) and that infinitycache came out on top. But right now Id try to run my G2 on my 2070Super, since with the Reverb G1 the experience was quite ok. I only sold it for some other shortcomings, not performance. What seems more interesting to me is that SmartMemoryAccess-thing. May this can help resolve some of the ingame stutters (especially on the G1 I had some occasional, but bad ones) which would make much more difference than going from 45fps (with motions smoothing) to 90fps or 100% to 200% SS for me. And as for features, I dont think RTX is relevant for DCS right now. When its is finally implemented in DCS we will be for sure on nextgen cards already. I dont think, DLSS will be implemented into DCS, so a more general (in the driver) approach of AMD might be more helpful for DCS. But that of course has to come first and also work. And even then it has to work in VR too. As a general approch NVs-drivers might be still better, but Im sure AMD isnt that stupid to develope first-class hardware, to only offer poor software afterwards. Right now, there is an unopended (but secondhand) ASUS RTX3080 quite near to my place on offer for a very reasonable price. Still those 10GB of VRAM keep me off going for it; and also Id like to try the G2 with my current card first also. Nevertheless exciting times right now and I firmly hope, that Nvidias dominance is over, but I also hope, that AMD is not getting dominant too. This can only be good for all of us and meaning competive prices and faster development. Im pretty sure, if AMD would have not posed such a threat do Nvidia, the RTX3000-series would have not turned out that potent.

Ok, thx! ;-) Actually in the misson where that situation occurred again and I decided to make a post here, I told the wingman to RTB. But he did not react, I guess since the lines were greyed in the comms menu and I did not hav the proper frequency. I guess, in such missions the wingman will only RTB to the preset homebase in the mission anyway.

Hi. Im not an expert on the Viper, just know the basics and also dont read this forumsection. I did not report/ask this earlier, since I thought this will be corrected anyway, but up to now it has not. In the PG-AAR-Quickstart-mission after sucessful refuel I usually land at Kasab or Fujairah and only sometimes at Al Minhad. In most mission on (straigt-in) final approch the wingman comes along on my right side and then starts to "jump", meaning, going up and down very quickly in a very unnatural way. Like gaining 200ft one sec and loosing them again the next. I did browse the bug-section, but did not find a reason. Has anyone the same problem or can give me an advice, how to stop this wingman-behaviour?? I have a trk-file, but since it was bigger than the allowed 5MB, I uploded it to Dropbox. Link is here: https://www.dropbox.com/s/ys09a2duyow5j6u/AARTest.trk?dl=0 I tested the replay and it work flawless until on glidepath for the landing; there I drifted to the right and crashed (in the replay, not the original flight). Nevertheless one can see the "jumpy" wingman easily. Thx.

One more reason to not buy Nvidia right now. According to the leaked benchmarks, BigNavi´s raytracing could be only slightly better than the 2080Tis but in other areas be even better than the 3080. I also dont think raytracing will make it into DCS before the next series launches. So this is of no consideration for me. Nvidia could be in a tight spot right now, if AMD really can catch up and offer good availability. Going to TMSC 7nM will take some time, but gains also will be mostly on the efficiency-side. I would not expect 10%+ perf from that move, since it only would offer slighly higher clockspeeds. But going that route (4000 series early next year) for sure will piss off many people, that bought a 3080 (with only 10GB of RAM) or 3090, just to see their card being old after only a short period of time. Competition could only be good for us. Even though I think, that the CPU-bottleneck still is a problem and will keep us from finally getting good fps in VR, even GPUs are getting faster and faster.

A few months back I somewhere wrote, that a 3080 will increase max fps or offer higher settings, but min fps will not be affected much due the CPU bottleneck. I kind of feel affirmed...