Redglyph

In mission 3? The option exists, at some point you are normally told "New radio item available (F10) Inform when you are ready to move on after tanking". Tanking is not mandatory - I would never have passed this point otherwise :D

I see this problem was reported as known issue due to update 2.0.5.2576, but has actually been there before. I can confirm it's dropping from 60 FPS to 6-7 FPS with 2.0.5.1648.165, so I doubt the latest update makes things worse ;)

Thanks! You must be right about Nellis, well spotted! Just looking at the coordinates confirms it, those are from the original file and its comments, and I haven't checked all of them. I'll simply make an update of the kneeboard I suppose. Having Tonopah Test Range on RSBN 27 is really bugging me sometimes, because TTR and GRL should be the two most frequently used stations for a MiG (historically at least), yet the user has to click many, many times to switch from one to the other :/ Perhaps when I figure out how to simply pre-configure this knob in missions it will be less stressing for my mouse ;) But I was tempted to simply swap it with another, less frequently used station, or sort them all out from North to South. Wouldn't be nice to change everything, though, and since this was also in the original settings it's probably best to keep it. Another solution would be a mouse-friendly knob. Hmm. Anyway, sorry for my ramblings :D

In case it helps with the coordinates, here's a link to what I had for the MiG-21 :) https://www.digitalcombatsimulator.com/en/files/2333411/ https://forums.eagle.ru/showthread.php?p=3023098

bump

I saw they warned about other issues too. You have the option to revert to version 2.0.5.1648, read this post to see how: https://forums.eagle.ru/showthread.php?t=114030 (look for "Updating or Reverting DCS World to the latest build of a Specific Version")

... and the date in the mission is editable, so we know what to do :D

I feel no need to change the DEC - except when I fly in January ;) but that's temporary. I would probably have tried if I had taken the time to test everything while reading the manual, it's a tiny bit confusing to say it's editable, but nothing serious.

When all MiG-21s are downed by enemies and nothing is left to repair, they'll have to notice :D

Ah well, they'll surely see it at some point :)

Just one or two tiny changes I'd make in the training 03 on navigation. When setting the time to destination, it's worth mentioning that the pilot must click twice on PREP to get the correct waypoint there, otherwise it doesn't work and the extra brackets don't appear on the HUD. It's not obvious to detect why. :) It's probably best to tell that the RD isn't implemented yet, after all the training is for "beginners " who are probably not aware of the missing features. ;)

I was brushing up my navigation skills in the M-2000C with the training in DCS 1.5.6.1938.247, and noticed a couple of issues. Perhaps they are on purpose but they do look strange. :) 1) Markers If I understood correctly we have 3 markers, M91-M93, to mark the current aircraft position and then treat them as waypoints. - If I do that, then enter DEST 91, and PREP PREP to get 91 on both sides, I should normally get the bearing and distance, but I get something else, not sure what. On the HUD, the heading, distance and ground pointer seem correct. - If I use the HOTAS to select waypoint n-1, n-2, ... from 91 I get 90, 89, ... which don't exist. After a while it resets to existing waypoints. - From the "normal" waypoints, it's not possible to use this +1/-1 to get to 91, 92, 93, perhaps it's on purpose, though it'd be handy to be able to. 2) Secondary question, waypoints on radar I suppose it's on purpose that doing a PREP PREP (to copy the waypoint from DEST), then pressing VAL, does nothing? We do have to manually enter PREP <waypoint number> then press VAL in order to see those waypoints?

I couldn't find any reliable pattern about it :/ You'd probably best increase the severity, this one is honestly more than minor, and seeing I have a few bugs reported back in early November with minor priority that haven't even been looked at, this one could remain for quite a while... ;)

That's apparently still the problem in DCS 1.5.6.1938.247, the campaign has a few missions affected by this. From the manual, the declination should be editable, but I couldn't change it (other similar posts say the same). Is there a special procedure? The manual is pretty discreete regarding the PCN ;) but I suppose editing this value is in the WIP part?

Nice to hear :) That'd be nice, in the road map there is a "F-5E Air Combat Maneuvering Campaign" which seems to be the F-5 counterpart of Sabre's A-10C training campaign.

I updated to TacView 1.5.4, had to uninstall / reinstall it a few times and fiddle with it before it actually worked, but now it seems to record the flights and it does not crash anymore! Sorry then, this seems to be a problem with older version of TacView, that occurs for some reason with this strange combination. You can forget about this thread :)

