Redglyph

Quick check in DCS 2.5.3.24984 - "Flaps Power Switch" is reversed - "Compass Light/Test Lights" is reversed - "Fwd Equipment Bay ECS Switch" is reversed - all ARMT 3-way switches are reversed ("Armament Mode Control", "Fuzing Control", ...) - "HUD Display Mode Switch" is reversed MPCD push interaction is only 1-way for the corner, 2-way switches (DAY/NGT, ...) Stopwatch not interacting (Stopwatch start/stop) So, yeah, basically all the bugs already reported one year ago are still there. I don't see them in the bugtracker, so I'm reviving that thread :)

DCS 2.5.3.24984 At certain angles, the image becomes much more brighter, which gives an impression of "flash" when rotating the view from outside (F2 view). Screenshots taken from the MiG-29 quick mission "Cold Start", 100% reproductible: - start the quick mission - F2 for external view - rotate around the aircraft Two screenshots in attachment to illustrate the bug, taken a couple of seconds apart from the same mission as described above. From most angles, the brightness is like the 1st screenshot, and in a small range it looks like the 2nd screenshot. I can't attach my settings because they're already in another thread, here is the link to the screenshot: https://forums.eagle.ru/attachment.php?attachmentid=199538&d=1544353868

DCS 2.5.3.24984, PersianGulf module Whenever I look at the map (F10), then go back to the cockpit (F1), the ground textures disappear. They reappear 10-20 s later, which of course makes it impossible to use this terrain for now. Screenshots taken from the MiG-29 quick mission "Cold Start". I didn't have this problem before, but the last time I tried PersianGulf was months ago (and it did crash my entire PC, had to hard reset), so there might be something very wrong with this module. I never had this issue with the Caucasus module. I see two distant relative threads, but since they are not reported and there is no answer from ED, I have to assume the devs and testers haven't seen them: https://forums.eagle.ru/showthread.php?t=222241 https://forums.eagle.ru/showthread.php?t=215803

Yes, that's the same problem that I have here, and apparently others.

Maybe, I made one but I'm not updating it anymore (devs won't integrate this patch anyway). It's such a pain to see the A-10C in such a chaotic state, and having to guess which way to click each cockpit control.

Do they plan to finally fix the cockpit switches as well?

Thanks for the quick reply, Bunyap! The 1 NM distance was completely overlooked on my part, sorry for that! Anyway, even if that was not obvious in my first post, I did enjoy the close formation exercise :D I wasn't sure whether to report 1) and 5) (and potentially 4) here or in their respective bug forums, the latter is probably the best to do. The offset in 4) seemed quite constant in several long legs, but if the waypoints are different I'm reassured it's not a declination mixup in the AI or mission editor (as if those were not already confusing enough IRL navigation...) Any cure for 3) would be much appreciated, fingers crossed!

That's pretty good news, comes just in time for the new cockpit hopefully! Now we only need the damage model upgrade :thumbup: But the Bf-109 is also a great airplane, with a bit of luck we'll see if Wags has something in reserve for it.

I saw that. Perhaps anything that turns and looks similar to a propeller stirs something deep in our subconscious? ;) Anyway, I don't need to see it, but it was not clear at all in Heatblur's communication.

DCS 2.5.3.24436 (OB) I observed the following issues. 1) Time discrepancies See 1st screenshot (maybe it's a problem with the Viggen module and not the mission). The line-up card specifies checking at 15:00 and take-off at 15:06, the kneeboard shows the engine start-up at 14:55 and take-off at 15:00. But the clock shows that it's already 15:00 when the mission begins, so there's a little confusion between the scripted kneeboard and the mission starting time? 2) Speed inconsistency The line-up card specifies .6 M during the flight. The leader's speed is all over the place, after B1 it's about .7 M, after B2 it's well over .8 M (the altitude is also erratic), after B5 it's a very slow .5 M. A bit before B1, on the way back, he's suddenly slowing down from .6 to .4. Then a short event of afterburner and immediately after he's deploying the airbrakes. There is no warning from the leader when he's about to slow down or accelerate. I'm not sure which part is due to the scripting and which part is due to the AI, but it's unrealistic. 3) Voice Wag's transformed voice is simply not understandable, and with the manoeuvring it's not possible to read the text. I suppose the idea was to mimick the VHF distortion but (1) it doesn't sound similar, (2) the two planes are next to each other, and (3) perhaps it could be more user-friendly, many people are not used to listening to distorted radio reception. 4) Bearings It seems we were not following the waypoints (see 2nd screenshot for an example on the way back). I was wondering if there was some problems with true North and magnetic North. I'm not able to see the declination settings of the Viggen, and changing them doesn't seem to have any effect. If the leader was not taking the declination into account and following magnetic N instead of true N, that could explain the problem, or almost, the angle seems a little more than 12°. Also, there is little or no warning from the leader when he's about to turn. 5) Crash At the end of the mission, DCS crashed, that's the first time I get this with the Viggen though the other missions I flew were simpler. I can post the dump if that's useful but I doubt it. Just let me know. I have seen that it was possible to skip missions so it's not blocking (I know how to edit the logbook anyway). # -------------- 20181203-203257 -------------- S:\games\DCS_beta\bin\edCore.dll # C0000005 ACCESS_VIOLATION at E50DF6D7 00:00000000 00000000 00000000 0000:00000000 E50DF6D7 0029F050 0000:00000000 S:\games\DCS_beta\bin\edCore.dll ?ResetLinks@LinkHost@@QEAAXXZ()+17 EA736462 0029F090 0000:00000000 S:\games\DCS_beta\bin\edObjects.dll ??1viMovingObject@@UEAA@XZ()+42 E4AE2AD2 0029F0C0 0000:00000000 S:\games\DCS_beta\bin\WorldGeneral.dll ??1woLABase@@UEAA@XZ()+12 4000B9C4 0029F0F0 0000:00000000 S:\games\DCS_beta\bin\DCS.exe

