Redglyph

This is still present in 2.5.6.45317, not sure it's the same bug since this report is already 1-year old, is it a regression or still the same? EDIT: less than 1 year, I forgot the dates were showing the month first here. Still a long time ago though.

Thanks a lot for your efforts!

The bug is still there. I also see it with the Yak-52 training mission (take-off). When the Yak-52 is aligned on the runway, use F2 for external view, and rotate around the aircraft, there are angles that cause this black flashing screen. Any chance we get some feedback? It's been 1 year and a half...

Later? It's been 4 years, they don't seem in a hurry to fix it ;) I'd be surprised if they even saw the bug report though. If that's annoying someone, I'd suggest to create a new one in a fresh thread (or even better, to post it in the Russian part of the forums).

Thanks! Sorry, I wasn't talking about this bug, you've been very active here :)

I don't have that, and I don't want to spend too much time setting it up, unless there's a specific request (from past experience, I know patches and such reports are often ignored by ED). I split it into several volumes to fool this forum limitation, but then I had to rename the files because ".z01" and so on are not valid extensions... So to unzip, you have to rename .z01.zip to .z01, etc. Hope it helps! I would be easier to remove those limitations ;) F86_nosound.bug.z01.zip F86_nosound.bug.z02.zip F86_nosound.bug.z03.zip F86_nosound.bug.zip

Apparently the track I uploaded was ultimately rejected by the forum server: Even compressed, it's more than 5 MB, nothing I can do on my end.

I got this problem today, trying the 2nd mission of 'Hunters over the Yalu'. DCS/2.5.5.41962 (x86_64; Windows NT 6.1.7601) Here is the sequence of operations: - start-up, take-off => no problem - external view on closest airplane to check wingmen => no problem - back to internal view => no problem - fly-by view => no problem - back to internal view => NO SOUND - external view => no problem - fly-by view => no problem - back to internal view => NO SOUND The log is uploaded in attachment. The track is uploaded too, bear with me because I haven't flown this in a while, so I'm fumbling about with some of the controls ;) But the good news is... I replayed the track and the sound disappeared at the same place! It's about 15 minutes after the start, use accelerated time and look for those actions: - heading ~047 and climbing to 8000 ft - switching pos lights off and checking with external view - looking at vehicle near RWY, then behind at wingmen - fly-by and back in the cockpit => COCKPIT SOUND STOPS Note that there is nothing obvious in the log when this happens (should be in the big empty gap below), perhaps there are clues elsewhere:

Haha, yes, it's been a long time! As far as I can see in DCS 2.5.5.41962, there is no change. If you follow the link you should see a patch and a report of all the wrong switches and knobs (quite a lot), it's mostly the 3-way switches that need fixing. I think the worst is not a deliberate choice of reversing all the logic, because it's arbitrary to begin with, but inconsistency like in the A-10C. I never know what click does what because there is no common logic behind, sometimes to flip a switch up you need to right click, sometimes you need to left click. Derelor reported this several times to the devs (together with my patch, so it's really zero work for them), but it was just ignored.

A2A did a great job (as always), but I think they simplified the taxi part by using the same system as, for ex, a Mustang, by simply using the rudder pedals. Unless I missed an option to have the real behaviour. That isn't bad, though, I hate this part in DCS ;) I'm not sure why you don't enjoy it, maybe the lack of feedback (FFB, accelerations) makes it less enjoyable but also more difficult to fly than in reality? Do you have the same feeling with the Bf109?

When a user edits the description in the User Files area, the HTML is escaped when the table is updated, so the text is mostly unreadable. Example: https://www.digitalcombatsimulator.com/en/files/3303202/ It happened when editing a previous entry, I haven't tried to create a new one.

Thanks for the tip. But what DCS version are you using? I've updated the description with an additional warning but without giving any detail, I assume it's 2.5.5 something. Unfortunately the DCS user file website is now bugged and it injects the escaped HTML tags so it's mostly unreadable anyway :rolleyes: I have no idea about a possible fix, I could not get any feedback from them, they even ignored my PM with a direct link to the patch, so I'm ignoring them in return as well as their possible new products.

OK, thanks! :)

DCS 2.5.5.41371 I have noticed that the AI was flying "on rails". It's very obvious when coming back for landing, during the approach, and probably also anytime when flying in formation. The AI is approaching at constant speed to rejoin formation, and the speed changes instantly to match the leader's. The climb or descent rate changes instantly from 0 to another value like 1000 ft/min. It's completely unrealistic, which begs the question of how reliable the fights again this AI may be. The difference with other planes, for instance the WWII, is obvious and very disruptive for the campaigns. I'm not sure it's worth uploading a track, although it could be done if necessary. Is that a known issue, and if so, is there any plan to bring a decent AI to this jet?

