Redglyph

If that was not a bug, we would have the same behaviour on all planes and/or all DCS versions, and we wouldn't have the setup box "lying" to us.

OK, thanks, I did see the other thread on 'cold start mission' but that was a different issue, so this looked new to me. I just wanted to make sure those were known, but I see it was already in good hands! :)

For those who haven't read the whole description, I'll try to summarize: - there is no way to tell whether we need to invert the axis or not, except start a mission, start the engine, roll, brake, cancel, and re-do the mapping again (for details, read the 1st post) - why simply not fix a bug? And finally, this thread was not meant as a debate, but as a bug report. But have it your way, I give up.

You probably think you're very funny or terribly clever, but actually that's not helping when someone is trying to report a problem.

I would provide a .trk, though for most errors above it wouldn't matter, but it's not possible to save them in training lessons unfortunately. Is that why these bugs were not reported? If those reports are badly perceived by the team, just let me know why, I'm just trying to help. 5) I've also noted an error in the audio or the subtitles, see attachment. We hear "22-25°" and the subtitles show "20-25°". 6) Way before 2nd and 3rd turn, there is already an instruction to turn, it's too early. UPDATED 1) There are actually more cut texts than in my first test, also in downwind for example, I had 4 of them cut when I re-did the whole landing training. In each case it wasn't possible to hear more than 1-2 seconds at the beginning or to read the text. My speed was correct so it seems due to misplaced triggers.

I understand that different hardware devices may react differently, the problems are: - the wrong feedback in the axis tune window (the value does increase when I press the pedal, without inversion, as I wrote in my post, this indicates the braking increases with pressure so I definitely don't expect to invert this behaviour), - the different behaviour depending on the version, mainly between 1.0x, 1.5x, 2.0x, now 2.5x... Maybe it doesn't vary on individual modules on the same DCS version, but this is obviously confusing anyway. The different devices you mentioned are a good point, the problem there comes from the so-called "default" settings not being taken into account once it has been changed by the user, which is actually another bug in itself. If it worked, the settings would already be correct on a new module.

Haha, I had it all backwards, but then I thought it was related to the OP and didn't see the point of the 2nd post :D Time to study those systems then.

Not clear to me, do you mean it was possible before and not anymore since 2.5.3? And do you mean DCS, or what is FCS?

Pilot's opinion (but definitely not on this bird or anything close): when you fly in a real aircraft, your vision is focused on infinity, and those reflections tend to be discarded because they are much closer and thus become blurry. In the simulation they are on the same screen, the eyes are focusing on them as well as what is behind the canopy, and so they are obfuscating the view to a greater extent in the sim than in reality. It doesn't look as if that had been taken into account (some games have that feature but I doubt it would be easy or even desirable in DCS). It is possible to roll the aircraft a bit if they become really annoying, such as when you have the sun directly behind. It's possible to move one's head also, but not on those models since those pilots are fastened quite securely to their seat, and the cockpit offers little room to move. In the sim, it is still possible to roll the aircraft, but the position of the head has not been taken into account, those images are static. So moving slightly the head has less effect than in the real cockpit, there the curvature of the canopy makes the reflection move around differently (hard to explain in a few words but look at a curved mirror and you'll see the effect). This difference makes the reflection more obstructive in the simulation, sometimes. The combination of this and the previous limitation makes them look as stains, not reflections, which is distracting. I haven't tried during the night. At that time, in a real cockpit, it is very annoying, I suspect this becomes the opposite in the sim? On the other hand, the fact the reflections are not taking the head's position would become even more noticeable and break the realism further.

I have observed the same behaviour, I hadn't tested the module in the previous DCS versions so I couldn't compare but it did seem very odd to see it start like that in 2.5.3.

The wheel brakes axis must be inverted when they are mapped to pedals, otherwise it brakes all the time. I've seen this inconsistency on several other airplanes, it depends on DCS version and the module. There is no a priori reason to require this inversion, since pushing on the pedal is the natural way to brake and this axis always work that way. Moreover, the bar on the axis tuning screen increases when one pushes on the pedal, without checking the "invert" box, which indicates it should work without inverting the axis.

I noticed a few issues in version 2.5.3.21153: 1) Some texts are not read until the end, they are cut by the next one. For ex the 1st screenshot shows a text that cut the previous one, I think it's mostly on cross and base that this happens. 2) On landing, the displayed text is correct (2nd screenshot, "adjust your landing attitude"), but the audio says "your landing aLtitude". 3) The altimeter is not pre-set to QFE and I haven't seen the airport's altitude, its QNH is not given either, which leaves the pilot without any vertical reference. 4) After stopping at the parking, doing the igniters clean-up then idling, the training mission remains stuck at the "all switch to off" stage, see 3rd and 4th screenshots (it's not easy to see the switches because of those highlighting boxes as usual, but I checked them closely and they are all off). Not sure there was something after, I had to quit in that state. Hope it helps.

