Jump to content

Brisse

Members
  • Posts

    1180
  • Joined

  • Last visited

Everything posted by Brisse

  1. No, DCS defaults to borderless window, which is just a window without borders that covers the entire screen, but it is not true fullscreen even if it looks like it is. Borderless window forces the frames to go through the windows renderer. Exclusive fullscreen mode bypasses the Windows renderer which means the game and graphics card is in full control of how the frames are presented on your monitor. Everyone that know what they are doing, yes. The benefits are less latency, properly working v-sync, zero discarded frames and thus also better power consumption, less heat, less fan noise etc...
  2. Correct. The sim you are thinking of is Jane's F/A-18. DCS producer Matt Wagner was involved in it's development. You can hear his voice in a lot of places in Jane's F/A-18, just like in DCS :)
  3. Both are real, but the measurements are made at different places. You seem to be running borderless window mode so the pipeline looks roughly like this: 1. The game and graphics card render 130 frames per second. 2. Those frames are received by the Windows renderer because you are not running exclusive fullscreen mode. 3. Windows is always v-synced no matter what your in-game setting is, so it will discard a lot of the frames it receives. The monitor then only receives one frame per v-blank, which is 60fps in your case. This is a really inefficient way to do things. I recommend you run exclusive fullscreen mode instead. Press alt+enter after you have launched DCS to make that happen. This will bypass the windows renderer, so there's nothing in between DCS, the graphics driver, graphics card and the monitor that is interfering. This also means that the v-sync option in DCS settings will work like intended.
  4. I'm fine with small land mass, and I'm fine with fantasy aspects as long as the work effort on the developers is within reason so that they can make it a free addition. It's not because I'm greedy, but free means everyone will have access to it right out of the box which is nice.
  5. There's a place for both I think. We don't have to restrict peoples choices now that DCS supports multiple maps :) I'm sure there are some helicopter-pilots who would love a small but detailed map.
  6. Hello! With 2.0 supporting the ability to add new maps, and carrier ops soon being a more important part of DCS, I think it makes sense to add a map with just open sea. I can't imagine that would take much work effort to implement, right? With little work effort involved, it would make sense if it was released as another free map next to Caucasus. Thoughts?
  7. Yes mattebubben, that would be my dream-map :)
  8. I'm not sure what the size limits are on the terrains but I was hoping for east coast, including Karlskrona (MarinB), Ronneby/Kallinge (F17), possibly F12 at Kalmar even though it was decommissioned 1980, and of course Öland and Gotland. Would be amazing if they could somehow put Kaliningrad and some of the South/East Baltic coastal area in there. I think that would still be slightly smaller than the Caucasus map, so maybe it's optimistic from my side, but I don't think it's impossible. A lot of it is open sea which takes less work to make.
  9. Well, your graphics card is mediocre at best while your CPU is fairly strong so you might never be able to balance out the loads perfectly. I see that you have clutter/brushes maxed out. I'm not sure that's a good idea. It can have a pretty big impact on frame-rate. Try to lower the setting to half, or even turning it off and see how your frame-rate and system loads are affected.
  10. If you have a weak graphics card, or if it doesn't have enough vram, then I definitely recommend lowering MSAA to 2x. It's one of those settings that almost purely affects the GPU, and not the CPU. Considering your CPU-usage is low, you want to lower all the GPU-dependent settings until you are happy with your frame-rate. As your frame-rate increases, your CPU usage will increase as well and your system will end up running in a more balanced state.
  11. The new game engine relies way more on graphics card, and frankly, yours is way below the recommended system requirements: I can imagine this change being annoying for those with older PC's but the old engine wasn't able to use modern PC's to their full potential. The new engine does that much better, and this change was necessary for DCS to move forwards as opposed to being stuck in the past.
  12. Last minute? Haha :) Xbone controller bundle was announced last summer (June) at the same time that the Touch controllers were announced. That's not "last minute".
  13. Before the pre order opened I was very reluctant to buy the DK2. I thought that once the CV1 is out, the DK2 will become worthless. Now that I know the price and how long it will take to get a CV1, I'm thinking that maybe a second hand DK2 is viable anyway, just to get a taste of VR. Question to anyone out there with a DK2: Do you think it's worth getting a DK2 for this reason at this time? I can get a good deal on a second hand DK2. Less than 1/3 of the price that I would have to pay for CV1. What about future support from Oculus? Will it work with future games and runtime releases?
  14. There is no such development priority. The reason it was updated for 2.0 was that ED released a new DLC Campaign for Nevada. We should be really happy that they bundled the M2000 updates in there despite not even mentioning them in the changelog. It is highly likely that the M2000 will get the same (or newer) update in 1.5 next time that is patched, but it's ED that release patches, not Razbam.
  15. BitMaster: Note that the ~100fps numbers are average framerate while playing back a specific track. Look at the max fps, and you see that it even approaches 200fps is some cases. Obviously there's no fps cap involved. I'm absolutely certain that if you played back the same track on your PC, you would see no more than around 100fps average either.
  16. The GTX970 is slightly better for DCS. The R9 390 is slightly faster overall, so if you play other games you might keep that in mind. DCS however is still slightly Nvidia biased even with the new game engine. AMD is a perfectly viable alternative now though. Before the new game engine, DCS was almost unplayable on AMD cards. See this thread for comprehensive analysis: http://forums.eagle.ru/showthread.php?t=157374&highlight=tiborr
  17. Weird. I had no problem hitting Mach 2.2.
  18. Once is enough, unless you alt-tab out of the game, because then you will have to redo alt+enter after going back into the game.
  19. Tried analogue TDC slew with my HOTAS Cougar and it doesn't work. Has anyone gotten it to work?
  20. Really? I'm pretty certain my numbers are right. Are you sure you are at MIL power, and not 85% or something? My numbers are the ones who are closer to the real flight envelope after all, and I didn't even cross check that until after I was done with my graph. Of course. It would be hard to obtain dynamic data for me to use and I didn't mean to do any serious work. It was just meant as a little hint to show Rlaxoxo that what he saw in his fairly unscientific test (drag race!) wasn't completely unreasonable. I just used the gross weight from each DCS manual. Maybe that was reckless of me. Should have fired up the mission editor and fetch my numbers from there using similar configurations. Clean config 100% fuel: M2000-C T/W = 0.89 MiG-21bis T/W = 1.15 (with em AB) So the relative T/W is still similar to my last calculations when I used gross weight from each manual.
  21. 97 kN at full emergency afterburner Source: Mikoyan-Gurevich MiG-21, page 39, By Alexander Mladenov,Adam Tooby Let's do that calculation again :) T/W = 97000/(8725*9.81)= 1.13
  22. Rlaxoxo's results may very well be realistic. I calculated the thrust to weight ratios of both aircraft at gross weight. MiG-21bis 8 725 kg 71 kN static thrust with afterburner T/W = 71000/(8725*9.81)= 0.83 M2000-C 13 800 kg 95.1 kN static thrust with afterburner T/W = 95100/(13800*9.81)= 0.70
×
×
  • Create New...