VAF [136] Striker

I get what you're saying now. You don't mean it's my processor specifically but more a processor issue related to using some scripts. Has there been any investigation by the MIST and CTLD or ED people into what's causing this yet?

I'm not a scripting person but I don't agree with you saying this is a CPU processing problem. This problem did not exist with 1.5.6 or the most recent update to 2.1. We were running these missions perfectly fine until then. Also, I'm not on Windows 10, I'm on Windows7 Pro 64 bit so I can see all the cores and what they're doing. I'm not an expert by any means but I can see that the maximum combined processor usage is 9% and the individual cores only spike (not all at the same time) at 80% occasionally. They then drop down to a flat amount around 10%. This is telling me that the processor is functioning properly. This is definitely scripting related since it doesn't happen when I remove MIST and CTLD.

OK, here's my update to the test this morning. The problems with stuttering and planes flying in weird positions appears to be MIST related because the mission I originally posted about has MIST only. When I run the mission with no clients the FPS swings wildly from 10 FPS up to 45 FPS. You can also see the counter actually stop and start so it looks like the mission is running very erratically. When I run a mission with no scripts in either 1.5.7 or 2.1 I get very clean FPS, very steady, around 60 FPS (default server setting). When I run a mission with MIST and CTLD the frame rate drops to a steady 5 or 6 FPS and almost never moves from that. So it looks like in combination, MIST and CTLD make the mission unplayable for now. Just using MIST slows the mission as well, not as bad but still slows the missions enough to cause the weird client behavior or at least that's what it looks like to me.

I was thinking last night that I should have done that. That would be more helpful to narrow it down. I was tired and didn't have time. I'll do some more testing and see if I can do that today. The only problem is that I only use MIST for CTLD so I'm not calling any of the scripts from it in the mission. Not sure if just loading it in the beginning will do much but I'll try it anyhow.

OK, I get it now. What's happening is that when we run CTLD and MIST the frame rate drops to 0-1 FPS. When I run a clean mission the FPS runs at whatever I want to set it at up to 120 FPS. I set it at 30 in the config file and it runs at 30. Set it at 90 and it runs at 90. We tested it with a no script mission in NTTR this evening and it's smooth as silk. Has anyone reported major FPS problems concerning CTLD and MIST?

0

They're part of the Mission Object Oriented Scripting Environment group.

I did. I ran an empty mission, clicked on spectators and then hit fly. It just gives you a light blue screen with no graphics and I can use right control and pause to get the FPS counter.

0 FPS I'm assuming that you want to see that since the server isn't running any graphics at all. Also, in the old version for the server it was suggested to turn the FPS down from 180 to 30. Does that still apply?

OK, thanks. So I can just add that line to the autoexec.cfg and it will take care of it. We've had up to 15 in the past with no problems at all but the test yesterday was with only 4 clients.

Do you mean on the client list screen? When I start a mission the only options I know are either to go to the map or show the client list.

Hey FlilghtControl, thanks for that info. I bet it's the 3D Rendering. It was originally off but I didn't turn it back off after the last patch. I thought that there was a way to set this into the "Saved Games" folder so that patching wouldn't overwrite it. If so, can you point me to the instructions to do that? On the other points: It's not a CPU load problem. I've been running a dedicated server for 2 years now on the same system. It's a 6 core 3.2Ghz with 16GB memory and I've had missions there were almost double the number of units and didn't have this problem. This was something that happened with the recent couple patches. When I checked the system load the CPU was at a steady 9% and the memory was at 5.24GB. On the internet connection. It's not lag or internet problems. I have pretty good ISP and my upload is steady 6Gb and download 60Gb. I tested using speedtest.net just prior to testing again. One test was late evening and the other was afternoon, off peak time. On the video. Sorry it was 13 minutes long but there are parts all over it where you can see the problem. I should have edited it down to just those points. I'm attaching the tacview file in the first message. On the RWR mod. That's only on my system and not on the dedicated server. DCS World crashed after we exited yesterday and I wasn't able to get a clean track file from the server. I included the log from the server but the track was from my system. Thought I made that clear but I'll note it.

