Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by illern

  1. 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 /illern Ju88fpsdrop.zip
  2. Yes it´s reported. https://forums.eagle.ru/topic/282228-mission-operation-jericho-has-no-loadouts/ /illern
  3. 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
  4. 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
  5. 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
  6. 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.
  7. I have now flown this mission a couple of times and think it need some more TLC to work. /illern
  8. 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.
  9. 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
  10. I often has my AI viggen crash in the campain and from what I can see they are hitting trees when flying over ridges.
  11. 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.
  12. 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
  13. 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.
  14. 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.
  15. 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.
  16. I have looked into this and tried to find whats causing the crash. I can reproduce the crash. For this tests I have set --force_disable_VR to just get the dcs window. But I normally use VR and it crashes with that setting also. Steps I have done: Renamed save game folder so it wants to create a new one. Repaired and removed files with DCS repair function. The only time it shuts down without a crash is when there is no options.lua file.(or if the file is empty) The next time dcs shuts down it will crash if the new options.lua it created the start before is present. I have crashlogs from 2018-12-20 where it has started to crash when shutting down DX11. ****************************************************** From the end of the log: 2020-01-12 15:08:07.061 INFO TERRAIN: lSystem::CleanScenes() 2020-01-12 15:08:07.063 INFO DX11BACKEND: DX11Renderer::shutdown() 2020-01-12 15:08:07.093 INFO EDCORE: try to write dump information 2020-01-12 15:08:07.102 INFO EDCORE: # -------------- 20200112-150807 -------------- 2020-01-12 15:08:07.107 INFO EDCORE: DCS/ (x86_64; Windows NT 10.0.18363) 2020-01-12 15:08:07.113 INFO EDCORE: C:\Spel\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll 2020-01-12 15:08:07.118 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 38067B5B 00:00000000 2020-01-12 15:08:07.124 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\Spel\Eagle Dynamics\DCS World OpenBeta;C:\Spel\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Goran' 2020-01-12 15:08:07.130 INFO EDCORE: OS-Version: 10.0.18363 () 0x100-0x1 2020-01-12 15:08:07.647 INFO EDCORE: 0x0000000000037B5B (dx11backend): RenderAPI::DX11Renderer::interframeResourceSync + 0x1E2BB 2020-01-12 15:08:07.648 INFO EDCORE: 0x0000000000037884 (dx11backend): RenderAPI::DX11Renderer::interframeResourceSync + 0x1DFE4 2020-01-12 15:08:07.648 INFO EDCORE: 0x0000000000013616 (dx11backend): RenderAPI::DX11Renderer::shutdown + 0x336 2020-01-12 15:08:07.648 INFO EDCORE: 0x0000000000055D53 (renderer): render::shutdown + 0x1D3 2020-01-12 15:08:07.648 INFO EDCORE: 0x0000000000034B4C (GraphicsVista): Graphics::Renderer::uninitialize + 0x10C 2020-01-12 15:08:07.649 INFO EDCORE: 0x000000000057020F (DCS): (function-name not available) + 0x0 2020-01-12 15:08:07.649 INFO EDCORE: 0x00000000001C8FF8 (DCS): (function-name not available) + 0x0 2020-01-12 15:08:07.649 INFO EDCORE: 0x000000000073B946 (DCS): (function-name not available) + 0x0 2020-01-12 15:08:07.649 INFO EDCORE: 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 2020-01-12 15:08:07.650 INFO EDCORE: 0x000000000006CED1 (ntdll): RtlUserThreadStart + 0x21 2020-01-12 15:08:07.778 INFO EDCORE: Minidump created. ****************************************************** From the end of the log when it is working: 2020-01-12 15:07:21.078 INFO TERRAIN: lSystem::CleanScenes() 2020-01-12 15:07:21.080 INFO DX11BACKEND: DX11Renderer::shutdown() 2020-01-12 15:07:21.114 INFO DX11BACKEND: NVIDIA API exit OK === Log closed. Attaching the 2 logfiles. I use DCS beta and at the moment I´m on: v2.5.5.41371 Since this started I have changed gfx card from 1080 to 2080ti and numerous nvidia drivers and dcs versions. dcs.log_optionsfile.txt dcs.log_no_optionsfile.txt
  17. In Mission 13 there is a chinook to the left of the F-86 that taxi to rwy 06. P-51 (Relic 2) taxis behind him all the way to the rwy. As soon as the chinook enters the runway the P-51 also does the same thing. The P-51 goes through the chinook and shreds him to pieces with his mighty 4 blade propeller and they end up in a fireball. Changed the mission so that the P-51 started 2 minutes later to let the chinook takeoff and all was fine. DSC v2.5.5.41371 beta Campaign v2.8 -c- Playing as the F-86 /illern
  18. The fuel tanks are not empty after ground crew acknowledge the refuel. It´s just the in cockpit instrument not showing the levels until you have started up the AC and get some generators going. If you look at refuel dialog after the refuel you will see that you have 100% edit: Also since you can hear the fuel going in you can wait for a short while and then start APU and engines while the crew is completing the refuel. /illern
  19. The clock works for me at least. Minutes and hours. The seconds are actually a stopwatch that you can control. /illern
  20. Not sure if this is a F14 or a ED problem since the F14 is the only AC with probe I own. I was wondering why my AI wingmen took so long to refuel all the time. Then I saw this. He was flying as if he was refueling but had the probe to the left of the basket. He does this until the tanker makes a course correction, then he tries to hit the basket again. But can loose it again and start flying to the left of the basket. He is not trying to correct the issue so it looks like he thinks the probe is in the right position. I don´t think he is getting any fuel in this position beacuse it takes forever to refuel his AC. Sorry for the dark picture but I forgot to take a screenshot on the daytime refueling. /illern Open beta version
  21. I use a Saitek X52 Pro system and this is my settings for roll and pitch: DZ: 0 Sat X and Y: 100 Curvature: 15 And for rudder I have pedals for my steering wheel Thrustmaster T500. Pedals are single axis so I set up rudder with 2 axis and set it to slider mode. 1st axis: DZ: 0 Sat X: 100 Sat Y: 50 Curvature: -25 Enable slider 2nd axis: DZ: 0 Sat X: 100 Sat Y: 50 Curvature: -25 Enable slider Enable Invert I think this work really good for me. No need for toe breaks. Just put my combined brake on a slider on the throttle. /illern
  22. It´s a bug. Search forum for channel 10 and you get several posts about it. https://forums.eagle.ru/showthread.php?t=227238&highlight=channel+10 https://forums.eagle.ru/showthread.php?t=199123&highlight=channel+10 Use manual input dials and - radio selector to talk to bases on 10 until fixed. /illern
  23. Ser this post for workaround. Needs to be done after update until fixed. https://forums.eagle.ru/showthread.php?t=227462 /illern
  24. That is what I did in my post. It doesn´t work. They still starts to differ at altitude.
  25. Also tried to find some answers to this a while back in this thread. https://forums.eagle.ru/showthread.php?t=199856 I have also tried to calculate the QFE and QNH. Start at one airport and land on another with a different altitude from sea level. When using different aircraft calculators online I can never get the same result as the aircraft says when I tuchdown on the other airport.
  • Create New...