Jump to content

SWE-Timberwolf

Members
  • Posts

    140
  • Joined

  • Last visited

1 Follower

About SWE-Timberwolf

  • Birthday 09/03/1978

Personal Information

  • Flight Simulators
    Flaming Cliffs 3
    UH-1H Huey
    Spitfire
    AJS-37 Viggen
    A-10C
    AV-8B Harrier
    M-2000C
    F-5E
    NTTR
  • Location
    Sweden
  • Interests
    Flightsims, movies, reading books
  • Occupation
    IT Technician

Recent Profile Visitors

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

  1. Thank you for this script. So nice that I don't have to try and force the AI to do what it should
  2. Another update: after some more testing it seems it is not a DCS problem at all. It seems it was my cable to my G2 that was causing the issue. I have tested with another cable and it seems to be working as it should now.
  3. Update: My workaround does not fix the problem. It fixes the problem for a few minutes. But every five minutes or so it changes the default audio device in DCS to the loudspeakers instead of the headset
  4. I noticed that a few seconds after takeoff the sound from my Reverb G2 stopped working when I flew the A-10C. Everything just went quiet. But the headphones were still working outside DCS (in spotify for example). I removed all mods and did a slow repair. Then I created a new mission using the caucasus map and used the Su-25T, then I saved the mission and started it. As before a few seconds after takeoff everything went silent. I use open beta and have tested this in both the single and multi thread version with the same results. Next I turned on my external PC speakers but I still had the G2s audio as default in windows. Then I started the test mission again and same as before the sound in the G2s headphones stopped shortly after takeoff, but this time I started to hear the noise from my speakers instead at the same time that the headphones went silent. I then restarted DCS and checked the audio settings inside DCS and changed the audio device from default to the G2, then I tried the mission again. The results were the same as before and the external speakers took over the sound as the sound in the G2 quit. I then went in to the audio settings again and changed the device from the G2 back to default and back to the G2 again. The sound were now back in the G2 headphones. Once I have done that the sound stays in the headphones. So it seems that DCS changes the default audio device for some reason. The workaround I did above seems to solve the problem during the current game session, but I have to go through the same procedure every time I start DCS. I have attached a log and track file. dcs.log No Sound .trk
  5. I started a new topic a few days ago where I experienced CTDs when strating a mission for the Mi-24P. After further testing I realized that this issue was not specific to the Hind, but to quit a few modules. It happens when I run the MT version of DCS in VR. I create a new mission in the editor and place any of the below aircraft on the runway and set the air craft to player. I then save the mission and choose fly. Then a new window appears where I select "Fly", then i get a CTD. I experience the issue with the following modules: AH-64D Mi-24P Mi-8MTV2 KA-50 KA-50 III A-10A C-101CC C-101EB F-15C J-11A L-39C L-39ZA MiG-29A MiG-29G MiG-29S Spitfire Su-25 Su-25T Su-27 Su-33 If I set the aircraft to client instead or if I do not use VR then it works just fine. There are no track file created for this, but I have created a video of the issue:
  6. Thanks for the info Yea, the game crashes before a track file is generated, however I forgot to mention that I did send in a crash report that was generated after the CTD.
  7. Update: I can get around the problem if I set the Mi-24 to client instead of player in the mission editor.
  8. I get a crash to desktop when ever I start a mission in VR in the MT version. It works fine without VR. It also works fin with or without VR in the version without MT. It crashes when I press fly in the mission editor so I do not even see the loading screen and there is no reply file I cam send in. I have tried to remove all mods and the Mi-24 module. I then run a full repair, but that did not help. I had a similar issue before with the FC3 aircrafts, but solved that by removing DCS completely and then re-installing it. Would have been nice to not having to do that again.
  9. Non of the FC3 aircrafts works for me. I'v only tried this in VR, but as soon as I start a mission with an FC3 aircraft I get a black screen and the game stops responding. Works fine if I start DCS without MT.
  10. Yea, I have tried that. Would have been nice though to not have to use the mod and have native support for it instead.
  11. Is there any plans to add native support for Windows Mixed Reality so we that uses for example the HP Reverbe G2 do not have to use Steam VR?
  12. I should also mention that the mission was flown in VR so although I was not always able to see the target menu displayed in my VR headset I do not know if it was displayed on the screen or not.
  13. Here is a track file. However after doing some testing now I got it to work sometimes as you can see in the track file, but the times it does not work might very well be caused by something I do wrong. Also tested with and without setting ACQ to TADS and leaving it at FXD. Link to track file: https://www.dropbox.com/s/xiyi5xdig0u6f90/AH-64D George.trk?dl=0
×
×
  • Create New...