Redglyph

The only small problem I've seen in 1.5.7 was ... oops. Let's not spoil it, you don't need to read this part (details at the end). Let's just say it's due to a DCS bug which currently impacts all the aircraft in 1.5.7 and 2.1.1. For the Museum Relic Campaign mission I have in mind, it's not a blocking problem, it just removes a small part of fun :) If that's a concern and you have already updated, you could "update" back to 1.5.6, I've done that in the past for another campaign and it's a seamless process which doesn't take much time. If you have other campaigns for the Huey or the Mi-8, it would also spare you all the current problems with the sling load. See this thread for the versions, and how to "update" (earlier posts).

Funny how people keep asking the same question when the answer is a few posts above (and several times actually) :rolleyes: Well, it's not as if I'd never done it myself I suppose :D 1.7 GB in 1.5.7 even without skipping the previous update, but I gather the difference between users depend on what add-ons they have installed. It seems about all aircraft and campaigns are downloaded. That's a lot of chairs ;) Still a lot of those messages: ERROR: torrent: url seed (http://srv3update.digitalcombatsimulator.com/dcs/webseed/A-10C.common/25/<long number here>) failed: The operation completed successfully

Any feedback from Polychop please?

Any feedback? Has this been reported?

Not sure this campaign missions have anything to do with it. It's a Belsimtek/UH-1H problem (at least for the wrong weight update), and perhaps a DCS problem/change for the hooking, see here and here. It doesn't seem obvious, I wouldn't hold my breath. If you want to perform those missions you're better off updating to an older version, check here to see how to do that.

DCS 1.5.7.11476.394 (same in DCS 2.1.1.11317.285) Setting failures in the user's aircraft failure tab, or setting them from a mission trigger, only shows the failure in the debrief but has no impact on the aircraft's flight model. See also this thread which was not reported and contains further details. This has been tested with several aircraft and is 100% reproductible. Two example of missions and the debrief log of the first one in attachment. The first mission (failure.miz) has the failures set in the aircraft tab, within 1 minute, 100% probability. The second mission (failure2.miz) has a simple trigger once the unit is out of a trigger zone, displays a message (that I see) and sets the failures. Also 1 minute, 100% probability. In both cases, the failures are visible in the log, they happened within a few seconds of one another, but the aircraft seems impervious to any of them. No warning lights when applicable. Examples: 1) F-86 with: pp_damage_OilSeparator pp_damage_BladesBrake pp_damage_OilPump hs_damage_MainHydro pp_damage_Ignition 2) P-51 with ENG0_JAMMED 3) L-39 with generator and emergency generator That would also impact some DLC missions, apparently, like here: https://forums.eagle.ru/showpost.php...5&postcount=50 (and other following messages). EDIT: attached debrief log rejected by forum uploader failure.miz failure2.miz

Yes, and you asked where to store the skin mod (so, files) so you could use them with those missions. Once you have installed them in the directories shown above, you just have to edit the mission if you want the aircraft to have that skin. You can only do that in the mission editor, just edit the training mission. There are two caveats: - you have to fetch these mission files in the DCS installation directory - it will be replaced by the original mission as soon as you update DCS You could simply copy the training missions in your user directory first, to avoid those problems. In missions you launch from "Mission" (and not "Training"), you are allowed to set things with the mission planner before flying, perhaps the skins are one of them. You could try, after installing the skin mod, to run the training mission by the "Mission" option in the main launch screen and do that. I haven't tried myself so I can't guarantee it works. Again, you'll have to fetch the mission file in the installation directory if you haven't copied it elsewhere.

*EDIT* That's a fair point. I'll create a new thread to revive this bug report as I'm not sure PM'ing possibly the wrong person would be the way to go.

You should be able to install them into either - <DCS installation dir>\Bazar\Liveries\<aircraft> - %USERPROFILE%\Saved Games\DCS\Liveries\<aircraft> (actually, DCS or DCS.openbeta or DCS.openalpha depending on the branch you're using) So for instance for a MiG-21bis livery, if your username is "sim", if you're using the openbeta and your livery is called "training": c:\Users\sim\Saved Games\DCS.openbeta\Liveries\MiG-21BIS\training Under the training directory, you must find the description.lua, and optionally other files depending on your livery. And you should see, next time you launch the Mission Editor, that the livery dropbox includes a "training" item :)

Err, I have no idea what I'm supposed to see? To me it seems pretty much level but the autopilot is off. Did you use the trim? As I said before, please indicate what is wrong and when ;)

