Jump to content

rob10

Members
  • Posts

    3320
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by rob10

  1. Set your GUI scaling to 1X.
  2. Your log file looks very similar to the one I commented on here.
  3. That's what that option did in game. How do you do it otherwise? I used 1.5X as well and I'd like to get my sizing back.
  4. Set your GUI scaling to 1X in the settings. Apparently only an issue if you have the supercarrier in the mission.
  5. Thanks. I knew I had flown a couple things yesterday afternoon and hadn't seen the issue, then flying last night I had it and I couldn't figure out why. But this would explain it!
  6. Set your GUI scaling in setting to 1X and you'll get things back to normal.
  7. Because for most people (obviously not all as evidenced in this thread, but most) they don't have the problem you're seeing. In a perfect world it would get caught but there are so many possible systems and configuration that there is no way to catch every possible issue. And if it does get caught but only effects 0.1% of users it might not be considered serious enough to stop a patch fully.
  8. Couple of things: you really need to try and get more RAM. 16 GB physical and 20 GB pagefile is very marginal and it looks like you're using a bunch of mods which likely won't help. Personally I think DCS realistically wants a minimum of 64 GB between RAM and pagefile and obviously the more of that that comes from RAM the better (speed wise). Check your anti-virus. There is a Access Violation crash which another user found was due to antivirus quarantining a file. You can also check this thread (and I know there are a few more with same Access Violation crashes):
  9. And check that your AV doesn't have the files quarantined. I would have thought reinstalling with AV off would replace it, but it might be causing issues if it's already quarantined. And if you're turning AV on before you run it, then it will still be nuking those files (it's generally detecting them, not really related to detection during installation).
  10. Set your GUI scaling back to 1 and you should be back to normal.
  11. Literally that the unit is tilted and by how much. The 2nd number in brackets is the MAX allowed angle and if either of the 1st numbers are higher than the 2nd numbers you'll get this. Mainly meant for SAM's etc that need to be relatively level to be able to function.
  12. Check your anti-virus. Quite possible that a file or two has been quarantined so is unavailable to DCS. It may have removed them before you excluded DCS.
  13. ST is not fully unsupported yet, but it is being phased out (ED has indicated this for >6 months now) so support is more limited. Honestly I think ED were planning to have it gone by now but they're having issues with some newer systems choking on MT so they haven't fully depreciated ST yet while they continue to work on that issue. Unfortunately I doubt there is anything you can do to fix it on your end short of running MT (this is a known and reported issue in ST). Otherwise your hoping for ED to decide it's worth the effort to fix it in ST.
  14. While the rest of your points may hold, it clearly was intentional to remove it currently. To quote directly from ORT's post: "Yes, this part of the map was removed from the build intentionally."
  15. Just to point out that NineLine has clarified that it was SPECULATION on his behalf that this was the reason for removal. So don't use that post in your consideration of why. If it was Urga, then a pox on them along with ORT and Urga should announce that fact it they weren't involved because they're getting mud on their reputation by default currently. Since ORT didn't name or imply who the 3rd party was, it's possible (as was suggested by another poster) that this is a licensing issue with ORT and wherever they got their base data from. Either way doesn't matter because ORT is deservedly taking a hit for the way they've handled this, but I'm holding off judgement on Urga until we know the details.
  16. In fairness, we don't know Urga has anything to do with this. NineLine speculated that it was about stepping on a third parties toes (i.e. Urga), but the ORT post doesn't imply that. As another poster suggested, this could be about licensing with wherever ORT got their base data from. That's very plausible since the chopped area follows a major lat/long grid line (logical spot for licensing to stop) and apparently doesn't really match up with where Syria goes to. Either way, the end result looks bad on ORT and more so that it wasn't announced ahead of time or even in the changelog.
  17. When I finally got done downloading the update I did get the prompt to restart system or cancel.
  18. Check your anti-virus. High likelihood that it has quarantined a file or two from the F-15.
  19. No, but yes on needing to enable . It is default now, but depends what shortcuts you're using (and if you're in Steam that's a whole different complication). Easiest thing is check that is says Multithread preview before version name on the main screen. If it does you're good to go. Otherwise you might need to update your shortcuts. If you were installing from scratch it would set them up default as MT. If you previously were using MT you should be good. If you previously had been using ST you'll likely need to update. And Steam you're more likely to need to change things (I don't use it, so I can't give you good directions on it).
  20. First off: I really liked the Sinai map we've had for the last year and it's been one of my favs despite the fact that it has some issues. And while it was annoying, I was willing to accept the really long wait for the update because I had faith that there would be a lot of updates/fixes included. Unfortunately, it seems they have taken that time to build new objects/eyecandy etc (which is great, no one is going to complain they exist), but haven't bothered to spend time fixing the basic items that make so much more difference to actually flying (i.e. navaids, bridges) and would have improved the map much more than the new objects/airports. Given the time that was being taken, it was my expectation that this polishing was what was going on, but apparently I was wrong in that assumption. I don't know the reasons for pulling part of the detailed Isreal area (a dispute with Urga or licensing issue with another outside party on base data are both plausible) but ORT has seriously damaged it's reputation by taking a year to put out a patch which was mostly added eye candy with very little fixing AND THEN not informing your customers you were removing part of the map (more so if ORT was already planning that this was only going to be a temporary removal). I might not have liked it, but it wouldn't have hurt your reputation with me if you'd been up front. I'm willing to see things from both sides and understand what I want might not be what's going to happen for legitimate reasons, but in this case you've moved me from a "promoter" and "defender" of this map to an unhappy customer. I no longer have faith that ORT is going to fix/improve the little things that have so much more impact day to day than "fancy new eye candy".
  21. No. At some point ED will likely clean things up in a patch, but it will work fine under the old Open Beta structure until then.
  22. Seriously? This was a really poor decision to remove part of the map (whoever was responsible) but to claim "hiding threads through merging to avoid bad publicity" is a bit much. ED regularly merges threads so stuff stays together rather than having a responses spread everywhere. Controversial subject or not. It makes sense to do so.
  23. Since the patch notes have this in the "KNOWN ISSUES" section I would say yes: "Known issue: Performance drop in some populated multiplayer servers when the “Select Role” window is displayed. We’ve determined several optimization steps we are working on currently."
  24. Shouldn't happen, but this doesn't seem to be majority of users that are losing settings. Not sure what causes you to have the issue (and it sucks that you do), but since it's not a common issue it's going to be challenging to fix it.
  25. I'm still hours away from download finishing, and it's good that they did mention that in the changelog, but from the posts it sounds like it DIDN'T prompt (just restarted) and while I tend to be pretty good at reading things (OK, maybe I overestimate how much I just skim ) I totally missed that. It really should actually PROMPT if it doesn't.
×
×
  • Create New...