DackSter94

=RvE=DackSter94 - Viggen

You know what? You are right. I'm uninstalling until this game has transsexual pilot model!

I dunno about how bad Leos are, but ground vehicles in DCS kinda always were a joke..

Igla seems to be about as effective as GAR-8 right now. It pulls laughable amount of Gs and thus, most of the times, lags behind target (first clip). Also, if it approaches target from 7 or 5 o'clock, it will always deviate at last moment for whatever reason (second clip). This should be combined with horrible damage model present for some planes right now (like f-15) it can take up to 5 or more HITS(which are unlikely to happen anyway) to kill it. Another issue, that affects all manpads ONLY in Multiplayer environment, is that their animation is broken for all clients on server when there are hostile planes overhead. On client side it looks like they having seizure while engaging targets, so missiles hit the ground in front of the launcher(but on server side it looks fine, thus there can be a missile going your way, but you will not see it on client, because it impacted on the ground near the manpad because of "broken animation"). PS: This has been an issue for a long time, not only in open beta.

=RvE=DackSter94 - m-2000c

Thank you, that worked!

No, I just did separate test, where i spanwed a-10c at 13000m+ at ISA+10 and temperature is still -47 just like at 11000m.

Interesting tho, if you set ISA+10, you can't get below -47 high up... So, if what you wrote is correct then there is still something wrong with the implementation?

No, no 11km was just random high alt i picked up..

Here is an example with numbers from the sim to make it clearer: I tested flanker at 59% fuel + full cannon ammo (infinite fuel enabled, so that mass of aircraft is always the same), level flight at 11000m full afterburner under 3 different conditions: 1) Temperature set to 25C(surface) in mission editor(ISA+10). 2) Temperature set to 15C(surface) in mission editor(ISA). 3) Temperature set to 0C(surface) in mission editor(ISA-15). Resulting temperature readout from a-10C at 11000m: 1) -47C 2) -57C 3) -57C (the issue) Resulting top speed in flanker: 1) TAS: 2666.7km/h (Mach: 2.507) 2) TAS: 2754.3km/h (Mach: 2.589) 3) Exactly same as 2) As you can see there was significant gain in top speed (almost 90km/h) from ISA+10 to ISA. But from ISA to ISA-15 there is 0 change in performance (obviously because temperature at high alt at ISA-15 = temperature at high alt at ISA).

Found out that the code works if you set your aircraft to "player". But if you set it to "client" it seems that LoGetTrueAirspeed() returns nil because you are not yet in the aircraft, and then code stops running. So my next question is how to check if the player has taken the slot already and is in pit, before trying to get TAS value?

Yes, it doesn't have to be linear, but it should be able to go lower then -57C. Reason I'm reporting this is Because you can't even get full performance from some aircraft(and may be all of them). For example viggen is supposed to be able to go like mach 1.98 with no stores at ISA -15, and at ISA it's only supposed to be able to go 1.82. Since we are locked at -57, no matter what surface temperature we set, we can't push aircraft to the limits.

It will be constant temperature, but if its 0 or -15 on the surface(and not 15 as in ISA), it will be a lower constant, no? https://www.digitaldutch.com/atmoscalc/ PS: sorry for editing a lot :)

ISA assumes that temperature at surface is always 15, no?

I found a temperature bug, while testing different planes performance: Here is a screenshot of temperature from A-10C CDU at 11000m(mission temperature is set to +15C on the ground): Here is a screenshot of temperature from A-10C CDU at 11000m(mission temperature is set to 0C on the ground): As you can see temperature at 11000 still same even though on the ground it was lowered by 15C. And it's the same for any lower temperature on the ground. This is further confirmed by planes performance. Their max speed is always equal when the temperature is stuck at -57C.

Hello, I'm just messing around with export.lua and I ran into a problem. I'm trying to export time and TAS at intervals of 0.25s into a text file. But TAS always returns nil, so text file is fails to be filled. I tried a lot of variations of the code, but can't seem to get it working... local default_output_file = nil function LuaExportStart() default_output_file = io.open(lfs.writedir().."/Logs/Custom.log", "w") end function LuaExportActivityNextEvent(t) local tNext = t local TAS = LoGetTrueAirSpeed() default_output_file:write(string.format("t = %.2f, TAS = %.2f\n", t, TAS)) tNext = tNext + 0.25 return tNext end function LuaExportStop() if default_output_file then default_output_file:close() default_output_file = nil end end

Thanks for the event and the prizes!

=RvE=DackSter94 P-51D Or somethinng noobish like Viggen

=RvE=DackSter94 UK =RvE= Viggen

Well in your other attachment i somehow have 39. In my tacview i always have 36. It's definitely not your fault, it's just retarded game. I think thise event will be more luck based then skill based.

Those score looked weird, it seemed to me that i saw plenty of bullets miss. Stuges post seems to describe an issue. + look, there is inaccuracy in your tacview, i don't have 38 bullets, i only have 36. Tacview is not accurate.

It's kinda weird, Tacview counts too much hits, while ingame counter counts too few. Sometimes you can see bullets fly "through" the target, yet you get nothing on the ingame counter.

Agreed. Not only flanker scores tho, L-39 too and I guess many others.

I think the circle below the gun target is destructible(well not visually destructible, but it's hitbox seems to disappear. That makes gun target hitbox bigger, so players who come after circle is destroyed have more advantage. Not 100% sure about that one, but that's what I found out during training session.(In multiplayer training I got much more hits then when I host for myself.

Half of new gun target is inside/beneath the circle, is that intended? Also, are we free to pick direction of atack on gun target?