:thumbup: :D (and I'm keeping the link for the cold winter about to come here)

It's strange, it's what I had with the FFB on (and like you, I don't see why it's not in the Special/S342 page either, given the impact on the controls...). Perhaps it was just coincidence it disappeared, I'm not sure but others also had control problems with FFB on. See also this: https://forums.eagle.ru/showpost.php?p=3282468&postcount=3 (but you did disable it so... it's just the "no difference" part that is curious, could the setting be overriden somehow?) It's a long shot, but you could post a track in the bug section, I'm not sure it would display the control positions in the bottom corner if you enabled that when "recording". I'm not even sure the track file contains control inputs or only the aircraft movements - my guess would be the control inputs seeing how replaying those track files fails sometimes, on beta versions or when the FM changes? If that is the case, it means someone else could play it back and check whether they see the same behaviour as you? I never had a reply from Polychop though, I'm not sure they're very active in the forums. But if you post a track I'll run it on my system to compare if you want. Just tell exactly when to look for a pitch up or something wrong. EDIT: The track idea works! I've recorded a small flight in which I'm trimming the Gazelle to fly low and level under power lines, then trim up a bit when the terrain climbs. Playing it back is fine, playing it back with FFB on is completely different, it mostly just spins around above the apron :D So you could try and record a track file :) SA342.trim.trk

Probably linked to this one? But I haven't received any reply from Polychop either. https://forums.eagle.ru/showthread.php?t=195433 And perhaps I'm doing something wrong, but I couldn't jump into the Gazelle in client mode, it was working fine for other modules. I can select the Gazelle, but when I click on the Fly button, I remain spectator outside the aircraft and can't get in the pilot nor the copilot seat.

Oh, I see, thanks for confirming! :) I thought it was out of beta, despite the unfinished manual. Not a big problem I suppose.

Reviving this old thread. Is RD implemented now? I tried to run this mission again but can't seem to make this part work...?

No, it's not necessary, just create a D:\DCS folder in which you install DCS. Or even better, a D:\sim\DCS1 for version 1.x and D:\sim\DCS2 for version 2.x, for example. And if you want to store something else, use other folders at the root like D:\documents and so on. Don't forget that DCS also stores some files in the %PROFILE% directory, most usually in C:\Users\<name>\... so this will takes some disk space on the C: as well, though much less than the installation directory itself (files such as screenshots, the logbook, track files, configuration files, shaders and so on - for me it takes about one GB, against 81 GB for the DCS 2.1 main directory).

Yes, definitely, especially the loading time of textures with more demanding maps in 2.1 and later 2.5. With an HD you will most probably endure severe stuttering during missions. I don't think an extra SSD should impact the price of this system very much ;) It's best to have a fast SSD, but it doesn't need to be a PCIe SSD. Typical transfer rate are 530 MByte/s for read operations.

IL2 BoS does (and wait for their release this month!), but graphics aren't everything, I like the kind of equilibrium we have in DCS regarding the different features and great aircraft. I wasn't tempted by CAP, it looked really more an arcade than a sim, just a matter of personal preference of course, could be fun sometimes.

Bug tracker is also a ghost town... there was such an active clean-up in March, very promising after the long "winter" of this great module, and it seems to have subsided to another winter ;) Are you guys up to something, should we expect a surprise? :D

Very instructive, thanks!

Well, check the few posts above, perhaps you have the same problem I had by leaving the FFB setting? Because of that, when I was using the trim, I had a sudden and large pitch down or up.

You were right! First I thought you meant the FFB settings in the SPECIAL settings of the SA-342. But after you last comment I checked the MISC and sure enough, this settings was back (I'm pretty sure I had unchecked this before). This was a vicious one. Now it's fine, thanks a lot! :thumbup:

Thanks guys. Well, I don't understand, I checked again the start procedure, nothing is missing. I'm not using simplified controls, the FFB is not used (but then it would just be ignored by my joystick right?). I have even re-installed the module, erased and re-programmed the controls to make sure. I'll just report this as a bug.

Shouldn't that be "Aerospatiale"? ;)

Problems 1-3 were due to the FFB option in Misc settings, the other problems are not directly related and at the end of the post. It would be good to prevent this problem by detecting whether the joystick is actually FFB or not, or having a checkbox on the SA342 page with the other FFB settings! Also, in the manual, pg 14 and 16, - "not recommended for non-FFB joysticks", it is not clear, does it mean we should not use the magnetic brake on the stick, or on the panel, or both... ? - "recommended for non-FFB joystick", again, it is not clear, must we avoid that (and what exactly?) if it's an FFB joystick? Aren't those set by the main settings option? My original problem report: Five other issues 4) There also is a puzzle for me, there are two commands "Magnetic brake On/Off" and "Magnetic Brake On/Off" on two different panels, did I miss something in the cockpit preparation? 5) It's not possible to move the "Cockpit vibration" in the special settings. It takes a lot of clicking around to finally be able to move the slider, sometimes I can't do it at all. The other sliders are fine. 6) The starter is ON in hotstart (so is the pump). 7) Manual is incomplete 8 ) When the altimeter is calibrated from 1019 to 1020, it reads "1010", the last digit is back to zero before the other digits are incremented.