Redglyph

No, just plain DCS.

Ouch, including a 35-MB image as a sub-sampled and dithered gif is probably not very user-friendly to those who read the forums... Next time just a link or a couple of actual screenshots would perhaps be more appropriate? ;)

DCS 2.5.4.25729 The switches, knobs and other details of the cockpit have projected shadows when a light source like the sun is behind them, as if the fuselage, panels and those controls/details were semi-transparent and the sun could go through. See two first screenshots on the Mi-8 and Huey, - the Mi-8 (bottom right): the shadows seem to come from the two light knobs on the rear panel near the door, - the Huey: the upper panel projects shadows of its switches on the front panel. It reminds me of the old problem of strobe and landing lights illuminating the cockpit, again as if the fuselage were transparent, perhaps both have the same root problem in common. My settings in the 3rd screenshot.

Anyone else had this problem? It's actually happening quite often, no matter which module.

I assume you mean AeriaGloria's problem (since mine was solved, at least the 1st and foremost of the 3 items). That's good catch, I couldn't really see what could be going on. In doubt, AeriaGloria, display your controller position with RCtrl-Enter (I think), that could confirm the issue. Adding a small track will probably help the devs, if they see this thread. That's what I mentioned in my first post, the synchronization has never worked for me, I have to move it a little bit at the beginning so that it's taken into account, and since I was new to DCS when I first saw this problem I did submit a ticket but got "wave fly away" type of reply, so I understood that was not how things worked here ;) So it can't hurt to try and open a ticket, just don't expect too much coming out of that.

Speaking of Early Access Manual, there are two of them, "DCS FA-18C Early Access Guide EN.pdf" and "DCS FA-18C Early Access Guide EN-13 November 2018.pdf". The former seems to be the last version but I'm not sure. I would suggest to put a version number in this document, to know which version potential corrections (like the ones above) are referring to/in which version they are completed. I'd also suggest to avoid changing the name of the document back and forth because it's most confusing when trying to keep track of them.

DCS version 2.5.4.25729 (but has been like that since 1.5 or even before) On the F10 map, at the bottom and when an object is selected, only the latitude is shown, not the longitude, it seems the field is dark or skipped (see screenshot). I know it's possible to get it at the top by zooming and keeping the cursor on the symbol, but for INS alignment or in-mission designation for example, it's not practical. Moreover, it seems to have been designed to have both lat/long shown on the selected item.

