Jump to content

jules9393

Members
  • Posts

    23
  • Joined

  • Last visited

About jules9393

  • Birthday 12/04/2020

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have had the same issue of late and that's with all comms options bound to my hotas and in different modules. It only opens with easy comms selected.
  2. After recording tracks from Reflected's Wolfpack Campaign and playing them back I have noticed an interesting affect. If I watch the track back the from the default position of the cockpit, the events of what was recorded unfold, the wingmen start to roll and take off. If I watch the track from the start from the F2 external view, the wingmen do not roll or take off. From my understanding the track replay system is a recording of inputs made at the time that a mission was played. So how can it be that inputs post mission can change what is supposed to only be a recording? I can understand this if one was entering the replay as a mission, but I am not. There is something seriously wrong here and the recording is not a recording.
  3. I joined the Windows insider program and it's that version of Win 11 that I am using, not the other that is floating about. Windows 11 has installed as an upgrade/features update rather than a clean install and that suited me. The reason for going that route is that I could not for love nor money get the June cumulative update to install and I wanted to see if SLI now worked with DCS 2.7. The drivers and settings were the same as before as with Win 10. As for being able to give you a figure of increased fps I cant, as the counter in DCS is no longer there, so my experience is based purely on eye test and feel. As soon as I have time to sort one out I'll let you know. It's early days but so far DCS seems to work and it seems smoother, which leads me to believe there is a performance increase under Win 11.
  4. I have been having the same problem since 2.7, I have even tried it with Win 11 just to see, but the same result. I have found though Win 11 gave me better performance when not using SLI than Win 10. Also with 2.5 I found that my best results using SLI was selecting, SLI compatibility Bits 0x04400005 (S.T.A.L.K.E.R.: Clear Sky, Rise of Flight, S.T.A.L.K.E.R.: Call of Pripyat, S.T.A.L.K.E.R.: Shadow of Chernobyl, IL-2: Sturmovik: Battle of Stalingrad) and SLI Compatibility Bits (DX 10 + DX 11) 0x000000F5 (The Talos Principle, Nurien-Mstar, DX SDK DetailTessellation11 sample, PC Building Simulator, etc. Nothing works now though and I hope this gets sorted.
  5. I have just been flying mission 5 of Horrido which features low cloud and as soon as combat starts against the bombers the flashes and general light show on the clouds is the worst I have ever seen it. I have never experienced this in any of the other software that I use.
  6. Just for the record I don't have Gsync either.
  7. Something has definitely changed for the engine with this last update because now my engine blows just on taking off in mission 2 of 'Horrido' with drop tank and rockets loaded and I have never experienced that before.
  8. I too am also experiencing the flashes on both the Channel Map and Normandy, it happens in Horrido during action and also in the Blue Noses campaign, Horrido is the worst though . I am using an RTX 2080 super have tried about 6 sets of different drivers including the studio ones and it makes no difference, neither does emptying the cache. I can't say for the other maps as I have not flown them in a while, but when I do I will let you know.
  9. Hi, thanks for the reply. I'm sorry to say that I had already done both of those things during my bouts of testing. Hopefully this will be fixed in one of the upcoming updates, or even when DCS changes to this new form of graphic system that they supposedly have planned.
  10. Sorry had to attach the log here. Cheers. dcs.txt
  11. Hi, here's my specs and log. Have just tried the same mission with FW190 A8 and BF109 substituting one for the other and flown by the AI. For what it's worth it does it in the latest Beta too, only worse, but maybe one might expect that. Intel Core i7 9700K 3.6GHz Octa Core LGA1151 CPU Corsair 163301 Vengeance LPX 32 GB (2 x 16 GB) DDR4 3200 MHz C16 XMP 2.0 Thrustmaster Hotas Warthog Joystick and Throttle Saitek Cessna Rudder Pedals Track IR 5 Win10 Pro 1909 18363.752 ROG Strix Z390-E Gaming Not overclocked and turbo off. Crucial MX500 CT1000MX500SSD1(Z) 1 TB (3D NAND, SATA, 2.5 Inch, Internal SSD) GTX 1080 Good luck to you all and stay safe, all the best, cheers.
  12. I second that and have experienced the same problem.
  13. Has anybody else noticed that the A 8 seems to suffer from stutters more than the 109, P 51 and the Spitfire on the Normandy Map in the DCS stable version 2.5.5? It is even more apparent when carrying a bomb. I have tested this against all the above aircraft, within the same mission and as well setting the AI to fly the plane and or planes. I have searched for other posts on this topic and have found none.
  14. I am currently still experiencing broken track replays with the Viggen. On a taxi to the runway it demonstrates a mind of it's own by running into the sand, or not even leaving it's parking lot etc...
×
×
  • Create New...