We've tested this twice now and same problem happens. Log file and Tacview file are from the dedicated server. Track file is from my simulator system. The video is 13 minutes but the problem is mostly in first few minutes while on taxi. Dedicated server is an Asus Sabertooth X79 with a 6 core 3.2 Ghz processor and 16 GB of memory. Windows 7 64bit. Clean system and mostly only used for hosting DCS World. It's on a wired connection with 6gb of upload and 60gb of download. This problem happened after the last couple patches in stable 1.5 version. Tacview file shows everything clearly. Client aircraft flying sideways, warping and vanishing and AI units warping all over the place.

I'm assuming that you are referring to either the EAC or the PAC if you are not actually turning on the autopilot using the "A" key. Is that correct? The EAC (Enhanced Attitude Control) and PAC (Precision Attitude Control) are functions that are enabled by default or if in flight with weapon systems enabled when you get into a quick mission. Please give more information so it can be explained better.

I have a lot of respect for you BN but I beg to differ with you on this statement. We've had several "big" announcements that turned out to be delayed for a long time. The last post in this thread states that 2.0 would be ready in 2014 and we all know that got delayed for over a year. Same thing has been happening with the Hornet and now the 2.5 merge. The merge was supposed to happen earlier this year and now it's been delayed again so another year long delay. https://forums.eagle.ru/showthread.php?t=129630 Another thing that's kind of frustrating is that we always find out about delays and redirection from someone translating the Russian side of the forum. It seems like the English side is treated like an unwanted step child and we have to dig to get the information especially when it's bad news regarding official delays or problems.

Hi Ciribob, We tested it last night with the old and new API and it's working OK. It looks like updating .net and setting the volume down to -95% makes it workable. Do you have any plans to readjust the internal values so that the slider is 0% without distortion?

We know. We all like SR and want to continue to use it. We'll try the older API and let you know the result.

We've already done all of this. We were on Buddyspike yesterday and almost everyone we were trying to talk to had the exact same problem. I know some of them had Windows 10 so that's why I felt pretty confident it wasn't a OS problem. But anyhow, this is really frustrating because it was working fine with 1.2.6 and now it's basically unusable. I'll try updating .net and let you know if it helps.

On our server as well?

Not an OS problem. It was working fine a couple versions ago.

The distortion is incredibly bad now with 1.2.8.0 and 1.2.8.1. We can't even use it now. Please tell me what we need to do to get it working correctly again.

Just to add to what's already been stated. G's and K's are 300 lb penetrating warhead so they're perfect against ships or large targets like them. They go deep inside the structure or hull and explode inside causing a lot of secondary damage. D's and H's are only 125 lb but shaped charge so they're good against small heavily armored targets. I take out ships all the time with G's. You can sometimes get them with 2 but the bigger ones take 3 or sometimes 4. The bigger problem is that the non-static Mosvka shoots 5V55R (same as SA-10) missiles at you so you're never going to get close enough to hit it with the A-10C.

Any way to set this or are they always in pairs?

Figured it out. Not more pitch but less pitch needed. When at about 150 meters altitude pitch the rocket reticle up to between 5 and 10 degrees on the pitch ladder. If you're pitched too high they illuminate but way too high above the ground to have any effect. If you do it at 5-7 degrees the illumination lasts for about 40 seconds. If you count to 18 after the first group starts lighting the ground and then fire off the next group and keep doing this over and over you can keep the ground continuously lighted at 6-8 km away. If you pitch too low or not at all they just crash into the ground because the parachute doesn't have time to open.

Have you actually tried them and got them to work in the Ka-50? I was at about 500 feet and even tried pitching up over 30 degrees and still nothing. We tried it on the Buddyspike server.