I checked the full start / M2, it's great so far! I agree with sze5003, the rate is pretty fast and the first time I was easily lost on a few items, including the alignment (the behaviour of the numpad was a bit strange, at first it wouldn't let me enter latitude, and only W longitude, not sure why). It seems you did extra work to verify the state of the MFCD state to highlight the correct button to push, or am I imagining this? I also liked the Easter egg at the end ;) A couple of items, though I'm not entirely sure and I didn't have the time to run through it a second time: - the cockpit handle and lock stay illuminated for a good part of the training, I suppose the highlight off is either missing or with a bad index, I even tried to open/close it again but without impact on it, [EDIT: I had closed the canopy before it was asked the first time, that's when I got this highlight issue, I don't have it if I wait until being told] - it says at some point, once the engine has started, that "now you can open the cockpit", which sounds strange, that's precisely when I'd like it to be closed so I can hear myself thinking ;) On the other hand, it was supposed to be closed before that, so it's not incoherent, just surprising. Perhaps when it's very hot, is that common practice to close it during the engine start-up and open it after? I like the idea of a continuous training that doesn't stop after the engine start-up, if you can manage that once the module is stable, it's a great idea (I understand how you prefer to keep it split for the time being though!). Looking forward to the other missions when I find the time! It's good news we get quality missions for this jet :) EDIT: A few minor things worth checking - EDP BIT: the instructions are given, then immediately further instructions are given on the DECS/shutoff valve, without waiting for the pilot to perform the built-in test, it may be confusing - "Watch for the CANOPY caution light to extinguish" - it's not illuminated to start with (apparently it's only illuminated when the cockpit is closed but unlocked?) - the instruction to cut exeternal power may be confusing since we're not asked to switch it on in the first place (or did I miss it?) - perhaps it would be good practice because I see that the battery is down to 23 V when we are told to start the APU, even without lingering - "Listen for the APU to decelerate for 10 seconds before the GTS engages to start the engine" - well, further instructions are given right after switching the engine start, so we can't hear the APU noise, it's covered by the instructor's voice ;) - same for H2O switch - "Next, we will conduct a JPT Limiter check", doesn't wait for the test to end, the instructions "Cycle the EFC switch to POS 1." are given immediately, confusing the pilot again with the next item while he's about to start the current one (the instruction even go to the "Reset the switch to POS 2" without waiting, I still have to stop the JPTL test...). Or was it necessary to do both in succession? - There were instructions before the "Set the barometric pressure", and after the trim to 4°, but it was lost on me because the text disappeared and I was busy with the trim. - FLAPS: I don't see any FLAPS POS fluctuation during the BIT(?) - "Pull the stick back and check EDP stabilator position at 10° up.", I only get 8°, but probably because of the 4° trim required before - "request taxi clearance"... but we didn't request start-up clearance ;) - "Even at idle power you can start to build up excessive ground speed", I just stop rather quickly if I remain on idle, even at 10°(?)

Here's the link mentioned above: https://forums.eagle.ru/showthread.php?t=114030

Yes it is... it must take some time to read. What makes me laugh is how much people try to sell it on Amazon, eBay and so on. Well, good for them if they succeed. It could be due to a 2nd edition in the works, they did the same for the Su-27 to add new material (30, 33, 34, 35 variants). I'm not sure there is a lot of new material for the Fishbed to justify that, however, it's probably just wishful thinking.

Glad it helped! There were rumours of revamping the Hog, hopefully ED will address those issues once for all at the same time. Perhaps they need a little encouragement though ;)

The only problems I fixed in the CMSP are - the "Master CMS Mode Select" was not stopping at min/max - the "Jettison Countermeasures" was not responding to right click If you don't want those 4 system switches to jump up from the bottom position, just use the left-click, this has the advantage that the right-click only does one function, the top one, and the left click does on/off, which you probably don't want to use by accident. I know it's not entirely logical but I think it's a limitation of the current function: the right-click is mapped to a spring switch, the left click is mapped to a 2-position switch. Anyway, sorry but I'm not going to spend time trying to change anything, given this patch will never be integrated by the dev team and I'd have to maintain it with every change.

I understand your frustration all too well. As said before, some of these bugs are general. The fact is, DCS has a great engine and very good modules, but it's more focused on forward development than stabilizing the base. As a consequence, 3rd-parties must often update their modules and repair what is broken with the ever-progressing engine, and most of the problems remain for months or years. I remember posting issues with the UH-1H training missions more than 3 years ago and they were never addressed, the weapon training is still broken AFAIK. I like DCS but each time I open it, all I see is all the little (and sometimes bigger) things that break down the immersion... which, yeah, makes me bitter sometimes. There are more stable periods, let's hope we get there soon. To come back on the Huey, I don't know if you have other modules but if you don't, I'd advise to consider "downgrading" to an older and more stable version of DCS, at least for the time being. Check this very useful thread for a list of the versions, and update instructions at the top. If you have DLC for the Huey, make sure it exists in the version you choose. Is "downdating" a correct term? :huh: Anyway. Any version prior to 2.5 will have much better performance, especially in Caucasus. If you fly lower, which is usually the case with this helicopter, the new 2.5 engine suffers a lot from the proximity of the trees and, to a lesser extent, the ground, so the performance quickly go down unless you have a very high-end PC. When I was hovering near trees recently, I got much less than 1 FPS in 2.5.3 (no, it's not a typo). You didn't make a bad choice, by any means, the Huey is a great DCS implementation of this helicopter, probably the best, you should check this two-part review on it: https://www.helisimmer.com/news/dcs-huey-accuracy-test/ https://www.helisimmer.com/news/dcs-huey-accuracy-test-part-2/ The campaign that comes with it, and even better, the Argo Campaign are both a great help and incentive to master the systems, I highly recommend you try them and learn along the way, with the help of the manual. The official training missions were never finished so I think they aren't worth trying. For the story, Belsimtek were much more active in the Russian part of the forums, which explains the unanswered problem reports. Now they have merged with ED, we'll see if that improves the feedback in these parts of the forums... Again, until there is an optimization of the engine and an update of the Huey, I'd simply update to an older version of DCS, preferably before 2.5. EDIT: For a temporary version, I'd probably consider the 1.5 branch ("The Current 1.5 Legacy Build Version is: 1.5.8.13716"), but it mainly depends on which modules you have.