Hey Reflected, I have given a try at the first mission, it's pretty good so far! I like the documentation and the background that you took the pain to build around the campaign. Small detail: I have noticed that the "CONFIDENTIAL" document specifies a QNH = 29.57 (I assume it's inHg), both in the PDF and the briefing panel picture. But the mission panel indicates that the QNH is actually 29.92 inHg in that region. I think you meant QFE = 29.57 inHg - that, or the mission editor didn't save the assigned pressure in the mission file. And here's a question, should we only use the F10 commands to give orders, or can we alternatively use the usual flight commands? UPDATE: posted this problem report, has anyone else noticed the same behaviour with AI flight model? I suppose it's a well-known issue.

Part of the delight is also certainly due to believable engine sounds, which was not the case before. It was a huge improvement in the overall feeling when flying one of the most beautiful airplane. :thumbup: Let's hope the difference will also be perceived and recognized by other module makers, and that some effort will be put into increasing the sound quality of their products ;) ++ I could do without that too, when the user viewpoint changes and the fake reflections remain at the same place, they are inevitably seen as a stain on the canopy, which makes the cockpit environment feel very cheap.

DCS 2.5.5.41371 With the mirror on, I get a lot of black images flickering on the whole screen, in circumstances that are hard to pinpoint but that seem related to the direction the plane (or the mirror...) is facing. I get this in a very reproducible way when I use the quick mission cold start at Vaziani, soon after taking off on RWY 13 (the sun being slightly to the left). If I do a 360, it restarts at about the same angle. I could do an active pause when it happened and if I switch the mirror off, it disappears. If I switch the mirror back on, the bug reappears. The nVidia drivers are version 397.93, this is a 980 Ti so I doubt there is much change in the drivers anyway. The quick mission uses a P-51D-25.

This module is a little bit like the WWII Assets Pack, it includes a lot of improvements on the "free" world that will hopefully entice more users to buy related modules like a Hornet, or to come to the DCS world. ED will have to find the right price and the right balance between the free and the paid version, I think there were already lenghty debates about this and it's worthless for us to throw random price tags without any statistics to back them up. But just paying because "it helps DCS" seems a bad argument, since it also gives them a lot of extra work when there is already so much to finish on all levels. I'll pay to get something I value in return, as most sensible people do (and part of that value is making sure DCS lives on, for sure). They'll fix the price accordingly to our demand so that they can get a value of their work, and that's how it works. So my concern is not so much that there is a paying version, but rather that it is yet another path that opens in the roadmap while there are so many opened items that users have already paid and are still waiting to be completed. It's not reassuring, even if people at ED most probably know what they're doing. My overall impression of DCS, compared to other products, is of a deep and complex, yet very experimental simulator, in which nothing is really finished or entirely stable. It's fine for a while, but that impression never subsided in 5 years (especially when it's impossible for users to get any feedback on very annoying bugs that have been there for years too). And this must certainly be coming from being spread thin.

There's not much data for the devs to investigate in your report ;)

That's what I supposed :) Here we see the runway but sometimes it's more visible in the air, especially since the gear handle and everything around is pitch black. Then there's the poor pilot and the draught ;)

DCS 2.5.5.41371 I searched but haven't found any report of this in the current section.

Any feedback on this? I also find it very quiet, is that realistic or a sound issue?

Hi and thanks for the great work on those modules (and the new ones)! You mentioned the tracker, on which I saw one missing item since you previously said it was on the list. I think it's worth adding it, because from my experience those are never fixed once the module is out of beta (e.g. A-10C, MiG-21, TF-51 ...). Bug description: https://forums.eagle.ru/showthread.php?t=196690 - from 2 years ago, accidentally moved to the resolved bugs Since the fix is included in this link, that should be quite straightforward and painless.

+1, the oddest controls may be mapped on those axes, imaginary rudder pedal buttons and so on, first thing I do on a new module is to clear everything ... except maybe for the F-16C, I saw that one of the AP controls was mapped to a 3-way switch on my throttle controller, that must explain that part. The switches are supposed to be read at the start of the mission, but it's never been the case (a bug I reported a few years ago but which was obviously ignored). I suppose that in some cases those are read, and must have set the autopilot to altitude hold. So it's worth checking the controllers before starting a mission, sometimes they are read on startup, but not always, which makes that kind of behaviour not always reproducible.

Fixed Jagdflieger campaign link: https://www.digitalcombatsimulator.com/en/shop/campaigns/bf_109_k-9_jagdflieger_campaign/ ;) :thumbup: