Jump to content

MRW

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by MRW

  1. I've done a fresh install, messed around with some ingame and nvidia settings, other maps work pretty good now, on Syria the fps shown by DCS is ok righ now, at least most of the time it stayesbetween 35-50fps, in more populated areas it doeas go down do 20 even, RAM is used a bit less, but the difference is 95-97% instead of 100% and there is visible annoying stuttering. Difference in memory usage is huge between this and the other maps. 32gb of RAM are stated as recommended, but for now it looks like definately not enough.
  2. On the Syria map I kind of know what you are talking about and I also get the filling like it is shimmering and there is quite a lot jagged edges, maybe thats because it seems to detailed really nicely. Done some tests, and MSAA x4 is definately working for me, but not sure if it's working as well as before the update? Can't tell really.
  3. Done a couple of simple checks, and before the update that introduced the Syria map in the Caucasus map and Persian Gulf I had framerates that were good enough for me, anywhere between 45-75fps. Caucasus with just 3 or 4 units on the map is using around 12-14gb of RAM in game and a little bit less in the editor. Persian Gulf with about 15-20 units was at 16-17gb of RAM ingame and again, a bit less in the editor. So I was basically running them no problem from the editor, in singleplayer or in multiplayer, never had any problems. Right now, after playing missions on these maps from the editor or from a 'mission' start, I am getting a little stutter every second and the frame rates seem to be a bit lower. Now with Syria, just a single F-16(me) and nothing else, it is taking around 20gb in the editor, and basically everything else up to 100% RAM use while in game which translates to lower framerates, and much more visible stuttering every 2 or 3 seconds. Many times while in F10 map the and zooming in the game will just take a 3-5 second break and while zooming the view in cockpit to take a closer look on the ground it's the same thing, which seems to be logical having no memory left. Not only annoying but also unplayable. I tried changing graphics settings but nothing help. Made a uch bigger page file and also nothing. Drivers are up to date and it's running from an SSD. Specs: i7 6700k @ 4,3Ghz 32GB RAM GTX 1070 Also attached in game settings.
  4. Yeah so, If you let's say put down an F-16 in the editor, and you take control of it you can easily rearm (haven't tried refueling, because I always started with full fuel), then you go up in the air, and after some time of flying if you land and want to rearm and refuel, the refueling part get stuck at some more or less random percentage and you can hear the refueling going on indefinately (I think I once left it on and went afk for almost an hour, it still didn't finish). Only when you start up the aircraft the refuleing gets done and you get rearmed, so that might be a little bug. BUT, if you do as Bouli306 said, request rearm and refuel with the power switch in battery or main power, and I think leave it on (don't remember right now), it get refueled in what i assume the correct amount of time easily. I don't know if it was meant to be like that but that is how it seems to work now. I don't have a track but it should be fairly simple to reconstruct on your own.
×
×
  • Create New...