It's a well-known bug in Razbam's modules. When the configuration file doesn't exist yet and the user tries to configure a module from the main menu, DCS crashes. Somehow it creates the configuration file from within a mission, but fails to do so from the main menu. It can be any type of mission.

What Holton says is correct, thanks for clarifying! The file I provided in the zip has the same size, it's not 7 KB, you must check the uncompressed size. But yes, you must compare the content. If you don't want to install anything, you can also do that by - unzipping Fix_AJS37_cockpit_mouse.2.5.4.25729.zip - opening a command shell (Win-R keys, type "cmd", RETURN key) - typing FC <file 1> <file 2> in the command shell window, with the complete path of the original DCS file, and the unzipped clickabledata.org.lua (you can drag and drop the files in the command shell window to copy the path, instead of typing it) FC will tell you if there is a difference.

Seeing the speculation on this book, I had to ask: So disappointing, but expected I suppose. Anyone knows why they stopped the publishing of this apparently great book? I own a couple of others from one of the authors (Yefim Gordon) and they're full of interesting details for who likes that sort of things, very good books on the Farmer and the Flanker. There's a new one about to be released, though I have no idea whether it's good or not, I'll wait for reviews: "The Mig-21: The Legendary Fighter/Interceptor in Russian and Worldwide Use, 1956 to the Present", Holger Muller (expected early 2019). The Osprey booklet is not bad but very succint.

Check that it's not the opposite, if your shutoff valve lever is mapped to the axis of your throttle controller (that's what I had). When I rshift-home, only the lever moves, when I move the throttle axis (after engine start-up), the lever resets and follow the axis, and the throttle moves as well. I think the fix would be, when it's necessary to force a mapping with a new feature or for any reason, the existing mapping to the same button or axis should be removed (same rule that applies when mapping controls through the menu). Ideally of course, there should be no such forced mapping on DCS updates. The other 2 issues remain: 2) and 3)

Fix in attachment, tested in 2.5.4.25729. Fix_AV8BNA_cockpit_mouse.2.5.4.25729.zip

It's a configuration bug (not sure whether the origin is DCS or the module). Apparently a default configuration was applied on top of the configuration I have been using for a long time. Somehow, it managed to link the throttle controller axis to both the throttle and the fuel shutoff valve inputs! Of course as usual, it also mapped the POV buttons and pitch/roll onto the rudder pedal controller, and other aberrations. After remapping all that correctly (which takes a lot of time in DCS), the problem disappeared. I hope they improve the configuration with a more sensible approach at some point, like the general default settings that one can save but which is not actually used for new defaults, probably something they forgot to complete or didn't pursue.

This bug has been there for years and they have never fixed it, nor have they ever acknowledged the bug reports on that issue. It's not a blocking issue, however, still quite annoying.

