Boosterdog

Given the detail thats gone into the Buff, are the wrinkes going to be a thing?

Lots of nice things and a nice mix of stuff. MB-339 is just beautiful. you can really tell its made with love. Day one buy for me. S3 looks to be in an advanced state and along with the Buff done to a much higher standard than I expected. Much higher. Very pleasing. Not sure where the Lancer is. I aint Facebooking for no one WW2 aircrft havent grabbed me in DCS but the F4U looks great. If i was told I had to buy the F4U in order to see F8 I wouldnt complain but I dont think it'll struggle in that regard somehow nor should it. Nice Start to 2022.

ED and its 3rd party partners have had £1100 of my gratutude and a further £3000 or £4000 required to use it over the past 4 or 5 years. The majority of that latter figure is down to an acceptace that as things move on, the performace demands increase and that some things that could perhaps counteract that dont move on as fast as one would like. I dont think those of us asking for a little more information about core progress (not so much a shiny new toy as an essential foundation for a single core engine on the edge) a little more regularily (not promises, not timelines, not deadlines) are asking for the moon on a stick but clearly ED and many community members such as yourself disagree. Fair comment. Asking and attempting to reason why we are asking doesnt automatically make us unwashed and ungrateful any more that accepting the status quo makes you an ED apologist or Fanboi (to take both equally idotic extremes of accusations). Now if Ive come accross as demanding such-- thats a different matter. And if have then I'll take it on the chin and thats my bad. Wasnt my intention. Any how ED have spoken so lets see what 2022 brings. All the best.

I cant recall it being so high previously though. And I dont think its changed in itself unless its some optimisation hack. At least not in the Caucuses anyhow. Could be wrong. Either way, not really a satisfactory solution if that is the case. Then again, between the VR community and those struggling with performance who even has the grass slider up and terrain texture on high? Not as many of us as once did Id imagine. Hmm - perhaps the grass slider could work vertically as well as horizontally

You dont say? I know its not huge in the grand scheme of things but it seems to be low hanging fruit to the unititiated. So low in fact it almost touches the gress. Which admittedly isnt saying much at present given the height of it. Thanks for the quick reply Flappie

I doubt they really care as Im sure they know their work is appreciated (if they dont, it truly is). If they do get dishertened then that is very sad but also indicative of how fast "Render Fatigue" can set in when little else (away from the latest and greatest product pushing) is perceived to be shared for a protracted period. DCS by its nature is a Jam Tomorrow render-fest (look at the content of your own Roadmap Thread - which I enjoy and thank you for BTW) . It has to be and we largely love it for being so because a picture does speak a thousand words. But it cant just rely on it in the absence of anything else which it can appear to do now . DCS isnt an easy "in" and the price of admission is rising so its simply unrealistic to expect an invested mass to be happy all the time withou a varied diet of information. Doing so is equally unfair on Mocap as it risks dimishing their work in the eyes of some to mere "filler". Which it certainly isnt. By what you say, ED should, by now, have a wealth of experience, good and bad, in managing communication. They should know who the the community recieves best (Wags could tell me he just run over my dog after crashing into my garden whilst driving and googling and Id probably still thank him for stopping by) and how to best impart good and bad news. Grpahics's writing and comminction style is excellent too and could easily utilised more (assuming that doesnt impact on other stuff which it probably would) The community does have its part to play and sometimes is unnecessarily overly needy and enttiled (me especially). But its not all on us all the time. It really isnt.

00:49 - evidence of someone who didnt successfully complete the field carrier landing practice part of the course......

Any news on this? The grass height is something of a unversal bug not just a Caucauses issue (though it does rather ruin that map now especially for FARPS and the like). Athough not as severe, the grass airfields of the Channel map also suffer with a scale height of about 12-18 inches across the board. The revetments look a little like Mr Potato Head whilst the runways are unrealistically covered in knee high, thick bladed grass). Im hoping that since it affects a paid map also , and in a kind of visually fundemental and very obvious way, its priority may be bumped up a little? (the tail wheel of the Mustang is off the ground BTW - not that yu can tell)

You need to disable it as a service. Type "services.msc" in the search window and open the app. Then look from the entry "power", right click on it and go to "properties". Select "disable" and restart your PC.

This is the thread that keeps on giving!!

When youre done can you get it to them to cut the grass on the airfields as well?

ED could take a leaf out of another combat air sim's book. Dev reports there are often quite detailed and wide ranging and have done a lot to keep the community on side (as much as a community can be anyhow) even when stuff has slipped and slipped again. Not every posts mentions long standing stuff and most is about new toys but the variety is there and in much greater measure than it is here. More imprtantly some of the problems that the Devs encounter are spoken about (even if not in great detail) to help the community see why something is so. Doesnt have to be every week or even monthly. A solid semi -in-depth update every quarter or even twice yearly perhaps. People just want a little reassurance that the big outlays they make and the time they invest are worthwhile. If you take the very recent bugtracker news, one perhaps can understand why we get anxious and act up when ED goes dark on something even if the descision not to proceed down the line is sound.

