Jump to content

NightMan

Members
  • Posts

    208
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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
  4. 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.
  5. 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.
  6. Is this cross in center of the screen related to tha April Fool's Easter Egg too?
  7. 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
  8. 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.
  9. This appears to have been corrected in version 2.8.3.38090.
  10. 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.
  11. 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.
  12. It appears to have been corrected in version 2.8.3.38090.
×
×
  • Create New...