DCS 2.5.4.25729 Track in attachment. Trying the cold start training mission. - asked ground crew to place chocks and plug the ground power - switched on the necessary breakers on right & left panels - throttle to idle - open start cap - pressed start button for 2 seconds => engine starting, RPM to 600 - either pressed Home or Shift-Home until the fuel shutoff valve is half open => RPM increasing After engine stable, - closed canopy - pushed the throttle a little bit => shutoff valve closes, the lever is moved to the close position instantly From that moment on, the shutoff valve moves with the throttle (?) but since it's mostly cut, the engine stops. If the valve is opened with Shift-Home again, it goes back to the closed position as soon as the user touches the throttle lever. Bugs 1) Shut-off valve is closed every time the user touches the throttle. This makes the module unusable for now. Other minor bugs observed: 2) Throttle is at max when the mission starts, even though the controller (see signature, HOTAS Warthog) is at minimum: its initial position is ignored at the beginning of the mission. NOTE: the main option "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" is ON, but I've been repeatedly told by Waggs that those were only for the A-10C (for which it doesn't work either), so I'm not sure it's used or not. 3) No tooltip appearing when the mouse hovers the cockpit controls. This is a known bug in training missions. The problem is that they are most needed (especially when the vision is obscured by the highlight effect). MiG15_start_failed.miz.trk

For DCS 2.5.4.25729 (open beta) Heatblur and M3 modules don't always respect the DCS standard regarding the knob and switch handling with the mouse clicks, those are mostly incoherent. Since the problem was ignored, here is a fix to avoid users pulling their hair off using the Viggen :) I hope it helps, let me know if I missed other similar issues. This patch won't interfere with campaigns, missions or anti-cheat protections, it's completely transparent and just fixes the cockpit interaction where it is badly needed. IMPORTANT: There is only one file to replace, and I put the original file in the zip file (clickabledata.org.lua). Before patching DCS, first check if that is the same file as yours. If it is different, you have another version of DCS and it will not work. I will probably not maintain this patch in the future, so make sure to check after each update that the patch is compatible (yes, you have to re-apply the patch after each update, unfortunately). If the worst were to happen and you corrupt your original file, just do a repair (DCS_Updater.exe repair), check this post for the details. In general, always keep a copy of an original file you are about to replace! How to apply the patch? Simply replace the file at this location, in your DCS installation directory, with the one in the zip file: <DCS>\Mods\aircraft\AJS37\Cockpit\scripts\clickabledata.lua What does the patch fix? It fixes the mouse clicks for the following controls, making them work according to the DCS standard (see 1st link above). Legend: - 3 = 3-way switches (left/right click inverted) - R = rotary position knob (left/right click inverted) 1) Left - 3 Canopy Open/Close - 3 Emergency Pitch Trim - R Base Selector note: the rotation sound is heard, even if the knob is at its min/max position and won't move, like the Group Selector and a few other switches, I can't fix that problem - 3 Countermeasure Release 2) Front (none) 3) Right - R Weapon Selector Knob - J/A Valjare - R Weapon Interval Selector Mode Knob - Siktningvaljare - 3 Navigation Lights - R Position Lights Brightness What is not fixed by this patch? The controls below are bit fixed. 1) Left - Canopy Open/Close, the mouse sensitive spot moves to strange locations depending on the position, I can't fix that. - R Base Selector, rotation sound is heard, even if the knob is at its min/max position and won't move, like the Group Selector and other switches, I didn't investigate that issue. 2) Front - Radio Manual Frequency Setting Knob Inner/Outer Left/Right, the user has to drag the mouse a long way to make them change, I haven't tried to fix that. 3) Right - Weapon Emergency Release Button, works through the cover. - IFF Code, doesn't move at all, probably WIP. - Magnetic Declination Correction, doesn't move at all, probably WIP. Fix_AJS37_cockpit_mouse.2.5.4.25729.zip

That would be great! If there is such a plan for a new Hornet campaign, I hope it's the same format as the A-10C qualification campaign, and not the F-5's. It's of course subjective.

This time you should have checked a few posts above ;) That being said, I'm 100% with you on the bug tracker idea/visibility, I have the clear impression that 90% of the bug reports I post (or reported by others that I see) are just ignored. Maybe they aren't, but it's hard to know for sure.

Good to know, thanks! Yes, like the RAT, the status on what has been implemented or not is not always easy to find, though I understand those items are probably not at the top of the priority list.