NightMan

Hi! Uuffff. I'm glad I'm not crazy. Thank you! However, when I started this mission, back in 2016, one of the conditions I had was precisely the weather - I wanted a cold and snowy environment, for reasons which are not relevant now. I've been playing with it and evolving it since then, but one thing I never changed was the weather. And it was working just fine the day before the update. In fact, the last time I changed something in it was in 2021-12-07. So, if the weather is the factor, then ED must have introduced something new to the A-10C model in this recent update. The fresh mission I created didn't take into consideration the weather - I just placed a plane at the ramp and started the mission. After reading your post I increased the temperature on the affected mission to 1º C and tried again, but the result was the same. Then I radically changed the weather to a hot Summer day and tried once again, but it changed nothing.

Sorry. NO, no, and no. I've been "flying" the A-10C for over 8 years and working on and using this mission for almost as long. Nothing has changed, except this last update. Everything was working perfectly the day before. However, I've been doing some debugging and found that the problem is somewhere in the mission code or in the Mission Editor itself. If I create a new, simple mission and run it, all the systems work perfectly. The engines start as usual and the ENG START CYCLE goes out as usual, allowing me to start the second engine. CONCLUSION: The problem is burried somewhere in the program and in the way it treats old missions. I tried editing the mission, change the plane to another type, saving it, changing it back and saving it again, but to no avail. So, the problem is definitely in the way the program treats old missions. Please; someone escalate this to the Devs.

Since this last update the ENG START LIGHT stays on after starting the first engine. Maybe this has been previously reported, but it is the first time I face this problem. Bug Demonstration - A-10C II - Engine Start Cycle light doesn't turn off.trk

Like the title says, the game freezes after the GAU is fired. After several minutes it unfreezes, only to freeze again immediately, even without doing anything else. After about 10 minutes I gave up. Please; don't ask me for a Track. The reason is obvious. I can only provide a Screenshot.

The ground crew seems to be very lazy.

Hi! I haven't flown the Kamov for some time, until today. And I noticed this problem is back. Please; report it again, as it is quite annoying. Thank you.

Is this cross in center of the screen related to tha April Fool's Easter Egg too?

Hi! I am sorry to bother you again with this, but today in a Multiplayer mission I found out that with foot soldiers it still bounces. When foot soldiers are killed the Shkvall jumps and slews around by itself, and (please don't laugh) some soldiers get up, only to die a second time. I leave a small track here. Bug Demonstration - Ka-50 - Shkval jumps after a target is destroyed - 02.trk

So I guess I'm fortunate!

Impressive investigative work. But I suspect there may exist another control causing the same issue because I'm not used to use Shift+R. In fact, I only recall using it 10 years ago when I started with DCS. In fact (again) I don't even have it mapped; I removed it 10 years ago.

I will. Thanks.

This appears to have been corrected in version 2.8.3.38090.

Hi! I am really pissed because today the problem is not occurring and I am not being able to reproduce it. Please, don’t take me wrong, and I don’t want to pull ranks or offend you, but I have a degree in Computer Engineering and I’m used to debugging problems, both in software and hardware, and I’ve been doing it for a little over 30 years. So, I have been thinking about what happened in the other day and there are 2 (two) possibilities I would like to propose: First: I use VirtualBox to conduct all sorts of experiments in a contained environment, and that day I had been using 2 (two) different VMs. VirtualBox might have left something stuck and the Right Control key is my first guess, because, as you might know, the Right Control key is the default host key in VirtualBox; Second: The second possibility involves a documented problem in Windows. There is — or was — a problem in the HID system that caused some USB controllers to prevent the OS from putting the machine into Energy Saving mode. In my case, with the stick connected, the OS wouldn’t even start the screen saver. If I disconnected it everything would work properly. Recently, one of the updates passed by Microsoft — can’t say which one — solved this problem, and now my machine enters energy saving mode and resumes without a problem with the stick connected. I’m not saying any one of these is connected with the problem we are trying to debug, but, for now, these are my best guesses. Talk to ED and see what they have to say. Thank you.

Please forgive me if I don't understand. What you mean is that one key like Control, or Shift or Alt is pressed when I open the Controls panel? That would mean a stuck key? But if that was the case, very weird things would happen while flying, and I am flying just fine. I will try to sort it out.

It appears to have been corrected in version 2.8.3.38090.

Nothing, absolutley nothing changed in my setup. I've even been away from home. I returned, accepted the update and resumed work on a mission I'm working on. I don't know if the problem is new or if it has some time, because I don't change controls every day. And is it me who has an attitude?! I'm just trying to help improving a product and you guys always take it as an attack. You know what; I have more important things to do.

I don't have any mod installed. Just plain Open Beta. It's really annoying when you assume the problem is on our side. It's not the first time someone reports something which you cannot reproduce, so I ask you; please try again.

I noticed it too today, and it happens in all models. I will try to explain. With the previous behaviour, when in the Control Options screen, if we pressed a sequence of keys mapped to some control, the focus/cursor would automaticaly position itself at that control. Not it does nothing. Imagine you pressed G. It would automaticaly position itself at "Landing Gear Up/Down". Now it does nothing. And it is not random; it is sistematic. It happens with ALL the controls. Now it respects only the up and down keys as well as the PgUp and PgDown keys, scrolling just like a normal list. It's not something we could record in a track, but it is EXTREMELY easy to reproduce. Just go to the Control Options screen and press G, or F1, or F3, or any other control you know you have mapped. This was an extremely useful feature. Please fix it.

You know what; you are right! Thank you very much. I have been editing the mission file by hand to solve that. It works exactly like I want, but it's all but intuitive. ED needs to hire someone who knows how to design an interface.

I don’t know if this is a new problem, but it cause serious problems for anyone creating a mission and trying to keep a record – let’s say a spreadsheet – with all the units and their corresponding Unit ID. It makes it absolutely impossible to be organized. What happens is that when adding units (+) each new unit is not added to the group — or if you prefer — placed after the already existing units. Instead, it is inserted before the previous unit, and all the already existing units are pushed down. Because of this we end up with the first unit in the group having the higher Unit ID in the mission. Another way of putting it is saying that the order of the unit in the group is inverted. Please see the screenshots attached.

I still believe it's a bug. Could you please explain exactly what you mean with that hi bass freq? But imagine you go down the street in your car and the exaust backfires. You may jump in your pants, but you never stop listening to the engine. It's the same thing here.

Complicated!

That possibility has crossed my mind, but the picture you posted doesn't allow to clarify the doubt.

In Mission Generator, if we create a new node, assign some Templates to it and immediately try to generate a mission with it nothing is generated. At first I tried with my own Templates, but then I tried with already existing Templates, and nothing is created. However, selecting pre-defined nodes and Generating a mission works perfectly. What do you need me to provide do demonstrate it?

Version 2.8.2.35759. Not yet solved.