Well, it seems on and off, after multiple tries it finally updated. So don't give up if you have the same issue. Here's one of the logs when it fails. I tried to install additional modules but I can't reach the server anymore, again. It really seems like one of the update servers has serious issues. 00000.000 === Log opened UTC 2018-09-01 18:42:27 00000.006 INFO : DCS_Updater/2.9.4.76 (Windows NT 6.1.7601; Win64; en-GB) 00000.006 INFO : cmdline: "S:\games\DCS_beta\bin\dcs_updater.exe" --apply install YAK-52 00000.008 STATUS: Initializing... 00000.008 INFO : basedir: S:\games\DCS_beta 00000.008 INFO : dcs_variant.txt: openbeta 00000.011 INFO : DCS/2.5.3.21107 (x86_64; EN; WORLD,POLYCHOPSIM_SA342,RAZBAM_M-2000C,L-39,FW-190D9,UH-1H,A-10C,P-51D,KA-50,F-15C,P51D-HIGHSTAKES_campaign,BF-109K4,UH-1H_video_EN,MIG-15BIS,F-86F,A10C-PIERCING_FURY_campaign,F86-MIG15-RELIC_campaign,F-5E,MIG-21BIS,MI-8MTV2,SPITFIRE-MKIX,BALTICDRAGON_A10C-ENEMY_WITHIN_campaign,AJS37,UH-1H_ARGO_campaign,LAIVYNAS_MI-8MTV2_OILFIELD_campaign,WWII-ARMOUR,A10C-TTQ_campaign,RAZBAM_AV8BNA,A10C-REDFLAG_campaign,F15C-REDFLAG_campaign,NEVADA_terrain,MAPLEFLAG_F5E_BFM_campaign,NORMANDY_terrain,SPITFIRE-MKIX-OPERATIONEPSOM_campaign,L39_KURSANT_campaign,FA-18C,PERSIANGULF_terrain) 00000.011 INFO : branch: openbeta 00000.011 STATUS: Connecting to update servers... 00000.472 INFO : Got reply from http://www.digitalcombatsimulator.com 00001.692 ERROR: Conection to server 'srv3update.digitalcombatsimulator.com' failed: Couldn't connect to server 00001.692 ERROR: srv3update.digitalcombatsimulator.com replied HTTP -1 00001.694 ERROR: Couldn't connect to server 00003.141 === Log closed. After a few more tries, srv16update.digitalcombatsimulator.com was fine for the update, in case it helps.

I have the same problem, but it's not my provider so it must be something else. What I posted in the wrong forum earlier: I was trying to update from 2.5.2.20601 to 2.5.3.21107, after a long time off DCS (heatwave here made it impractical). But no luck, the updater only says "Couldn't connect to server" (DCSupdater 2.9.4.76) Is the server down or is there something I missed on the update procedure?

Pretty interesting and informative interview of test pilot Jyrki Laukkanen, who has many hours on MiG-21 F-13 and Bis, among others. One particular detail, but on the -F variant, is described 14:37 regarding AB limitations, not sure they apply to -Bis. And confirmation at 29:30 that the -Bis is heavier to handle than the -F but much better equipped. Make sure to have a look at the model at 35:30 ;)

If you find that long and boring, perhaps it's not for you. But yes, it can be annoying to realise all you have done for a while is in vain because of a bug... I actually thought you were kidding about the testing bit, we can't seriously expect someone to go through a 10-hour test each time there is a new release. And when I'm saying a 10-hour test, it's without considering all the possible deviations they have to test too, so multiply that by .. a large number. It's impractical. What would be nice to have is a wider set of non-regression tests for the aircraft module. I have no idea how they proceed for that.

It's so shocking indeed :D

It's a mystery. Since it's quite long to load the first time, sometimes I used to switch to a document to read, and DCS was reclaiming the focus every two seconds or so, this part of the code must have been WIP for a while. (I don't do that anymore, touching some keys on the keyboard apparently triggers a re-query of the licence keys so it's best not to touch anything, and wait patiently.)

