Jump to content

SignorMagnifico

Members
  • Posts

    217
  • Joined

  • Last visited

Everything posted by SignorMagnifico

  1. Yep. I feel the same way. I don’t see growing pains. I hear a death rattle.
  2. I agree with you. I don’t think Ugra has the right to change their minds a year after the fact. The map was already approved like it was. Ugra, ED, and OnReTech knew about the overlap from DAY ONE. They don’t have the right to bully another third party. OnReTech should have run to ED right away. These disputes SHOULD go through ED and not between the third parties. I also don’t think OnReTech has the right to remove features customers already paid for. This is a violation of the agreement they had with paying customers who already bought the map. Imagine if Hellfires get removed from the Kiowa because another dev has a module that shoots Hellfires and doesn’t like it.
  3. I’m starting to see the picture that it was Ugra who demanded OnReTech to remove parts of the Sinai map people already paid for. Sorry, Ugra, but you don’t just get to change your mind after a year. BOTH of these maps are great. Please get your heads out of the sand and listen to ED’s customers. This really is not the time for third parties to be fighting with each other.
  4. NOT COOL to remove features after we already paid for the product. I hope this is just a bug or an oversight you all can fix.
  5. I also experienced this issue. The gun firing sound on the Sabre sounds like the cannon on the Frogfoot instead of .50 cals. I think a sound file got replaced by mistake in this last patch.
  6. On my end, I seem to have really low FPS once I get close to the ground at airfields. (Tested at Kandahar.) FPS randomly dips into the 20s-30s. Not always, though. Once I get above 500/1000ft, the problem goes away. RTX 3080Ti and i7-14700K. 96GB RAM. DxDiag.txt
  7. Issue has been fixed for me after I rebound my Steam account to my DCS account, transferred the purchases, and redownloaded the modules in question. No issues after that.
  8. I am also experiencing this problem. Why have my purchases been taken from me? I have owned these on Steam since February 2014. Pretty sure this qualifies as a "stopper issue" prior to releasing a patch.
  9. I agree. That's why it's a "minimum" goodwill gesture. It doesn't fix the issue at hand until development resumes and all RAZBAM's products are completed.
  10. If ED is committed to selling the product, they are committed to supporting it, in my book. ED should be responsible for updates and maintenance on RAZBAM’s modules if RAZBAM can’t continue development. ED can show me they care about their customers by fixing all the outstanding bugs, at a minimum.
  11. Does this mean that you have the source code?
  12. That one is still receiving updates. Check the changelog for the last DCS World update. The team responsible for the terrain is a different unit than the aviation team.
  13. This situation is unacceptable. Eagle Dynamics should have contingencies in place for this. Neither side should be holding us hostage. If RAZBAM is unable to update the module because they haven’t been paid, ED should be the ones updating it. The Streagle hasn’t even been out for a year, and it’s already a dead module with no radar. If this continues, we’ll lose three more.
  14. This is correct. The South Atlantic updates are handled by another team (not the aviation one), so this is not news one way or the other. The status quo with RAZBAM's aircraft modules remains unchanged.
  15. Fare thee well. Safe journey.
  16. If RAZBAM bows out and goes bankrupt, I expect to be refunded what I paid. I’ll take store credit if that’s the only way. Not about to ask for a refund, yet, though, because ultimately what I want is to play those modules. Store credit doesn’t give me a full fidelity Strike Eagle I waited years to play. Store credit doesn’t give me back the Harrier, MiG-19, or Mirage I bought in good faith that my purchases would be supported as long as DCS World exists. Please, ED, if you’re reading this, find some compromise to let RAZBAM continue development while you negotiate or find some way to fix the bugs yourselves. It’s unfair for either side to let customers sit with a broken product while there is a dispute. Show us we can still trust this company with our investments. As for me, this situation has broken my trust in both parties.
  17. When typing in coordinates manually using lat/long on the Jester menu, if I accidentally click lat/long again without typing any numbers after the cursor is visible, the game crashes immediately. Happens every time. Log attached. dcs.log dcs.log-20240601-070309.zip
  18. Thank you, Heatblur, for setting the bar again when it comes to DCS modules.
  19. Is this issue fixed in the upcoming patch?
  20. No, I can’t be heard at all. Fails at the test and in-game comms.
  21. Update: Tried changing around the settings again to see what is causing the issue. The microphone test is now working with the following settings without needing to use Nvidia Broadcast as the microphone audio source. I can use the microphone input directly from my sound card. To fix this, I had to lower the microphone sample rate to 48000Hz. I also cannot set headphones to be the same audio output as the main audio out on my sound card. DCS main audio out through my sound card works fine. The root cause of DCS not detecting my microphone appears to be that DCS cannot handle audio input exceeding 48000Hz. My sound card supports up to 32Bit 96Khz on the microphone input and audio output.
  22. I had the same issue on my end with a PCIe sound card. Had to use RTX voice as a workaround, but if I do that, my frame rate tanks when using Shadowplay. I don't know why DCS Voice Chat has such a hard time with audio inputs when every other program I use, including SRS, works fine.
×
×
  • Create New...