Cobra Who?
Which thread?
I wonder what 2.9 and the big three and oh are going to bringā¦
Oh wow, how many surprises!
Wow, 15 years⦠I always thought of myself as a newcomer to DCS, but come to think of it, Iāve been around for more than half itās life now⦠So, actually, I just suck ā¦
I remember Wags Weekly Black Shark Tutorial Videosā¦and The New Clickable Cockpitā¦Fun Times
Did I miss something? I saw maybe some new trees and new rain effects on the canopy on the F-18. Anything else?
Iām glad the newsletter showed a pic of the Chinook and mentioned the C-130J. I was getting concerned about the radio silence on the Hurcā¦
I hope we get those grass wind effects for the warbirds too.
Nah, I was just messing about with the idea that I know something more.
I really donāt.
Yes you do
Has anyone found documentation on the new framerate counter in 2.8? Trying to decipher what some of the values mean. TIA.
No documentation that I know of. As of my last flight a few days ago; they still donāt have all the values āhooked upā, unlike in the former version all/most of them did something.
Which Values.
All those '0ās tell me theyāve yet to hook those values up with the in UI (they worked before).
From memory (and I only used to pay attention to a few)ā¦
Trg - number of triangles rendered I think
SunY: I think this is the angle of the, well, sun, on the Y-axis; DCS coordinate systems is such that X = NorthSouth, Y = East/West (Z = alttude MSL). Lighting is a big deal and this may be helpful to someone. Again I could be completely wrong on this value.
FrameTime - the better indication of performance; how long the frame took to render in ms.
Main and Scene - more timings for various items
Video mem: I donāt recall that working before but it might have; I never paid much attention to it
Lua: I watched this one a lot as my system uses lua scripts - a lot of them (all āscheduledā so as not to take up too much time, and never on every frame). A percentage value here for lua stuff. FWIW, I try to never let this get above 3% - if you see this getting high you have a lot of stuff running via your export.lua script (loaded at startup).
WinWing software used to be a big killer here - would push this value way up and kill your FPS. I donāt let it load as all it does (or used to do) was control the LEDās. In VR I obviously canāt see these.
Please elaborate.
I thought the WinWing software also controlled other hardware profiles such as how certain knob axes react and specific afterburner zones for specific aircraft. Am I to understand that once I set a profile I do not need to have the software running in the background? I have to be honest, Iām not sure how the software truly works so I just run it by default.
Thanks,