As before, it's not exactly the same problem with win7 but similar. There's a lot of focus switching back and forth when starting DCS, and starting a mission. I think it may partly depend on the DLC protection because it's not the same in free or stock campaigns as in paid campaigns, perhaps you could check if you see a different behaviour too. Also, when starting the editor, some initial mouse clicks are ignored sometimes because the window is losing focus, and it flashes a few times before finally getting normal. It's really a bit erratic. I never saw that before 1.5 (except the older versions that had multiple executables for the menu and flight and which were glitching all over the place when launching a mission, but that's very long ago), it appeared in 1.5 and got worse in 2.0/2.5.

On top of what was said, I'd recommend the Basic, Advanced and Tactical, starting with the Basic to be sure you like this kind of campaign. But read the parts of the manual that are relevant to the next mission, then try the practice mission, and once you are comfortable with it, pass the same campaign mission. If you're willing to spend the time, only do the training missions then do the full campaign as a whole when you feel ready, that will effectively be a full review and repetition helps learning. You can also read the next manual part and check if there's a stock training mission on the same topic, I usually find it easier to get the info from two sources of different nature (book and hands-on), but that depends on your personal character. EDIT: Oh, Red Flag is a very nice experience. It's a bit easier than most of the other campaigns IMHO, so you could try it after the Basic qualification. Piercing Fury and Enemy Within are awesome too, though more intense. I haven't tried Stone Shield.

Start DCS and open the module manager, if that's not already done, this will install the campaign. Then simply select it form the campaign menu and start it.

Link for those who can't see the embedded video above:

Communication menu is not active until a comm has been selected (and even so, it was simply not working in the Instant action harrier landing mission), and using comm1 for ex. does not show any frequency. The mission editor doesn't show it either, so it's hard to guess. I suppose it's a fixed, hard-coded frequency for now. Thanks! :)

I was surprised to find a full section of the NATOPS flight manual on a "Banner towing system" (9.3). It's obviously meant for target practice and not advertising the latest fancy brand of toothpaste, but I'm wondering why they would use an F/A-18 for that, when airspeed is limited to about 220 kt anyway. Perhaps when they're based on a carrier. My favourite part is "Banner Release Failure. If the arresting hook fails to extend, the banner cannot be released. In this case, the following procedure is recommended: 1. Select full afterburner while increasing AOA in an attempt to burn through the cable." Can't wait to try that ;) Here's a short article on the subject: https://www.stripes.com/news/pilots-hone-skills-in-dogfighting-off-coast-of-iwakuni-1.42749

Next missions :) 4. Overview and TACAN-ADF Navigation (probably "Overview *of* TACAN-ADF Navigation") 1) The user can practice navigation, but the goal is not clear, is that free flight? When does it stop? Since setting a course has been taught, perhaps an exercise and a check that the user has the correct approach vector could be implemented instead? 5. Waypoint Navigation 1) Setting the Tacan on the UFC. The user is told to press ON, then 67 ENT. But when I press ON, all information that was displayed before (T/R, RCV, ...) is switched off. Sometimes one has to press two times on the ON button, but the logic of the correct sequence is not entirely clear (as the communications with ATC which seem impossible on manual frequency). Also, the highlight marks make it harder to read the keyboard, they should be removed or made more discreete as discussed before. 2) The user can practice navigation, but the goal is not clear, is that free flight? When does it stop? 6. VFR Airfield Straight-in Landing 1) The user is told to use the barometric altimeter, why not contact tower and ask for QNH, so we know the altitude? It should be a mandatory step. 2) "Press spacebar" at the end of the explanation, then immediately after, no text but "press spacebar to unpause...", could be merged. 3) One word of a text is said, then the voice skips the rest and directly goes on to the next part ("At this point, you should be on-speed with an angle of attack[...]" is cut after the first word by "Being below 250 knots, go ahead[...]"). 4) "Do not flare the aircraft, but rather continue on the glidepath and touch down at no more than 800 feet per minute.", and "Maintain on-speed AoA and fly the aircraft into the runway with a vertical velocity of no more than 750 feet per minute, as displayed over the HUD altitude indication. Do not flare.". Is it 750 or 800? 7. VFR Airfield Overhead Pattern Landing 1) In this mission, radar altitude is used, and not in the previous one. Is there a reason? Shouldn't that be said? 2) The velocity vector can be caged. Honestly, I don't see any difference, what should I be looking for when there is no crosswind? 3) The user is told to set course of 70°, but Kobuleti is 64°. 4) I get the indication to drop to 600 feet and so on, on downwind, but nothing after that, even after landing and stopping (trigger issue?). Note that there is no option to save the track, so I can't provide you with one.