Redglyph

Simply edit the mission as I did above and it's much better. After this Su-25, you can optionally chase the other bandits :) I can't upload the file for copyright reasons, we just have to wait until Heatblur reads this and updates the missions.

Strange that it wouldn't spawn at all, you don't even see a speck in front of you at the very beginning? To solve 1 & 2, I just set it (target1) to late activation, and added an activate action in the unpause trigger. I haven't tried to delay the dialogue, so the first two dialogues are still missing (the first time I run the mission).

Only if you don't take it too personal when we report issues on this great module ;) Thanks for hunting them down!

Thanks! Yes, I realized that later, I should edit my post.

DCS 2.5.4.28615 Same issues as in the guns mission: 1) An enemy aircraft is spawned in the front of the user's, but the active pause is on, and while the user's F14 remains at the same place, the enemy aircraft flies out of range. As a result, a lot of time is required to catch up, if it can be found at all, which is not the purpose of the mission. 2) The dialogue is mixed with Jester's voice when he's spotting the enemy plane, which makes both dialogues incomprehensible. => the enemy plane should only be spawned in front, once the user press SPACE and the active pause is removed. 3) The dialogue starts late because of the initialization and is cut. This only (mainly?) happens the first time the mission is run. => wait a while before starting the dialogue. Temporary work-around for 3), load the mission, abort, load it again.

Haha, I tried to report that in another thread (among other disk space-related issues) but only got irrelevant remarks saying basically that it was fine like it was. So good luck with that.

The problem here is coming from most people not reading correctly a post. I won't even try to answer this further, it was not meant as a debate anyway. It will come naturally later from someone else anyway.

Wow. OK, thanks! :) That was the correct answer to the OP.

DCS 2.5.4.28461 Shore-Based Landing mission 1) The diagram on the briefing page is unreadable 2) Like some other training missions, the audio text at the beginning is cut. It is displayed once the mission starts, but since the user must get busy to adjust the throttle and other parameters to the starting conditions, there is no time to read it. After 10 seconds or so, it begins being narrated but then it is cut almost immediately with the next instructions ("set hook bypass to Field..."). This behaviour is not always consistent, restarting the mission makes the audio earlier. Other missions For example, the "gun gun gun" tutorial has a similar problem. There isn't even audio until "If you want to use the radar to track and compute a firing solution", and the text displayed earlier just before that is sometimes so brief it's impossible even to type PAUSE. At some point I saw the Gun Rate and the Master Arm switch highlighted and no text for a while, then a short text flashing mentioning to open the Master Arm cover and set to ON. Etc. In conculsion the whole beginning of the mission is very confusing again. I think it could start smoothlier with a trigger on time or position, there are probably transients at the beginning of each mission due to fact this aircraft is more demanding. This makes the mission start very dependant on the system it is running on, and the performance-related options.

