Jump to content

rob10

Members
  • Posts

    3332
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by rob10

  1. Fair enough, maybe it was December that last was last update. I was more thinking they've had at least a couple of updates since Razbam have announced they weren't doing any more. Maps typically don't get the frequency of update that other modules do. They have stated before it's not an issue and the fact that they have updated it long after Razbam stopped doing any updates is a pretty good indicator.
  2. Yes. IIRC more than one.
  3. ANY mods have potential to interfere in weird ways with any part of DCS (it happens all the time that seemingly unrelated mods break things -- at one point a (non-naval) plane mod caused the supercarrier to not show up). Worth removing all the mods to see if that fixes the issue. And if just removing them doesn't work, I'd try a slow repair after they're removed to see if that fixes it.
  4. Please post a (short as possible and preferably on Caucus map) track file. You can save a track file from the debriefing window when you close the mission. That will allow people to check that you're not missing a step somewhere or reproduce the bug. ED devs also have additional tools that allows them to use a trackfile for more deeper debugging.
  5. That file no long does anything since the DTC was introduced. See this thread:
  6. I would think the BYPASS mode is using more the JETTISON logic/mechanism rather than the actual ALE-47. I assume it's a backup system since CM's are pretty critical. So I can't imagine you'd ever use it to test function. And for same reason I doubt the ALE-47 is "on" when using it (again, if it's broken you probably don't want to power it but you may need CM's still. Also, with a DTC, it's pretty simple to set up whatever program you need for your flight so it really doesn't require doing anything. I also have no actual knowledge of it, but that's what my logic on it would be.
  7. Try physically moving to your left, then looking over your right shoulder. Sounds like TIR is starting to lose signal. Might not be enough that it's obvious in the dots in the interface, but when a small movement starts moving the whole screen you notice it. My TIR LED's are on my right side, so I have my camera on the right side of my monitor (rather than middle) to give it a wider FOV toward the LED's).
  8. Personal preference. If it's going to have a DTC it doesn't take much to press the button in the MUMI page (Hornet anyway) to load it. I'm not hardcore enough to do all the tests (ie voices) but that would feel wrong not to do the DTC.
  9. In this case, there was a substantial Germany update and IIRC recently also big Kola and Sinai updates (not sure if they'd have been since you last updated) but very plausible with maps that it could be 149 GB. Fortunately most of that will replace existing, so you shouldn't need fully that much more space on your drive.
  10. And NOT using the Comms menu is currently where the problem lies. Although I have seen at least one report that Case 3 still crashes, but as long as you call at least inbound you shouldn't CTD.
  11. Agree it would be good that you should be able to create a default DTC that will be loaded if you don't pick another one. Also agree with it being loaded on hot start. But I don't think it should be automatically loaded for cold starts.
  12. You're using the EASY COMM's binding and REALISTIC COMM's is enabled in the mission. You need to use "Transmit Switch - UHF (call radio menu" (or the VHF version) rather than "Communications Menu". Works fine when you do that. You should get UHF Radio AN/ARC-164 above the radio menu that pops up. When you're using the Communications Menu binding you won't get that.
  13. Post a track. This isn't reported widespread and clearly isn't an edge case usage so likely it's something specific to your case. Without a track it's wild guesses that you're going to get.
  14. No idea. When I was testing it was just me. My guess would be at least the lead for each flight, but possibly each aircraft.
  15. As long as you call inbound to the carrier it's not broken. If you don't, then yes you can get a CTD on landing with current build. And that's why the "5 minutes" of testing probably didn't catch this. I automatically called in when I was testing after seeing reports of this and I had no problem landing. Until someone figured out this was cause I couldn't recreate it. Once I stopped calling in then I could reproduce it.
  16. So you want a refund from ED through Steam. OK, lets say Steam takes a 30% cut (no idea if that's the actual amount, but that seems to be what general consensus is) on every sale. So ED is already out 30% on what you paid. Now you want (presumably) 100% back. I'd pretty much guarantee Steam isn't going to cover the 30%. So now ED got 30% less for your original purchase in the first place AND has to pay you back a 30% premium (since Steam isn't going to cover that). So for easy math let's say you paid $100. ED got $70. So it's flat out costing them at least $30 more for every refund the authorize through Steam, and the whole $100 is coming out of their pocket. Like it or not, with the store credit they are offering ED store customers they still have the $100, it's just being moved around. So trying to claim a "fairness" argument since they are giving ED store customers credit doesn't work. Even if ED was giving full cash refunds, they'd still be paying an extra $30 to Steam users so where's the fairness even there?
  17. Not sure this will solve it for the Harrier, but if you call inbound to carrier it will fix it at least for the SC and other aircraft. Essex was also having issues and not sure if it's the same or a different issue.
  18. Contact the carrier prior to landing should fix it (even if you just call inbound and don't do full comms). If you abort inbound it will crash too.
  19. For the record for anyone who comes across this thread in the future, the solution was to TURN OFF Force Feedback in the settings.
  20. Yes, it should be in that new path. HOWEVER, make sure you are going to COREMODS rather than MODS as the start of the chain you're looking at (World/COREMODS/aircraft/FA-18C/DTC/ALR67/CMDS_defs.lua rather than World/MODS/aircraft/....) and it should be there. It is formatted slightly differently in the file, but pretty easy to figure out. ALSO NOTE, you need to create a custom DTC file in the DTC manager to get this file to be created IIRC (you don't need to use the one you created, but it will create the default one you're going to want to edit). And your changes in the default file will need to be redone after each update.
  21. Removal of the old pod is up in the air and being discussed right now and your question is one of the reasons why. ED a while ago backed off on immediate replacement of the old one with the new and it appears they are going to leave it for backward compatibility. It may or may not get and update to make it more realistic (i.e. less effective than it currently is).
  22. Why are people SOOOOO resistant to posting a track? It's the easiest thing you can do and often shows some simple step that's not mentioned in the written description that is causing the issue and saves so much time guessing what's actually going on for people trying to help. In your original post you mentioned both the button and the keybind not working which suggested a procedural error (in fact you even said "Am I missing something stupid?"). A track would help diagnose what you missed or help ruling out a procedural error. Now mentioned if you plug (presumably the old hardware) back in it works fine. Which suggests a possible hardware issue. Good luck figuring it out.
  23. As I said in the other subforum where you posted this, ADD A TRACKFILE. That will narrow down what you could be doing wrong. Currently it's a complete guessing game.
  24. Which carrier (Essex carrier has a problem with all users currently and is acknowledged) and are you using Tobi eyetracking (which currently is causing an issue with all carriers, which is reported, but not sure if it's acknowledged)
  25. It's not a "problem with the external drive" per se, it's the fact that it IS an external drive which is almost always going to mean it is (much) slow transferring data to your motherboard.
×
×
  • Create New...