ezfox

Can we get this also for F-5E, please ?

Doesnt limiting the framerate using the MaxFPS option in graphics.cfg fix this ?

+1 Come on ED, how hard can it be to fix this ? :/

Hi, i think the cockpipt mirror in the L-39 behaves wrong. When i move my head closer to the mirror, the fov increases and vice versa. I would expect the opposite behaviour ? See attached screenshots.

Not sure if this should be here in MiG-15 bug forum or in VR bugs, but i think its MiG-15 model related. 1/ The nose cone light (offset) is wrong and somehow coupled to head movement in VR. It also feels like the left border of the nose light cone is coming right off my left eye when sitting in cockpit. 2/ In night-flight the cockpit is illuminated magically above exactly 1700m flying height. 3/ In night-flight when flying inverted, the environment is slightly illuminated/brighter then in normal flight attitude. While rotating the plane the "light cone" comes in sight counterrotating (so if you turn your MiG on the back clockwise, the lightsource that illuminates the environment beneath is coming in sight rotating counter-clockwise). See attached sreenshots. Please let me know if you need more screens or infos. Thx ! Version is latest 1.5 Beta -> 1.5.4.54316 VR is Oculus Rift CV1 Greetz, Enrico

There is enough work to do for them before final release: https://leatherneck-sim.mantishub.io/view_all_bug_page.php?refresh=true The chaff and flares bug renders the module useless for me at the moment. But i´m happy flying the MiG-15 instead until this gets fixed :)

On Facebook they stated after the Kickstarter cancellation, that the normal Seats will be available in june.

After several years the Flight Seat from Speedmaster is available again through a Kickstarter campaign: Lets hope they reach their fundraising goal ! :pilotfly:

Found another occurence from a couple of days ago - so this is a repeating error. Logs.zip

00500.393 INFO EDCORE: # -------------- 20151011-214419 -------------- 00500.393 INFO EDCORE: 00500.393 INFO EDCORE: # C0000005 ACCESS_VIOLATION at EC0F6E3F 00:00000000 00500.395 INFO EDCORE: 00000000 00000000 0000:00000000 00500.398 INFO EDCORE: EC0F6E3F 0015EC50 0000:00000000 ?convertVoltage@Adapter@Elec@EagleFM@@UEAANN@Z()+9CF 00500.398 INFO EDCORE: EC101713 0015EC80 0000:00000000 ?clear@Relay@Elec@EagleFM@@UEAAXXZ()+33 00500.398 INFO EDCORE: EC101685 0015ECC0 0000:00000000 ??1Relay@Elec@EagleFM@@UEAA@XZ()+25 00500.398 INFO EDCORE: E9A75D53 0015ED00 0000:00000000 00500.399 INFO EDCORE: E9AD81BB 0015ED40 0000:00000000 00500.399 INFO EDCORE: E9AD67B7 0015ED70 0000:00000000 00500.399 INFO EDCORE: 3F973266 0015EDB0 0000:00000000 00500.400 INFO EDCORE: 3F9BEC12 0015EE10 0000:00000000 00500.400 INFO EDCORE: 3F9BEA64 0015EE40 0000:00000000 00500.400 INFO EDCORE: 3FAFA987 0015EED0 0000:00000000 00500.400 INFO EDCORE: 3FAEE387 0015EF80 0000:00000000 00500.401 INFO EDCORE: 3FAE66B8 0015F240 0000:00000000 00500.402 INFO EDCORE: EAC95A2F 0015F270 0000:00000000 ?exitFromState_@FSM@Common@@AEAAXXZ()+4F 00500.402 INFO EDCORE: EAC958BF 0015F2B0 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+16F 00500.402 INFO EDCORE: 3FAEB701 0015F310 0000:00000000 00500.402 INFO EDCORE: 3FB02014 0015F340 0000:00000000 00500.402 INFO EDCORE: 3FB01F64 0015F370 0000:00000000 00500.402 INFO EDCORE: 3FBAB60C 0015FA20 0000:00000000 00500.403 INFO EDCORE: 3FBAD4B5 0015FA60 0000:00000000 00500.405 INFO EDCORE: 76EF5A4D 0015FA90 0000:00000000 BaseThreadInitThunk()+D 00500.406 INFO EDCORE: 7712B831 0015FAE0 0000:00000000 RtlUserThreadStart()+21 00500.506 INFO EDCORE: Minidump created. convertVoltage_CTD.zip convertVoltage_CTD_mission_and_track.zip

Yes, but there is still a bug. For info: "[" and "]" are mapped on my german keyboard by DCS to the "Ü" and "+" keys. When i check the (default) config for "kneeboard - next page", the key-field appears to be empty. Nevertheless, the default key is working ! As soon as i try to remap my "+" key to this function, the configuration dialogue warns me, that the key is already used for "next page": When i apply this change, a Keyboard.diff.lua-file is created and the key gets non-functional: local diff = { ["keyDiffs"] = { ["d3001pnilunilcd100vd1vpnilvunil"] = { ["name"] = "Kniebrett - nächste Seite", ["removed"] = { [1] = { ["key"] = "]", }, }, }, ["d3005pnilunilcd100vd1vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "]", }, }, ["name"] = "Kniebrett - nächste Seite", }, }, } return diff Greetz, ezfox

After i deleted the file "C:\Users\...\Saved Games\DCS.openbeta\Config\Input\L-39C\keyboard\Keyboard.diif.lua" the issue is fixed for me too. :thumbup: That means the bug was with the default L-39 keyboard lua file. It got copied over to the diff.lua and the DCS updater was not able to patch this file.

Check the activities on the Wikipedia article: https://en.wikipedia.org/wiki/Aero_L-39_Albatros#Operational_history I think the best match would be military actions against insurgents and small militant groups, border control and similar small scale operations. This would mean enemy manpads, APCs, trucks, small bases (FARPS) and such.

The kneeboard is still bugged - no change. The RV-5M Radio Altimeter was fixed. :thumbup:

This bug was already reported: http://forums.eagle.ru/showthread.php?t=148625 It doesnt seem to be mem leak. There are thoughts that it doesnt happen as long as no other vehicles and/or planes are present in the mission. Greetz, ezfox