discwalker

someting is changed in skin handling in 2.5.3.23954 The swifts is a vanilla distributed skin, several missing texture skins in the whole aircraft, especially the green two digit place in vertical stabilizers. (but nozzles also missing texture noised) Gromov Flight Research Institute skinS (3) was perfect in previous DCS build also https://www.digitalcombatsimulator.com/en/files/3302348/ EDIT: this is updated to latest openBeta standard, DCS restart required third: https://www.digitalcombatsimulator.com/en/files/3246434/

poll in this topic: https://forums.eagle.ru/showthread.php?t=223778

Some of my missions are Read-Only for saving the state as is, from accidental overwriting. I started read onlys since this at first occured with me: https://forums.eagle.ru/showthread.php?t=211723&highlight=save+failure 1: because an important milestone of a big mission 2: because is a rare bug reproduction state (that was a mission to worth to conserve: https://forums.eagle.ru/showpost.php?p=3632818&postcount=12 -->that precise bug fixed) 3: because of a track file that hard to replay again in the same way (I simpy set RO flag in my file manager.) 2018-12-08 13:12:04.141 INFO TERRAIN: lSystem::CleanScenes() 2018-12-08 13:12:04.421 INFO EDCORE: (dDispatcher)enterToState_:3 2018-12-08 13:12:08.927 ERROR VFS: VFS_open_write: CreateFile(C:\Users\pitwalker\Saved Games\DCS.openbeta\Missions\f14_all.miz): Unknown error 2018-12-08 13:12:08.927 ERROR Lua::Config: Call error onShowMainInterface:[string "./MissionEditor/modules/me_mission.lua"]:6258: can't open "C:\Users\pitwalker\Saved Games\DCS.openbeta\Missions\f14_all.miz" for 'wb' stack traceback: [C]: ? [C]: in function 'assert' [string "./MissionEditor/modules/me_mission.lua"]:6258: in function 'copyMission' [string "./MissionEditor/MissionEditor.lua"]:614: in function 'openReturnScreen' [string "./MissionEditor/MissionEditor.lua"]:687: in function <[string "./MissionEditor/MissionEditor.lua"]:678>.

If someone can reach that speed please post the track file of it. For me at approx 2400 kph TS (2.2Mach) the two vertical stabilizer is tear off. update: with rudders restricted to zero deflection, 2600 kph TS is the max speed for me, lethal. Once 2500 kph TS was enough to kill one engine completely, emergency landing was success.

Please fix the real cause ED fixed what not caused game crash: the possibility of multiple players. dcs.log-20181107-154854_hundredClient+onePlayer.zip

test with the latest DCS with 2.5.3.23788 game crash at second explosion (7th seconds)

2.5.3.23788 still unable to handle well Read-only missions

Hello. This is an open bug report! Opening post updated with current track+dmp+log. edit: fixed in late 2018 edit: came back in 2019

Please acknowledge and fix this 3 months old reproduceable game crash. (Opening post is updated with fresh pack of crash log.)

=) Easy avionic mode exists, and if will exist, this is not a big wish

poll: Add NAV feature to MiG-29 HDD as a mission designer option I started a poll to optionally get back the "missing unreal feature" https://forums.eagle.ru/showthread.php?t=223778