Ah, OK. I tried a few things to bring more information, apparently it's perfectly reproducible when Tacview 1.5.3b is enabled (Scripts\TacviewGameGUI.lua script present) - if I remove TacView, it doesn't crash, - if I leave TacView but do the same test with other aircraft, it doesn't crash. EDIT: see below, does not crash with 1.5.4 So it's not a big problem, the obvious work-arounds are to launch from "Mission" or remove TacView. To reproduce: - launch DCS - launch an Instant mission for the M-2000C, for example "landing" (Caucasus M-2000C Landing.miz) => the mission starts - quit - "fly again" => the initial view is visible with the briefing, the paused sim environment - "fly" => crash Log: 00067.597 INFO EDCORE: # -------------- 20170225-192639 -------------- 00067.597 INFO EDCORE: S:\games\DCS_beta\bin\lua.dll 00067.597 INFO EDCORE: # C0000005 ACCESS_VIOLATION at F23E3882 00:00000000 00067.603 INFO EDCORE: 00000000 00000000 0000:00000000 00067.608 INFO EDCORE: F23E3882 0017EC90 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaS_newlstr()+1292 00067.608 INFO EDCORE: F23D1E2E 0017ECC0 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_rawget()+1E 00067.609 INFO EDCORE: E0A4B087 0017ED20 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll 00067.609 INFO EDCORE: E0A4CF8F 0017EE10 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll luaopen_tacview()+121F 00067.610 INFO EDCORE: E0A4D567 0017EE80 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll luaopen_tacview()+17F7 00067.610 INFO EDCORE: E0A4BD26 0017EEB0 0000:00000000 C:\Users\sim\Saved Games\DCS.openbeta\Mods\tech\Tacview\bin\tacview.dll 00067.610 INFO EDCORE: F23D7254 0017EEF0 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaD_growstack()+7A4 00067.610 INFO EDCORE: F23E6FB5 0017F070 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaS_newlstr()+49C5 00067.611 INFO EDCORE: F23D7541 0017F0A0 0000:00000000 S:\games\DCS_beta\bin\lua.dll luaD_growstack()+A91 00067.611 INFO EDCORE: F23D684F 0017F220 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_getinfo()+11AF 00067.611 INFO EDCORE: F23D785E 0017F260 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_yield()+9E 00067.612 INFO EDCORE: F23D2440 0017F2B0 0000:00000000 S:\games\DCS_beta\bin\lua.dll lua_pcall()+60 00067.612 INFO EDCORE: EA1A8221 0017F310 0000:00000000 S:\games\DCS_beta\bin\edCore.dll ?call_func@Config@Lua@@AEAA_NPEBDPEAV?$basic_string@D@ed@@HH@Z()+E1 00067.612 INFO EDCORE: 400219C5 0017F360 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 40021E5C 0017F410 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4001666E 0017F480 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4001D721 0017F4E0 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4000BBD4 0017F510 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.613 INFO EDCORE: 4000BB24 0017F540 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.614 INFO EDCORE: 3FCE71CF 0017FC00 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.615 INFO EDCORE: 4011FE1D 0017FC40 0000:00000000 S:\games\DCS_beta\bin\DCS.exe 00067.616 INFO EDCORE: 77A759CD 0017FC70 0000:00000000 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 00067.616 INFO EDCORE: 77BAA561 0017FCC0 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 There is a minidump, it's a little heavier than the log but I can upload it somewhere if it helps. There is no need to use the mission editor to launch any mission. Just open the mission menu, select a mission and you should see the "situation" part of the briefing. Click OK and you have the whole briefing available, from there you can launch the mission. As said above, it's possible to use that to launch the Instant missions as well. Hope it helps :) The "Instant mission" menu, however, behaves in a non-consistent way and starts the clicked mission file without showing anything. There is no advantage, why this is there is unclear to me. Still, it acts as a category selector, after a fashion, by looking first into the Missions/QuickStart directory. But the main problem reported here is that it doesn't seem to agree with both TacView and the M-2000C.

I see the same bug in DCS version 1.5.6.1938.247. Since there is no description above: - switching autopilot and altitude hold actually behaves like altitude select.

You must be onto something. :) From what I see, for example the first training missions of the F-5E and the M-2000C have the same settings, tooltips are not enforced. My general settings allow me to see tooltips and I have the "Use these settings in all missions" checked. If I run the F-5E training, I can't see tooltips, and if I run the M-2000C training I can. Now if I load the F-5E training mission in the Mission Editor and save it, later I can see the tooltips when I run it from the same training menu, so some settings must be changed. When I compare the "options" file, in the .miz newly saved mission and the original, this particular line changes (along with others): ["tips"] = false, becomes ["tips"] = true, in the options["difficulty"] part. So apparently the saved options are not entirely correct, and they don't correspond to what is shown in the Mission Editor either.

DCS version 1.5.6.1938.247 When I run more than one quick mission with the M-2000C, it crashes to desktop. Isn't that a very old bug? I thought it was solved? To be fair, I don't see the point of those, aren't they just regular missions for which you can't see the briefing summary before launching them?

I confirm the bug in DCS 1.5.6.1938.247. I first though that pressing the test button, but this isn't a work-around. It seems to shut it off, but the volume knob simply doesn't do anything.

This could be moved in the release bug thread, still a problem in DCS version 1.5.6.1938.247.

Has anyone else experienced this problem?

Right, I completely forgot about this mission. Not sure since I never got any reply, one of the groups given by the AWACS should be the C-130, it must be possible to estimate which one from the current position. EDIT: I've tried again, to make sure. Yes, just take the planned route, then listen to the AWACS to get directions (you have to filter them, there are multiple enemies). When a text appears and tells the "aircraft is at 345", you have to read "the aircraft is heading 345" instead. But as previously, the return journey is a mystery, only the initial direction is given then nothing more; perhaps there's no further indication to expect. It seems to work pretty well like that, in any case, the result is 100. :) The first mission of the BFM campaign (after the intro) is a simple flight, so you could give it a go. As long as you can do the start-up procedure, take off, land, and use the TACAN for navigation you should be fine. :) A campaign with the F-5 would be awesome, indeed! The BFM is interesting but they're basically all the same mission with different adversaries, and the pilot has to guess which method is best to defeat them but that's it. Something more varied would be great, that'll probably come at some point.

Thanks for reporting it. I wanted to check it out the other day, but the bug tracker site has been down again so I couldn't. I deleted my previous post, in which I was obviously a bit concerned about how long those bugs seem to remain (even when the patch is provided by the reporter), especially a critical one like an interceptor being often without countermeasures to defend itself. Let's just hope they'll take care about the MiG when they have more time... ;)