Boosterdog

Lot of folk telling you the water is warm but none are asking if you can swim. DCS is currently a monster performance wise. You'll need a good (read expensive) system to run VR even half well. I think the price of admission starts somewhere around an 8th or 9th Gen I5 K chip with a 1080TI. And that just about gets you in the door.

Ah you missed the secret magic word "Hobbit" !

This is true.

Without knowing your system specs and how much you are willing to pay, I think its a difficult question to answer. One thing I definately recommend is deep pockets.

Ah, but are they? A-hem. And I quote... "At any rate the arms, at a short distance from the trunk, were not wrinkled, but covered with a brown smooth skin. The large feet had seven toes each. The lower part of the long face was covered with a sweeping grey beard, bushy, almost twiggy at the roots, thin and mossy at the ends. But at the moment the hobbits noted little but the eyes. These deep eyes were now surveying them, slow and solemn, but very penetrating. They were brown, shot with a green light. In my deep research of this subject (30 sec google -foo) someone actually asked how ents reproduce---now theres a rabbithole if ever I saw one. BTW - Ill be in all day to receive my "Pedant of year" award.

Its good advice however its not the panacea. Not that you said it was. Im not inferring that. I run windows on Sammy 980 pro M2 and DCS on a WD Black M2 using a 4th Gen PCI interface. . Aside from the graphical demands of the module itself, which is the focuss here, the nature of its use will bring it into contact with a lot more AI routines for its targets (at least in SP) and will likely do so in environments where other factors such a destroyed zones, smoke, AI route finding and AI coms are at play. Add to that the increased demand of low level use on a PC and for an older single core application like DCS (currently) its a perfect storm. If you own the Mi24, play the PG disaster relief mission to observe how a relatively simple mission can stall even a decent PC when AI takes centre stage (i hope it not just me :-)). Until Multicore, its implementation and its effects within DCS itself are a known, the true performance of the Apachie, as a full package, will not be a certainty. I am hopeful as I cant See ED punting out on two attack helos in a short period of time (3 if you include BS3) without considering this.

I see it in lots of AI stuff. Activations, mortars firing after setting up, AI vehicles commencing route finding, AI tasking. Looking at the very basic info in the task manager there are big CPU spikes whenever these occur which momentarily impacts on the GPU. More obvious in heaver missions or when the GPU is loaded with lots of high desity stuff like destoyed buildings or cites of when lots of AI tasking is happening in short order. I see it more as I use Vsync so the frames halve for perhaps 2 or 3 of the 60 cycles in the given second it occurs. Even without vsync however a group of AI troopers opening fire on you for the first time can knock 25 fps out of your sails for an instant and upset the flow. DCS runs everything but sound on a single core. My hope is when multicore arrives such issues dimish or cease complately as AI tasking is hopefully shifted away from the core doing the rendering.

Changing the view distances causes DCS to reboot I think. Map view distances and LODs are all over the place as well. High in the Caususes is like Extreme in Syria whilst a perfectly rendered building in the PG becomes be an amorphous block in Damascus (and dont go rocket a shack for a tower block will spawn in its place! :-)) The game graphically just isnt as good or as optimised for Helo's as it is for jets and props as it stands. Its not awful by any means but popping detail and glitching shadows certainly detract. But here we are. Cant fly a hip, hind or apachie anywhere else.

Its something I used to do and it does help a little. The big however though is that you really need to stay in the weeds at all times not to see the effect (especially if you are used to higher settings). ED will state that they have differing levels of rigs not just high end ones. On an "average" rig, things have to be turned down for certain types of play and for certain modules. The concern here is that the type of play (down low) and the module (hi res duel pit multi MFDs and Rotor annimations) is going to be a very demanding application. If you can play DCS now, I doubt the Apachie will break it. You may find times where your old settings are asking too much of your rig and you will need to scale back some of the graphic options. The question is by how much. And how much "give" is too much. If you are already dialled back and still on the margins then it may be a problem at least until its optimized further and Multicore/Vulkan (cant we just say MC/V??) comes along. That said MC/V is still a complete unknown. If I take the F18 with its screens etc and place it on the ramp I can happily sit there with 100-110 fps. F14 about 85-95 fps. Thats will all the goodies on but on a 1080P 2D screen. Put the hind there and its 75-80 fps with no mfds to render. I imagine the Apachie may be similar to the Hind in similar situations but may suffer more in operation when the MFDs are displaying targets and it its below or just above the tree line. The difference between say an A10 (which can sometimes show issues with the MFDs displaying images from TPOD and Mav both at once) and the Apachie is that the A10 is normally higher and, as such, is giving the system less of a headache graphically from the get go. The other factor is perhpas that although there may be an MFD in each position, if its showing the same data, the hit may not be as bad as one might fear. Until it arrives its all speculation.

