Jinker

Just for your info (no rift in these tests): http://forums.eagle.ru/showthread.php?t=159284

Well, yeah... As I wrote in my first post, I was trying to push my system. I normally fly with no clutter, anisotropic filtering at 4x, shadows flat only. This way I get 50-150 FPS all the time (with occasional stuttering) and I can't really complain about the visuals. I'm gonna just swallow this, given that a new graphic card is out of budget for the moment :wassat:

Thanks Brisse, this is the kind of hint I was looking for. Unfortunately, it seems that the MSAA does not have the effect you suggest. Still, it looks like DCS "forgets" the CPU available capacity. @Mustang: the attached log is done with ClockBlocker active. The GPU seems far more unstable than without this tool (just compare to the log of my first post)

Hi there! I've been so far very happy with DCS 1.5.2 performance on my mid-end PC, and I lately tried to push it a bit... The eye candy is still important for me :prop: So, I was definitely surprised to see that DCS does NOT really squeeze my system, with the exception of the GPU. Scenario: I launch DCS, load the FC3 instant action A-10A CAS, at mission start I turn left 90° (turning on the mavericks), fly over the hill, the towns, the forest, the sea and eventually turn 180° to fly again above ground at a higher altitude. Output: FPS ranging from 30 to 70; continuous micro-stutter when looking down or to the side; major stutter when changing quickly viewing direction or zooming. From the attached log it seems that the only bottleneck of my system is the GPU.... I'm looking forward to hints from you expert people out there. Thanks!! :detective_2:

Tried out the mission, everything work as you described except the soldiers do not follow the waypoints after drop... they just mill around :unsure:

Hi there! A few days ago I switched off the option "Easy communications" and I realized I have a lot to learn ;-P Till now I could make almost everything work as explained in the available tutorials... but I have still problems with the allied flights reports. I read in a previous thread that AI flights only use VHF. In the ME, only AM is available. So I set them to a VHF AM frequency that can be picked by the Huey: my trials were 123, 130, 135 MHz. But still, no luck... I don't get any allied flight report (the corresponding option is turned on). Note that in the same mission with Easy Comms I was getting all the radio chatter. Strangest thing: I get anyway all the reports from AWACS, whatever frequency and band I'm tuned on O_o Any idea of what's going wrong here??

Oh, so obvious... thanks mate!

Hi there, I wanted to try out his: So I created a mission where there is a soldier which transmits in FM at 35 MHz (I tried also other frequencies) but in the Huey I don't get the signal. I did this through the additional actions for the waypoints "Perform command" - "Set frequency"... is that correct? Any hint?

I've experienced wrong behavior and crashes with the new function introduced in v1.2.15: "Added previous waypoint selection with [LAlt + '~']. " In navigation mode, trying to select a waypoint lower than 1, gives a nonsense 8-digit number. In landing mode, the same gives a crash to desktop. Confirmed on the A-10A and F-15C.