illern

Hello! As soon as I look at a JU-88 bomber formation i´m going from stable 45fps to massive slideshow at 19fps. It doesn´t happen with B-17 or the A-20. It doesn´t matter if I´m a friend or a foe, using Mosquito or P-51D(only ones I tried so far). I´m flying in VR, se specs in sig and attached dxdiag. Attaching a small track with a P-51D in between 2 formation of bombers. 1 JU-88 and 1 B-17. The same amount of bombers in both formations. In this track I´m red as the JU-88, as soon as the JU-88:s are in view the FPS drops to 19-20fps. Ver: Open Beta 2.7.6.13436 /illern Ju88fpsdrop.zip

Yes it´s reported. https://forums.eagle.ru/topic/282228-mission-operation-jericho-has-no-loadouts/ /illern

Hi! In the briefing image of the prison where it says to bomb East wall the arrows pointing to no 3 east wall is actually pointing to the west wall. Likewise the no 1 and 2 also point to wrong wall. Se attached image. /illern

Hi. In the mission operation jericho none of the flights has any loadouts at the start. Flew the mission and no one bombed the prison including me. Checked the mission in mission editor and all planes are empty. /illern

I have a HOTAS Warthog and I use the "High-Pressure Fuel Valve Off/Idle" bound to throttle off. The one you have to lift the throttle to closed position to activate. That button is inverted. Press to Off and release to Idle. Do you really need two buttons? If you only use one and choose On/Off (Toggle)? It was (throttle to idle) that was for one button, toggle was for a switch that stays in on or off position. Then it is first press to Idle and second press to off. So now I have tested all variants of High-pressure Fuel Valve Off/Idle = For HOTAS throttle closed pos. Press = Off, Release = Idle On/Off (toggle) = Stable switch that stays in on or off position. Switch on = Idle, Switch off = Off (For HOTAS, Off is pressed) = Not bindable. (HOTAS Cut off) = Works the same as Off/Idle (throttle to idle) = First press = Idle, Second press = Off

After watching the F-18 take off from the carrier and the voice briefing is over you end the mission and just start the next one from the campaign menu like normal. Then the flyable mission 1 will start. Edit: sorry, didn´t realise you had answered your own question.

I have now flown this mission a couple of times and think it need some more TLC to work. /illern

This aircraft will be a pain in the neck when flying in VR with all the low and back panels. You will have to break the neck and the back I think to see and interact with a lot of switches, specially those on the left side.

Hi! Have been trying to fly the single mission "Atlantic Wall Raid - Bomber Escort" but it is not possible to fly due to some criticial mission bugs. The mission fails from the start and is not able to start correctly. The first flight "Red flight" is supposed to start and takeoff immidiately on mission start. This is what triggers the rest of the mission. But the do not move an inch from their parking slot. I have found the issue with this. It is all the tire flags that mark the path to the runway and also the wind flag next to the tires. Thay are in the taxi path of the AI so they won´t move because the path is not clear. If I remove all the tires and the wind flag then the mission starts. The AI cuts the corner onto the field. A second minor bug is the trigger "2FU" that makes my AI wingman call in formation on starboard gets triggered on the ground after the timer of 300s has elapsed. This trigger should have another condition to it. For example AI Wingman 200ft above ground to make sure it gets triggered in the air. When we are on the ramp the AI wingman is already in my moving zone so as soon as the timer expires the message gets triggered. Don´t know if there is anything more wrong with the mission, since I haven´t had time to test it any further due to time spent looking for the error. /illern

I often has my AI viggen crash in the campain and from what I can see they are hitting trees when flying over ridges.

What happens is when the F5 extends the nosewheel strut it won´t raise the aircraft but instead the nosewheel gets buried in the tarmac and then he is not able to steer anymore.

I don´t know if this is the same issue. The iranian strike group did shot first. After that I told Knight "Tiger" and got sent for a new group that was inbound. I had trouble finding that group and when I eventually did they were just cruising along to the east inside iranian airspace. 2 F14. I went after them and shot them down with my gun. The didn´t even flinch. Just continued to cruise along although they were attacked. All communication ceased after knight sent me towards them. No F10 menu either. Went home and landed on carrier and got result 50. /illern

That´s how it´s supposed to work. Like any other DCS module. Communication menu is only for ground if you don´t have Easy communications on. In air you need to use correct radio PTT button. Ralt + \ for P-47 I think.

Noticed the same today when flying the mission "Top cover". At the time the B-17 are at the target my oxygen ran out. I had the oxygen regulator in Normal mode.

Well I have sound and that error is in both log files. Both the one when closing DCS is working and the one where it is crashing when closing. As I described above, I have done cleanup and repair. The game is working for me, it´s just the crash when I exit the game and filling upp my savegame folder with crash and dmp files. About the sound, I haven´t noticed that earlier. But in Audio tab in settings I only have Default listed in all sound and recording devices. But the sound is coming where I want it. Checked some old logs and in 2018 with my old computer it was the same: 2018-08-12 15:47:02.706 INFO SOUND: Using driver: xaudio29 2018-08-12 15:47:04.725 ERROR SOUND: FindAllAsyncDeviceClass has timed out with: 258 2018-08-12 15:47:04.725 INFO SOUND: Found 0 available audio device(s): 2018-08-12 15:47:04.901 INFO SOUND: loaded 1308 sdefs from "sounds\sdef" And in 2017 almost the same: 00001.320 INFO SOUND: loaded 1231 sdefs from "sounds\sdef" 00001.514 INFO SOUND: Using driver: xaudio29 00001.535 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 00003.550 ERROR SOUND: FindAllAsyncDeviceClass has timed out with: 258 00003.550 INFO SOUND: Found 0 available audio device(s): 00003.551 INFO SOUND: Using SSE FTZ/DAZ mode.