The some who prefer not to see stutter when looking left or right for instance? Im a 2D-er and Track IR bound. If I cant Vsync my frames to 60 constantly, the game stutter and drops are very distracting since the whole thing flicks between 60 and 30 fps. Without Vsync the jerks and stutters are also distracting unless the fps is around the 120 mark (even though Im only displaying 60 pfs on the screen). So FPS (or the ability to provide a minimum level thereof) is very important to me. Not the overall highs but the lows percentile. Except for working out if something is wrong, I dont have a counter on and I couldnt care really too much as long as I get the 60 fps. Over time I'll turn down the graphics if the game demands but Ill check every OB patch to see if there is an unexplained perfomance drop simply to report it. You can live with a little stutter and enjoy the experience as a whole but that wouldnt be enjoyable for me. Thats all. If that biases my viewpoint it does so only to the same degree that your ability to live with stutter biases yours.

I dont know how many times I carefully craft something then called up the objects box only to hit the delete button by mistake. With no "undo" option, its a bit of a nulclear switch. Please could it be moved to a discete area away from the rest of the tool options. There is sufficient space.

Didnt some Mercuns land at Whitehaven during the American War of Independence (or the Ungreatful Subjects War as we like to call it here in blighty) with the intent of doing something nerferious. Then there's the Battle of Fishguard again in the 18th Century. Shores were breached, if only briefly... "Since 1066 no forgeign power has breached the shores of the British Isles and hung around long enough to complain about the weather"

He has a 3090 and a 10900K @ 5.3 Ghz. No idea what usual settings are or what they usuallly return.

He please see below thread posted in 2.7 object bugs section. Iss ue seems to come partly down to core stuff that allows surface lighting to be seens on the blind side of objacts (or possily just on carrier blast deflectors) but also down to the extet of the light cast from the cans of the F14 on AB. Thanks

From low angles of view from directly behind, the glow of the F14's ABs can been seen on the deck of both the SC, regular carriers and CV59. Heat blur effects are also present to the rear of the blast deflector for all Carrier Based Modules and AI. The issue appears to be resultant from the F14s own lighting (which I will report on the HB page) which illumninates a much larger area to the rear of the aircraft than it possibly it should n comparison to the F18 and RL images. The problem is most manifest in the F14 AI launch prceedure on the SC and regular carriers when the AI proceedure holds the aircraft for period of time before launch but is also apparent with F14 AI on the CV59 although the jet moves almost as soon as the ABs are lit . Primarily HB F14 issues but reported here since both surface light (and possibly) heat effects should not be apparent on the blind side of objects and as such a core (or at least a generic Carrier) issue. Thanks SC F18v F14 Illumintion behind Blast Sheild.trk CV59 F18v F14 Illumintion behind Blast Sheild.trk

Try it using a free trial. Its problably the oinly way you'll properly see if it suits you. The detail sliders for the structures work well on that map. you can knock em down to perheps 0.6 without a really noticable effect and gain a few fps lower down over built up areas.

I agree with this but would also say the DCS core is also becomming or has already become obsolete for the complexity of the modules, maps and world effects being pushed out. The issue doesnt just sit with the consumer being expected to PWWRRR it out because, often even that doesnt fully solve it.

Exact issue as what?

The check boxes under the "hidden on F10 map" are for selecting which players you HIDE the drawn objects from. In your example you wont see them if you are playing as a Blue, Red or Neutral Pilot but you will as an spectator or game master etc. Visible in planner is the colum to the right Under the Figures section that you have checked.

The bonzai art of optimization conducted with a chainsaw. Tis the DCS way.

Make sure the coalition or "common" is selected for the drawing layer in the Figures box binding option and that the visiable in planner box is checked.

Lasts year's Roadmap raised too many expectations which 2021 spent its time dashing. Major stuff like the engine recode, anticipated stuff like te SC development and a lot of minor but much looked forward too stuff like the improved AI models not only didnt happen as mapped but were never really spoken of again (save for a general update on the recode in Oct- its predicted roll out date). Not producing more of the same is an understandale and sensible move. However, all those Elephants are still running about in the room. So, personally, Id like to see a more concerted effort to assure us they are still coming and still on some form of track at least in 2022's Newletters and not just more Apachie, Apa(Viper)chie, Apachie, Sale.

Im sorta the opposite though I have a spitfire somewhere from years ago....... which I why I read your post and said aloud "its not a Corsair, its a Crusader"

I just spat my coffee.......Loves my harrier as much as I loves my 21 but..... I personally wouldnt hold off buying another Mag 3 product if it interested me. Ive had 100s of hours of fun out of the MiG.

If I were objecting because I would have to press a button or choose a different version of the module to fly solo in I'd agree. But thats not the case. You get your way and, without ED incorporatng position changing into MC I cant fly the Hip in MP without some limitiations. We disagree because we play the game differently, thats all. I hope we can respect eacjs other's views on it without the immfamatory comments.