Or the F14 low down and slow with a Lantrin Pod active (Twin Pits, Hi Res cockpit, two rendered displays of the Lantrin image (?? long time since I flown it but I think Latrin is now avaialbe in the pilots pit) - still be speculative.

It would still be specific to his (monster) rig and his subjective interpretation. I doubt it would be any more or less informative than BIGNEWY's post who is also flying it at present. How the apachie performs is going to be very much down to how and where the individual is using it, what the individual thinks are resonable/acceptable settings and what the individual is running it with. Im afraid you will either need to risk biting the bullet for the nice discount or wait for the forums to guide you and perhaps pay a little more

The in game Vsync forces on Vsync only in Windowed Mode and is a built in Game Feature independent of the NCP. The NCP can read it however (hence the use application settings option). Im not sure, outside of Vsync if all the other NCP settings are similarily ignored in windows or if appies only to certain ones. Outside of windowed mode the in-game Vsync has no effect and the GPU software takes full charge. In not dependent upon whether you use a profile or the general settings. If you disable the in-game Vsync and just activate in the NCP you will know what mode you have launched into if you toggle on a frame counter (or use in the in-game one if you can see it well enough). If you are in Full Screen you'll see the expected Vsync cap. If you dont you are not. As I say, with the full screen optimisation box unchecked I rarely, if ever, get lauched into windowed. Here is the rub with Full screen-If you launch into the game in Full screen BUT you Alt-Tab out to look at discord or something when you return you will be in Windowed mode so will need to hit Alt/Enter to re-activete full screen. If you are using Windowed mode, Alt -tabbing has no effect because its doing what it was designed to do which is put DCS into a window that can be alt/tabbed between and the ingame Vsync will always work. I dont think this is a DCS issue. Effectively you are telling the PC "Yeah I know I wanted full screen but, y'know what, now I dont". I think Full screen is the better option but it trades convienece for quality a little. In your case it appears you were launching into Full Screen but the NCP was using fast sync so the frames rates reflected this. Any frame counter is only a measure of the engine output and not the displayed frames which is why Fast Vsync makes it look like there is no vsync at all as its allowing the engine to go flat out in order to try and populate its two flip flop buffers with fully rendered frames. If you dont use an FPS or the volume thing usually moving your head around will less less smooth if you are not in Full screen (if the games is set up as above). Alt/Enter isnt a DCS thing its a Windows X86 default for switching between Windowed and Full Screen. My understanding was DCS is windowed. If I set my reolution lower, it certainly appears in a window. As an aside. I recently found another small issue when large frames rate increases could actually affect the game and the menu and cause the chip to effectivly get stuck in a loop wth the GPU forcing frames down. This tended to stop once in game but in the menu it always showed 50 fps not 60. Adding a reasonable cap to the NCP (so between 120-199 fps) stops the error. This error would only occur if the game launched in an interation that wasnt vsynced. Glad you sorted it.

@Mustang Sadly even the Ultimate setting is a tad too strong for my needs (low blows over Damascus -unsurprising really - or not given im running a 3080 at 1080P) and my reliance on Vsync. Im unsure if the alteration to the terrains have an effect outside of the two new settings or if its my very tired eyes playing tricks on me but the final detail pop appears to be tamer across the board. Even if it is a placebo its a very useful banker for a future time. Thanks again.

This is the "cleverer people" I wuz referring to!! Thanks Mustang!

Please dont think Im de-crying this. It seems to be helping quite a few whatever the reason so well worth sharing. There are also a whole host of other things that can be reported as issues but are caused by software such as Afterburner polling a lot of things a lot of tiimes. I had an irksome tick that was caused by Avast over-zealously scanning automatically even when supposedly dosabled. That simply needed some default settings deactivating. It does no harm at all to give people information that they can troubleshoot with. Especially if it can fix something for them. There as many different takes on what TIR does and doesnt do when when the fps is away from its 120/60 capture rate as there are units sold. Some will say it doesnt affect them, others (like me) will anchor the fps using vsync as they will tell you it does. The stutters here are describes as fairly regular "ticks" which id say are unlikely to be TIR induced (usually that the "when I turn my head" sorta posts).

I think this was working ok for me pre 2.7.7 but went wobbly again thereafter. @Nealius if you have a keyboard that can alter or mute the volume one thing you can do to check with some certainly and relativiely easy is right click on the desktop DCS icon and select "compatabilty" and check the box "disable full screen optimisations". If you open DCS and go into a mission and alter the volume, you shouldnt see anything if you are in true full screen. If you do see the volume bar, you are not in full screen and you can Alt/Enter. If you prefer mot to have the box checked all the time, run the game from cold a few times to see how the ground lies so you have a good best guess. In my experience the chances of launching into true full screen first time are greater with the box checked for some reason but its not a given.

Working for me. One thing i recently noticed (others probably knew it all along) is that DCS, regardless of whether you start it from the Updater.exe or the DCS.exe uses the "Black Shark" profile in the NCP. Moreover, it appears there is one DCS.exe to rule them all (ie if I set something up in the DCS.exe for my OB install, it applied the same to the DCS.exe in the Stable version I had installed until recently. If you browse to DCS.exe and make an alteration you will see the profile defaults to "Black Shark (DCS.exe)". I assume that NCP "sniffs" for it as one of its pre-installed data basy things. Anyhoe.... are the Vsync "use application setting" options enabled in the Black Shark profile?

First. I apologise for OT posting in the thread. The pilot appears to as animated as any other jet jockey once he's without said ride. The limited animation is pretty much on par with ED's own in the F18 and A10C I just looked at. Although there is a small increase in the refinement of movement as he gets up on the latest ED modules it is very minor. I cant recall any ejected pilot doing anything different in DCS (but I never really have bothered to watch). The only difference I see is that the MiG pilot isnt grounded when he stands up. Yes it is a bug but not one most of us would die in a ditch over. Is it realy as immersion breaking as the pilot standing bolt upright and motionless like a statue in the first place? Place the pilot square on the ground and what do you have? A static lump doing nothing but staring into space for a few minutes before going "poof". But 6 scale inches lower than now. M3 were working on a new pilot for the MiG, I dunno if that is still a thing as its very very very low down on my own list of priorites. Perhaps that may bring some changes. You will have you own views (clearly) but I really dont think its a good use of a small developers time to have to explain in detail their reasoning in removing a bug report about a minor issue. If that is indeed what they have done. You may, of course disagree, which is right and proper. I post as a counterpoint.

For the stutters I have, and have always had, there is no difference. Not that I expected there to be. All of my stutters in this game come from clunky AI coding battering an already sweating single core. Whilst I remain on the fence as to whether this is a fix for DCS or a solution to a past misconfigaration/incorrect power settings implmentation in windows itself, Im happy for those it helps nonetheless.

I call it the Tunguska option. Trees and objects are removed in realivaly large blocks a lot of the time. Sometimes the blocks make sense, sometimes not. Sometimes its good as you dont need to define the area too accurately, sometimes it leaves silly looking terrain. Surgical it is not.

There were changes you could make to the config lua in the main game folder at one point. I think Mustang had a mod to do it as well but I can’t locate it now. I think it was rolled in with some other mods like haze reduction I tried it at the time using my old 6600k/1080 set up. Looked great. Halved performance. In general Syria has been hacked back and not optimised. On the highest settings building still do not fully render until you are on top of them. The detail sliders are pretty useless for the map too. Anything lower than 0.95 will see a noticeable drop in detail even at close range. I’ve only found them to be useful on the channel map which I feel they were developed in conjunction with where they work very well. EDIT I beleive its Line 392 in the DCS/DCS (OB)/Config/Graphics.lua. Currently its 1.5 but there are threads out there saying they altered it to a vaule of 6. YMMV and your PC will not thank you! I do not know if the mod I referred to altered other settings (marage springs to mind) within the discrete setting entires just above that line. Its interesting to look at the entries in green too. Although theres no telling now when comments are made, it points to code changes over the years with things no longer working/obsolete. A giant game of Jenga for the Devs! EDIT 2 - I think the autoexec.lua that some people put in their saved games folder overwrites the entries in the root graphics.lue file. There are certainly common entries in each. EDIT 3 - I wouldnt bother just doing the above - It has a bizarre effect on the graphics in 2.7 making objects dissappear close to the camera in certain view angles. The Performance hit is also nasty. Cleverer people may have better solutions but the only real solution rests with the maps Devs and ED. IMO Syria simply over reaches in terms of graphical fidelity for DCS, in its current iteration at least, and has had to be hobbled as a result. Until whatever ED have in mind for the Core improvments comes to fruition thats the top and bottom of it for now. This is my "positive speculative spin" based on nothing at all. (9/11 conspiracists perpare to awed by just how little fact this is based upon!) If I were making a map that Id put a lot of developent time and money into and I possibly had a choice of making it in a way that would see it still look great (and sell) in a few years Id probably build it with some future proofing. It means I dont have to rework models into a higher level of detail later even if Id have to compromise quite a lot initially. And, I were of a mind to offer expansions to it down the line, given the area is highly suited to such, Ill have a viable base for a much longer period to do so . Moreover its a base in the middle of all the good stuff that effectivley sticks a big "THIS IS MINE" flag in a rather interesting corner of the virtual world. And aliens assasinated JFK.....oooops!

They'll be coming for you - Pitch forks in hand. Staggering towards you like be-goggled victims of some alien head crab invasion. Trying to spot you at a distance whilst working out why you are only appearing in one eye.... Apart from performance my main reason for not going VR is that I trust neither my lad or my wife.......