Jump to content

Antiguedad

Members
  • Posts

    64
  • Joined

  • Last visited

Everything posted by Antiguedad

  1. I'm just starting the campaign, it seems very good. But IMO some of the voice recordings have too much gain, and they have been recorded too close to the micro, that causes little distorted sound and lots of plosives like p's, b's, c's and so, for example in Blakeslee's voice. I's just a personal and constructive advice for the next campaign.
  2. When I kill last enemy unit from the convoy the mission ends with message: "Mission failed, enemy convoy has reached the city" . It's impossible that convoy reaches the city because there are no convoy units remain... Have anyone had this issue? Sorry, have no track. Openbeta multithread preview last version. EDIT: I've been checking the mission in mission editor. It seems you are referring to flag 555 that has been not defined earlier in the condition to mission fail. I've changed flags from three lines of code and mission now seems to work: trigger "fail tgt1": 556 to 554 trigger "FAIL1": 555 to 554 trigger "rtb18": 555 to 556 Mi-24 Revanche02_corregida.miz
  3. Meanwhile, something similar can be done with process lasso, setting DCS affinity only to the P-Cores and other less demanding but interfering process (opentrack, etc.) to the E-cores. Also you can remove hyperthreading for older games like Arma 3 setting affinity to the even cores (0, 2, 4, 6, etc.). It also prevents core parking without disabling C-states in bios. It's the poor-man version of Intel APO but works very well.
  4. Same problem here with Focusrite Scarlett Solo, mic crackling and DCS crash.
  5. Same here, I think VOX and Hot Mic don't work, only PTT.
  6. Msi afterburner or similar programs that periodically monitorices cpu/gpu parameters usually cause stutters. Try disabling it if using.
  7. Same, just bought it, love the Gazelle but rotor is kinda crappy.
  8. It was meant for @adirtynurse with DLSS, sorry.
  9. @adirtynurse try enabling HAGS if disabled.
  10. I've also had issues with 2-3 latest nVidia drivers releases, such as game crashes, hard crashes and a random checkerboard pattern in Chromium based browsers (Edge, Google Chrome) as you can see in nVidia forums. Last one stable for me was 536.99 Studio Drivers from 8-8-2023. Try this: NVIDIA Studio Driver | 536.99 | Windows 10 64-bit, Windows 11 | NVIDIA and see if DCS is stable with it.
  11. Even with low-minimum settings Syria and F1 are very CPU-GPU-VRAM hungry. With 16GB RAM, a 2 cores/4 threads i7-3770 and specially only 4GB of video ram it's normal that framerates get very low when the VRAM gets full.
  12. There are three separate things here, maybe: 1) Campaign taking off with 105% weight which is a little challenge but doable. 2) A discrete error with mission 3 loadout overweight. 3) A possible general DCS bug with choppers taking off from farps and crosswind.
  13. Try mapping it to a key of the keyboard, just to be completely sure. Edit: Sensor Select Left = LShift+Y
  14. When you use markpoints the steering for the first one (MK0) wont work. Steering for the other ones works fine. You can check this by creating several markpoints (Mk0, Mk1, Mk2, etc.) in different locations, cycling though them with the waypoint increment button, and looking at the steer arrow (internal one) in the HSI. The steering direction between the last one you created and the MK0 wont change. Thanks.
  15. No, there is not any other prerrequisite. I think maybe it's a false contact in your stick that prevents a continous long press. I had the same problem, in my case with a X52, and I solved it by opening it and cleaning the left direction of the POV hat contacts with alcohol.
  16. At mission start you have to use f10 menu to ask for permission to both start engines and take off in order to the other mission triggers to work, maybe?
  17. I think AI chopper crashes from FARPS was a general DCS bug with crosswinds, so it's not a campaign error, though in some mission maybe there is a puntual error with starting load. Sorry, it was not your fault.
  18. @Flappie, crosswind + taking off from FARPS also causes crashes with Mi-24P (in the store campaign, for example) and other AI choppers, not only CH-47.
  19. Main problem is with AI wingman. For example, in mission 10 player has S-8KOM HEAT/frag rockets and no problem taking off with 101% weight, but wingman has S-8OFP2 MPP rockets, which are heavier, and AI struggles taking off with 105% weight (maybe I'm wrong). Please revise loadout (rocket type) and weight, as I said, your campaign is very good.
  20. In several missions wingman chopper is unable to take off and continue flight plan due to the excessive take off weight. Also in a couple of missions I had to call ground crew to reduce my own's chopper weight. The campaign is fun to play but these details break immersion a little, please revise initial take off weights.
  21. I've had several similar crashes, in my case with JF-17, it happens only with russian speech.
  22. I think this repeated crashes happen only with russian voices, BTW. I've had them several times, and always with russian speech.
  23. I've done it and no files were modified. I think it's maybe related with the changes in DCS sound file structure and other similar crashes reported earlier.
×
×
  • Create New...