I suspect many of us used a lot the MiG-29 navigation function on the head dow display since LOMAC. Waypoints and Runways was nicely visualized. ED almost 2 years ago removed waypoint knowing ability on MiG-29, without a notice, what a deprivation! (https://forums.eagle.ru/showthread.php?t=160270 https://forums.eagle.ru/showthread.php?t=171212 https://forums.eagle.ru/showthread.php?t=158228) We have only a fresh promise to add Su-25T kind of functionality once: https://forums.eagle.ru/showpost.php?p=3652885&postcount=13 Wags:"It will be added back to the HUD in an update." But the simple moving map was better. Visual alternate airport selection capability is handy. Navigating with that in bad weather is priceless, especially think to approach. The feature is thankfully working in Flankers (Su-27, Su-33, J-11A) (in key "1" NAV mode, HUD repeater mode off state)

+1 for extending game master functionality :set the AC group tasks :alterting triggers real time :spawn bandits for a group :spawn tanker for a group :change airbase neutrality :edit warehouse stock :set failures real time for a plane These and similar addons can save a coop mission testing run.

Inventorys are so incomplete. Thanks to adding SA2 to HUNGARIAN ground units. Please add SA6, SA3, Shilka and Humvee to the inventory of Hungary! MiG-29A and Mi-8 IRL linked to Hungary, now unselectables. We use accurate HUNAF skins for those, and fly as Russians. Slovakia also missing MiG-29A... An easier step would be to add all units to all countries, not worrying about skins. Communities solve skin issues locally, not needed the DCS vanilla install to include all skins, the storage waste is not needed. (MiG-21 skins weight 5,86GB) Current assignment is a great obstruction to mission editors. Unlocking officially unskinned units selection can be done via one small checkbox. I not promote a ton of different skins to a single country, like ed did with the F/A-18C, 15 for Spain - never seen any, 20 for US If an USAF aggressors asset has empty list of skins it must be populated with all of skins available.

I advice simply force renew IP before start your DCS multiplayer session. I don't want to believe your ISP lease the IP adress for less than a day when you force IP renew via your router's diagnostic tool.

Really? Built in VOIP is maybe a waste of programmers hours. The strongest negativum: DCS is "sometimes" crash during a multiplayer session. And that case comm is broken. Sometimes with host crash. With TS we have the opportunity to figure out of the cause of the crash. We report for teammates disconnections during connetcions, so that client can be shut down with force and can retry. The team most time must be connected before host start and slot allocation: At rendezvous, briefing... Remember the option of passwording a server, we need a way to sharing the password. Voice activated clients may will eat bandwith, not just disturbing everyone. The using of voice comm during MP is solved for me. If I want and I can talk in that language. DCS community is dispersed by native languages also. Intercom is working on Cribob's tool? AFAIK SRS (DCS Complex Radio) not eliminate a need of another VOIP tool. Two push to talk button is enough. DCS is a sandbox simulator, with so many possibilities. Every new feature bring new bugs to it. And I see no hope with this ED coding team size to fixing just reproduceable bugs.

the bug extendedly alive in 2.5.3.23225 No mods involved to create this messy mission: Blue side 32 country -> 27 usable (unusable: 69=Italian soc. rep., 36=Japan, 22=Switzerland, 66=Third Reich, 7=USAF Aggressors) Red side 9 country -> 6 usable (unusable: 27=China, 17=Insugents, 68=USSR) A more intelligent mission resave could easily correct this. Or a more intelligent first unit creator procedure! coalition declaration (without neutrals): ["coalitions"] = { ["blue"] = { [1] = 21, [2] = 23, [3] = 11, [4] = 25, [5] = 8, [6] = 28, [7] = 26, [8] = 13, [9] = 30, [10] = 5, [11] = 16, [12] = 6, [13] = 31, [14] = 32, [15] = 15, [16] = 69, [17] = 20, [18] = 36, [19] = 12, [20] = 40, [21] = 41, [22] = 44, [23] = 9, [24] = 46, [25] = 22, [26] = 10, [27] = 66, [28] = 3, [29] = 4, [30] = 1, [31] = 2, [[b]32[/b]] = 7, }, -- end of ["blue"] ["red"] = { [1] = 18, [2] = 24, [3] = 27, [4] = 17, [5] = 0, [6] = 43, [7] = 19, [8] = 47, [[b]9[/b]] = 68, }, -- end of ["red"] missing countries from unit declaration (the order is unimportant): ["coalition"] = { ["blue"] = { ["bullseye"] = { ["y"] = 625697.98691655, ["x"] = -306184.75268309, }, -- end of ["bullseye"] ["nav_points"] = { }, -- end of ["nav_points"] ["name"] = "blue", ["country"] = { [1] = { ["id"] = 23, ["name"] = "Austria", }, -- end of [1] [2] = { ["id"] = 25, ["name"] = "Bulgaria", }, -- end of [2] [3] = { ["id"] = 30, ["name"] = "Finland", }, -- end of [3] [4] = { ["id"] = 31, ["name"] = "Greece", }, -- end of [4] [5] = { ["id"] = 32, ["name"] = "Hungary", }, -- end of [5] [6] = { ["id"] = 41, ["name"] = "Romania", }, -- end of [6] [7] = { ["id"] = 44, ["name"] = "Slovakia", }, -- end of [7] [8] = { ["id"] = 1, ["name"] = "Ukraine", }, -- end of [8] [9] = { ["id"] = 11, ["name"] = "Belgium", }, -- end of [9] [10] = { ["id"] = 4, ["name"] = "UK", }, -- end of [10] [11] = { ["id"] = 6, ["name"] = "Germany", }, -- end of [11] [12] = { ["id"] = 16, ["name"] = "Georgia", }, -- end of [12] [13] = { ["id"] = 13, ["name"] = "Denmark", }, -- end of [13] [14] = { ["id"] = 15, ["name"] = "Israel", }, -- end of [14] [15] = { ["id"] = 9, ["name"] = "Spain", }, -- end of [15] [16] = { ["id"] = 8, ["name"] = "Canada", }, -- end of [16] [17] = { ["id"] = 12, ["name"] = "Norway", }, -- end of [17] [18] = { ["id"] = 2, ["name"] = "USA", }, -- end of [18] [19] = { ["id"] = 3, ["name"] = "Turkey", }, -- end of [19] [20] = { ["id"] = 5, ["name"] = "France", }, -- end of [20] [21] = { ["id"] = 10, ["name"] = "The Netherlands", }, -- end of [21] [22] = { ["id"] = 20, ["name"] = "Italy", }, -- end of [22] [23] = { ["id"] = 21, ["name"] = "Australia", }, -- end of [23] [24] = { ["id"] = 40, ["name"] = "Poland", }, -- end of [24] [25] = { ["id"] = 26, ["name"] = "Czech Republic", }, -- end of [25] [26] = { ["id"] = 28, ["name"] = "Croatia", }, -- end of [26] [[b]27[/b]] = { ["id"] = 46, ["name"] = "Sweden", }, -- end of [27] }, -- end of ["country"] }, -- end of ["blue"] ["red"] = { ["bullseye"] = { ["y"] = 476584.79871728, ["x"] = -170650.02037614, }, -- end of ["bullseye"] ["nav_points"] = { }, -- end of ["nav_points"] ["name"] = "red", ["country"] = { [1] = { ["id"] = 0, ["name"] = "Russia", }, -- end of [1] [2] = { ["id"] = 18, ["name"] = "Abkhazia", }, -- end of [2] [3] = { ["id"] = 19, ["name"] = "South Ossetia", }, -- end of [3] [4] = { ["id"] = 24, ["name"] = "Belarus", }, -- end of [4] [5] = { ["id"] = 43, ["name"] = "Serbia", }, -- end of [5] [[b]6[/b]] = { ["id"] = 47, ["name"] = "Syria", }, -- end of [6] }, -- end of ["country"] }, -- end of ["red"] }, -- end of ["coalition"] BLUE_vs_RED_v1.5_empty.miz

key/joy button command: Launch Bar Control Switch - EXTEND/RETRACT / left vertical panel I have no issues with that from beginning

I appreciate the great work that in the EA F/A-18C lot 20. I own the Hornet, and I like flying with it. I don't mind new features are coming slowly.

LOL This chart and video is unusable without the vital information of BRC. Information is missing, David OC! I not see any improvement in ATC since 2015. ATC is like in LOMAC times, but not match to actual design criterias. Please try a carrier landing at night on a BuddySpike Blue Flag server, where F10 map shows only you, and no ouside views are available. Can we get the BRC as a hotfix?! Or should we eject with the F/A-18C and Su-33 when all fuel is consumed?

Track Track about runway misleading ATC messages from Stennis and Kuznetsov. And please declare QFE in hPa for Su-33. 2,5,3,23225_misleaderShipATCs.trk

@Rescue, In my attached image above: "Enfield 1-1, Ship, fly heading 40 for 11, QFE 29.93, runway 09, to pattern altitude" The ATC of the SHIP never speaking about BRC. While the BRC is 270 degrees in that simulation. For knowing the BRC you need assistance from F9 or F10 view or from buddies with F9 or F10 view.

misleader ATC about heading of the ship The ATC runway declaration is only accidentally matching with reality. The bug is reported february, since then ED in deep silence: https://forums.eagle.ru/showthread.php?t=201558&highlight=heading (in RL=IRL=in real life)

Yeah, nozzles touch runway easily track: full internal full gun centerline tank full AA load full pitch trim forward! full stick forward state!! without flaps!!! +full AB location: PG/Sharjah time: 8h23m Rctrl+ENTER view active in cockpit I also need official explanation to this. 2,5,3,23225_m29_pfm_pg_blowTyresBug0.trk

demo Take control stationary AIs on ground. Only the F/A-18C explodes to me from my inventory. (The take control of moving AI is a different thing, only reliable in air with mechanical devices altering mostly.) If you not own a module you will not see that cockpit in the following track file. (Recorded in Maykop.) more_alive_afb-uncontrolled_teaser_with_unfueled_controlled_AIs.trk