I just checked, it is closed - obviously I'm not talking about this thread, but the one linked above ;) It's not a bug, but what looks like interesting information, however it is another version of the Farmer as I said above. Maybe it's why it was closed. That's why it would be interesting to indicate why a thread is closed (when it's not obvious).

There's a long thread about it (outside of the bug/problem section): https://forums.eagle.ru/showthread.php?t=234927

That seems to be an entirely different version of the MiG-19, not sure it's relevant. Unfortunately the thread has been closed for some unknown reason.

Even if you target the switch and the mouse cursor transforms to the clickable shape, most positions do not react to the click. The user has to aim to the right of the switch to be able to click it from SHUTOFF to NORMAL. I tried to take a screenshot but the cursor is not shown (it was on the tip of the switch but it wouldn't click).

Thanks Baltic! So that answer the question on those two pairs of switches I guess (afterburner cut and oil cutoff), they are only used as emergency and should remain OFF. Not easy to find an English translation of those manuals :/

Yeah... I saw the video (and was not a huge fan of it frankly) but it doesn't link the two problems, and hardly counts as a report in this forum in the first placce, I suppose ;) PS: also, the author of the video states a lot of things without giving any source, so I'm can't rely on that info, to me it's just venting (perhaps necessary for some under the circumstances, but that's another story)

DCS 2.5.4.28461 I noticed a little glitch in that mission, there is a text saying to move to a specific catapult, but there is no audio and the text is only briefly displayed. I actually missed it the first time because I was looking inside the cockpit, then at some point I was instructed to sweep the wings forward and to put military power, which seemed very strange from the starting position ;) The Tomcat is also dancing furiously on the deck, it seems that the aircraft in DCS are not yet statically linked to the ground they are on, they're slipping back and forth (and up/down) all the time. It didn't seem that obvious in the cold start mission.

Found out it happened because of the Afterburner Cut switches, I've finally reported that here.

DCS 2.5.4.28461 I previously reported a problem in training mission 2 (cold start), but the problem seems to be in the system modelling and/or in the documentation. In summary, the problem is: after clicking on the Afterburner Disable button of the throttle quadrant, - the military power lamps don't illuminate as expected when the throttle are fully pushed, and - the afterburner is not restored as expected after clicking on the Afterburner Enable button. This doesn't occur in other missions (hot start / air start). It turns out both problems are due to the "Left/Right Afterburner Cut" switches, which are set to ON during the pre-start procedure. So I'm wondering, - Afterburner Cut, ON = the afterburner is cut? or is that the reverse? - Engine Oil Cutoff, ON = oil cut? or is that the reverse? I think there's a confusion here. Note that either position doesn't seem to bother the engine for the oil cutoff, so maybe this isn't modelled yet due to the very early access status of this module. Could Razbam clarify this little yet important part? :)

As has been answered, cheap SSDs are not always the best, and comparing a simulation that requires a fast SSD with a game which doesn't isn't a good argument. I repeat, the problem is not only SSD but very long downloading times, and most probably disk loading to the memory, memory occupancy, and so on (no wonder one gets regular freezes). Just disregarding a problem saying "I don't have this problem so you should not have this problem either" is also very selfish IMHO, but it seems the norm here. So have it your way, let's encourage 3rd parties to include unrelated files in DCS, and sorry to point out a problem that was already pointed out and fixed in another module :p Jeez, some people.

Fine, let's encourage them to waste precious disk space because another completely unrelated game is taking more. That's a very good argument. And yet not long ago, similar reports were made for the Fishbed which was taking less than this (and for relevant files).

Sorry differ but in my opinion they need to optimize a little bit instead of asking everyone to buy a larger disk, 8.5 GB is completely off the mark. Recently, M3 said they'd make an effort for the MiG-21bis, which was also taking a ridiculous amount of disk. Unnecessary stuff like those WAV files have nothing to do in there. Yes, some SSD are cheaper... and probably also less reliable or less performant. In any case, I'm not eager to reinstall everything for that kind of reason.

I'm using an SSD. You are correct, before that I was getting a lot of those when starting even the Nevada map in 1.5. Since then it's smooth (except Normandy) :) It happens also in very local flights, for example the shore take-off or the landing missions. So it's likely the F-14 either computing or initializing something, or loading data. I suppose a good test would be (i) very low world radius, (ii) low-quality textures, in order to see where this is coming from.

I have 16 GB of RAM for the CPU and 6 GB for the GPU. In general the performances are OK when using the simple training missions. Some of them have static F-14s so it probably doesn't represent a typical busy mission. I get regular freezes of 1-2 seconds in flight or taxiing, that I never get with other modules (in Caucasus, that is, I didn't even try in Normandy). Seeing the huge amount of space it takes on the disk, it could be due to the little space remaining in memory for the DCS world after the F-14's textures are loaded (overall it doesn't look as if optimizations were the primary concern). Or it could be the module initializing something, I don't know, it's just breaking the immersion quite effectively. It's otherwise a great module, I hope those performance issues can be tackled soon.

DCS 2.5.4.28461 The F14 is currently by far the largest module, it takes more than 3 GB of disk space, and another 5.4 GB in the CoreMods folder. So about 8.5 GB only for one module! SSD space is precious, and download times are getting long, would it be possible to reduce that somewhat? Some of that seems to come from uncompressed files. For example, - "Soundtrack" takes 540 MB, those are *.WAV files that could be compressed. Actually they're present twice: their *.ogg counterparts already eat up 100 MB in Sounds/Walkman. Are those .WAV files related to DCS? And are they necessary? Perhaps they could be optionally downloaded on another site for who wants them? - the manual is 252 MB! That's more than a scanned book of the same size, and it makes the reader struggling when going through. There is an option to compress the images when building a PDF document, it should be used. I'm pretty sure the textures can be compressed too. The problem is, if we remove those files ourselves, they are downloaded again on each update.

To add some information on this issue: I observed the same problem with the kneeboard controls on the MiG-19P but it disappeared on its own after starting a mission with the module and restarting DCS a few times (for other reasons). I changed other bindings so it may be due to that. When I'm looking now at Config/Input/MiG-19P/keyboard/keyboard.diff.lua, DCS added one (?) of them as "removed" without my intervention. This command is in the common files, Config\Input\Aircrafts\common_keyboard_binding.lua (while yours is in the module's defaults): local diff = { ["keyDiffs"] = { ["d3003pnilunilcd100vd1vpnilvunil"] = { ["name"] = "Kneeboard current position mark point", ["removed"] = { [1] = { ["key"] = "K", ["reformers"] = { [1] = "RCtrl", }, }, }, }, I confirm the same duplicated orange lines as you for the Viggen, but I haven't flown it so I can't say about the "auto-repair" which happened on the Farmer.