- Canopy open/close is moving the wrong way with left/right mouse clicks - Countermeasure Release switch is moving the wrong way Please check the standard linked here, the purpose is that all aircraft modules in DCS behave the same way. The MiG-21bis already have this problem of incorrect behaviour...

OK, thanks! I've tried a few things, it appears we can't map this action to a controller and that it must be mapped to the keyboard.

Is the RAT model visible now? I have tried to set a main generator failure and/or to deploy manually the backup generator but I don't see any external RAT. I also find the user manual a bit confusing: So it is only extended when the nose wheel is "depressed", so on the ground? Or do we have to extend the landing gear in the air, between 300 and 700 km/h? I'm afraid none of this is clear to me, even though I'm familiar with such devices, to me they're only useful in the air and deploy automatically on generator failure, or have a switch to manually extend them (like in most airliners), and it's generally not related to the landing gear whatsoever. In any case, I don't see it when the landing gear is extended either. :confused: Could anyone clarify? EDIT Since then I saw a video showing the RAT was visible during ground operations, and a similar comment in the announcement thread. Still it's not visible (neither on ground or on generator failure) so I assume there was a regression or they finally decided not to release it in August.

Heh. With the same joystick that normally controls the airplane pitch & roll? Which button/key did you map the "Rb05 switch input with flight stick (hold)" to?

:O I did not! That seems like a neat detail, thanks for telling me! However, it's not the case here. I found out I had those shaking problems with some of the missions when they start on the ground with the engine already powered, like for example, the take-off training mission. Moving the Viggen a little bit farther calms the shaking down, so it must be an initial placement problem.

With the additional VR argument to support this improvement, it should definitely be considered :) Perhaps you'll stand a better chance by posting also in the DCS wishlist (although I'm not sure, there must be tons of suggestions there...), or by asking Derelor how to proceed with this, he seems to know the subject pretty well. This probably requires a modification of the default_button function (or similar name) for each aircraft, since the cockpit interaction logic seems duplicated for each module. I only know a tiny bit on the A-10C and the MiG-21 so I may be wrong. In the mean time, I wouldn't be surprised if this could easily be done as a mod in the Lua scripts (typically cockpit/clickabledata.lua). And since those "in the mean time"'s can last for a very long time, the little problem is maintaining the mod with every update, I have done that for a while with the A-10C and the Fishbed then I finally gave up. An argument I heard several times was "yeah, but if I integrate this, what about the existing missions, will that break them?", which of course is a false argument (at worst some mission may explicitly say "left click this or that" but it's very rare). The other resistance probably came from changing what the existing base was accustomed to, but then again, if that makes more sense they should like the change. Anyway, I was talking about the general behaviour of all modules. Perhaps it's the wrong approach, and by trying with the Harrier and asking to Razbam if they'd take the patch... who knows. It's still very much in development and they might be more willing to improve things. If that proves to be better as a proof of concept (big words for such a small modification!), it could be easier to convince that the other modules should also be changed.

Similarly, the last training mission on CCIP bombing is behaving yet differently, by checking the settings and continuing if/when they're OK. This is IMHO the best way to do, but this training mission does it too quickly and the dialogue is interrupted many times. => there should be a minimum delay to make sure the dialogue is said, especially when the settings are already preset correctly. This was with DCS 2.5.3.24436

DCS 2.5.3.24436 I'm trying to steer the RB-05 missile by holding the input mapped to "Rb05 switch input with flight stick (hold)" and the flight stick, but that doesn't seem to work. Beside, the input is still used for the aircraft so it's pitching up and down as I move the stick. I'm using the RB-05A training mission for the test.

There was this old post from Wags in the Epsom campaign forum, but there is nothing on their roadmap yet. If they improved the damage model - I've read they intended to start on the Spitfire as a testbed, and if such a campaign saw the day, it would be awesome!

I hate to contradict you though, my cockpit was closed and I had my fancy scarf around the neck...

You'll be glad to hear there is a standard! \o/ That's the image in attachment, which Derelor posted in answer to a similar report for the A-10C (which is beyond any hope, despite the patch I tried to provide and that I don't tire to remind them). Razbam is usually one of the few developers, beside ED/Belsimtek, who follow this standard... though when it's WIP some knobs and buttons are sometimes acting up (or down) ;) +1 on forcing right/left click for the 2-way switches, that would be more natural and much safer! I would go a little further and even say that it would be good to have a key mapping standard for the common commands like starting/stopping the left/right engine, resetting the caution light, opening/closing the canopy, switching the lights, and so on. But that's probably more difficult because there should have been a set of common constants in the API for those and I don't think it's the case.

Hello! DCS 2.5.3.24436, trying the last training that prepares to the RF campaign. - The schedule is impossible to keep, the user is supposed to take off at 16h09 and that's not enough time even by starting all the tasks in advance, before the instructor mentions them. I know now that the clock should be disregarded but that wasn't obvious then. - I have no ATIS on the way back, I tried Green 2 or Red 8. I guessed that since I had Hotel on departure, this may have switched to India and gave that information to the tower but that was wrong ;) No apparent impact on the outcome though. Other than that, excellent work as always! :)

Damn, you're right, that was it! :D

I see this thread hasn't been seen yet by the dev/tester team. I confirm that the parking brake is only a cosmetic artefact in version 2.5.3.24436. Moreover, the plane is always shaking strangely, even on idle, this is really annoying. I'm not entirely sure it's linked to the brakes as it also happens when the brakes (or parking brakes) are not applied.

It's not the expression which shocks me (especially with the action of scooping, as stated by others), but the "so that out ELINT guys" part ;)