Jump to content

rob10

Members
  • Posts

    3296
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by rob10

  1. Sounds like the logs are pointing that way too, but usually if it's a hard crash with the loud squeal that's a hardware issue rather than a Windows or DCS issue.
  2. Check out the updated Supercarrier manual that was posted earlier today (in the Supercarrier mini-updates thread) and it will answer at least some of those questions.
  3. It still blows my mind how under rated the old 1080 cards were. I moved on from it a while ago, but it always amazed me when people with (theoretically) better cards were complaining about performance a lot worse than I had.
  4. And why do you think they haven't? It wasn't every developer at ED working on fog and/or the new deck crew. People seem to forget that ED tend to do things in the background with only the occasional mention of them until it's baked (or at least baked enough that they're going to put it out). I always go back to the example of multi-threading which a large number of people had wrote off as being abandoned until one day it was added.
  5. NineLine responded to your post in the main thread. The FAQ has what is *currently* planned, maybe the ones you are asking for might be added down the road, but if they were planned they'd have included them in the list in the FAQ. Why would you expect more communication/transparency than that?
  6. Sorry, forgot to get back to respond when I was actually at my gaming computer. The GREEN SCREEN thing is in the Game Peripheral Display tab, when you are in SET MFD DISPLAY option. Typically for that screen issue the fix is in DCS itself. Under the SYSTEM options menu set your RESOLUTION option to WINWING (it will likely be the bottom of the list) rather than any of the other options.
  7. Ouch . That'll be very unfortunate if you can't work around that. I'll 2nd the sentiment that I appreciate the effort 3rd party campaign makers put into their work.
  8. This. Likely something simple you're missing but it's really hard to just guess what it is.
  9. I hope your expectations for any response on this are tempered by the fact that this is less than 80 people total responding on a poll in a thread that's going to self select for a higher percentage of people wanting this. I get you're keen for this, and yes the poll supported it, but only 80 people responding is not even a drop in the bucket of forum users, let alone DCS users so it's not likely to get a lot of traction.
  10. Config/input and under the appropriate aircraft.
  11. RAM requirement has hit a tipping point where 16 GB is barely enough even with a good pagefile since sometime in the summer. There were a bunch of people that started running into issues after an update and the common denominator in a lot of cases was only 16 GB (and mostly a small pagefile).
  12. Post a track. I just tried it from air start and ground start and had no problems with at loadout. Did you mess with the fuzes in the re-arm menu at all?
  13. You're probably better to post a track of that. I used one tonight and hit no problem.
  14. Also worth trying the GREEN SCREEN option in SimAppPro to see exactly where it is exporting your MFD windows to. It should give you clues if the green shading shows up on a different screen or partly off the screen you've turned it on with.
  15. Re-reading it I was reading too much into the OP's post. Basically all they're asking for is to be able to save the download to a different spot which makes sense. When they were talking reading to one while writing to another my brain was thinking something more complex.
  16. You can set ANY plane to red or blue. So just pick the plane you want as aggressor and make it red (if you're blue). Pretty much the same as you're asking for. I could see an argument that you want to take off with it or something before you fight them, but while you're free to request it, I doubt you'll get much traction on getting it implemented.
  17. Unfortunately no option for this that I'm aware of. Has been asked/discussed before.
  18. IIRC (could be wrong, been a while since I did this in the Viper) but did you close and reopen the fuel door? I think you need to do that to reset things in the Viper. Apparently I don't RC. Was the A-10 I was thinking of that you have to do a reset (which closing/opening the door will do)
  19. That's a neat idea, but honestly how much of the update delay is really due to unpacking/checking? I mean that as a legit question because my internet is so painfully slow that it is very much the bottleneck, so maybe it is a significant factor if you have really fast internet. Because while I think it's a neat idea, I'd have to imagine that would take more than a couple of hours of dev time and I'm not sure how much benefit there would be for time spent.
  20. In fairness, if you go back to the post you ended with "I wonder how long this post would last if I posted this on Zambrano's Discord" it definitely comes across as a statement rather than an opinion (especially if you only read that post). May not have been what you intended, but that's how it reads.
  21. rob10

    What next?

    Considering they got slapped by ED for what appeared to be a tease or hint, you're likely going to have to wait for the announcement rather than getting an announcement that an announcement is coming.
  22. Unfortunately a long standing bug that as far as I can remember has never been fixed.
  23. Would be great, but I'm pretty sure you're reading way too much into that. I don't doubt they'll add detail to edges, but ED has already said that PG (and other older maps) was built on a completely technology than that newer maps so they'd pretty much have to start from scratch to add the PG parts to the Iraq map. Or wait for the new "global" map at some point (likely in the longer term, if we're dreaming maybe the medium term) that will cover both areas.
  24. There are none YET. ED has been adjusting the overall dots, but nothing headset specific has been released. The only reason it may look better in the Quest Pro is because it was changed globally and the current version happens to be OK for that headset. Which is exactly why they are working toward headset specific settings (because a global setting clearly doesn't work on all headsets).
×
×
  • Create New...