Bonz

I created a mission that had few names assigned by me. I certainly didn't name any waypoints. Then I must have hit a key or some naming command and now all my waypoints and stuctures have names that all look computer generated... they look like a variation of the following: 5: DictKey_WptName_370 6: DictKey_WptName_178 etc... I suspect these are normally hidden? How do I get rid of them. They show up on the map as a ton of clutter. Help!!! Bonz...

Search for Process Lasso on the web. Distributing to other cores or their Hyper-thread or both. I'm not smart enough to know which is best so I'd do what BitMaster suggests. As I understand it... Each core on a four core system each has one hyper-thread. In the PL application these are labeled CPU0 - CPU7... with CPU0, CPU2, CPU4, and CPU6 being the "real" cores and CPU1, CPU3, CPU5, and CPU7 being the hyper-thread. Someone please correct me if and where I'm wrong. Bonz...

PL is Process Lasso... I don't know much about it but it allowed me to adjust "Affinity" which, as I understand it, is the tendency of a program to associate with particular threads within the core of your CPU... I think. Maxing out any thread can cause the Micro Stutters. Apparently many folks have seen them... possibly more often on newer computers. This happened to me on a new build computer... last fall... I've been trying to eliminate these "Micro Stutters" ever since. If you look at the YouTube video provided by David OC in a previous post... it clearly shows the problem and using Window TASK Manager the individual who produced the video demonstrates how to fix it. I wish I knew who this person is... I'd like to thank him. The time he took to build that video helped me tremendously. What I did follows: 1. Start out by opening Task Manager (Ctrl+Shift+ESC) while in DCS. 2. Click on the Performance Tab 3. Click on CPU 4. Move the mouse over the CPU Graph (If there is just the summary graph). 5. Right click and select "Change Graph to... then, Logical Processors. 6. This shows the various thread within your CPU. 7. Now at the top of the window click the Details Tab. 8. Select DCS from the list and Right click, Select Set Affinity. 9. Select the CPUs (Threads) that you want DCS to run on. 10. This will only be temporary... next time you start the game it will revert back to what it was... I think. Someone else might know better. But so far that's my experience. 11. Process Lasso is a program that will do the same thing but seems to make it more permanent... I'm very new to PL and I'm not recommending it... just telling you what I did that seems to have fixed my Micro Stutters. Bonz...

OK... here's the latest. Success! That was the problem and the solution. No more Stutters!! Hurray!!! First thing I tried was task manager. At first had trouble displaying all the threads, but after about a minute figured it out. Also figured out how to adjust my affinity. moved DCS from just one Thread to four, then six, then other configurations, all resulted in spreading the wealth and prevented any one thread from carrying the entire DCS load. Played the game and their was smoothness from end to end. I Then downloaded Process Lasso (PL) and quickly figured out how to adjust my affinity... and again smoothness all the way to the horizon. I'll need to become more familiar with PL to determine the best configuration for my system, but what I have now is centuries better. I've been trying to fix this for several months... Thanks to everyone who contributed especially David OC and the German gamer who posted the "possible fix". No More Stutters... this is something to know... Keep this thread posted. One additional note... when I first opened Process Lasso I noticed that all my apps, other than DCS, were spread to all 16 of my threads. DCS was the only program using only one. Bonz...

David OC... thanks! your post looks like a possible solution. I'm at work but will give it a try later today. I'll try the Task Manager first and then give Process Lasso a go. I'm assuming from your comment that the TM solution is not permanent. Bonz...

Still stutters on new machine... the biggest thing I've learned so far is the information provided by running MSI Afterburner was interesting and maybe it suggests a path to a solution. The big question I have... Why does my old machine i7 3430 with 12 threads balance the work load over all twelve threads way more than my new machine i7 7820 with 16 threads... which is very unbalanced with one thread running at 100% almost 100 percent of the time with the same settings flying the same mission? most of the other 15 threads are zero or nearly so... Both frame rates are now fairly stable around 60 fps (with Vsync ON), except when the demand is high and the FPS drop... this happens noticeably more often on my new machine which still has micro stutters. If anyone can explain why this is happening I would really appreciate it. It just seems odd. Both monitors are set to 60 FPS. New machine has an older monitor... Dell 30 inches. The old machine has a new 32 inch monitor. Bonz...

OK... I just ran MSI Afterburner on my old machine. What a difference. My processor only has 12 threads... labeled CPU 1-12 in MSI Afterburner. None of them are pegged at 100 percent. All are busy... but well below 100%. All are varying up and down but averaging about 25%. None show 40 or above, none below 10%. GPU usage is about 70%. When I left the mission and returned to the DCS homepage there was a momentary fluctuation in CPU usage but then not much change. Almost all CPU (thread) temperatures were in the 40s. What does this mean? 1. I have a bad processor on my new machine? 2. I have a bad setting somewhere... in DCS or BIOS? or Both or somewhere else? Vsync is ON on my old machine. Bonz...

Fair question... I did go through and set them all the same at one point... Could be that over time I may have reset that setting... someone recommended I turn VSYNC off... may not have done so on both machines. I will check when I get home tonight. When you say it will never go above my screens refresh rate... does that mean if I turn Vsync ON my FPS will never get any better than 60 fps (assuming that's my refresh rate)? As to the Core vs CPU vs Thread discussion... I understand all that, however the MSI Afterburner program refers to them as CPUs 1-16... as I recall. My point in bringing that up is that "Thread 1" is maxed out at 100% for nearly 100% of the time and then drops off to the low teens when DCS is shutdown. That seems like a hardware limitation. I didn't have time this morning to run MSI Afterburner on both machines... I'll run it on my Old Machine later today. I will also double check the configuration on my game settings on both machines so that I'm comparing Apples to Apples... I don't think that's the issue... this problem has been happening for several months... for sure during the time when I know all my setting were the same. The Vsync issue is different from the stutters issue, I think? Bonz

I ran MSI Afterburner this morning and I also figured out how to run the frame rate counter native to DCS. What I discovered... On my New Machine: The frame rate counter with Fraps only looks every second. The frame rate counter native to DCS samples more often. Both generally agree but the native counter shows greater variability then is indicated by the Fraps counter. Some fairly big swings every second. MSI afterburner also shows that my new machine has 16 CPUs and that CPU1 is the most effected by DCS startup and gameplay... it's running at 100% almost 100 percent of the time. Is that normal? Having said that the temperature for CPU1 indicated 0 degrees. That can't be good. I had to leave for work, but I plan to run MSI afterburner on my old machine as well. I'll post the results later today. One last note... Both frame rate counters on my Old Machine are rock steady at 60FPS, over dozens of seconds, compared to both frame rate counters on my New Machine at the same point in the same mission. It's almost as if there is a setting or program that mandates a minimum of 60FPS and this program kills other processes to make that happen. If so, it's running on my Old Machine and not on my New Machine. Anybody know what that might be...?? Bonz.

I should be clear about something... There are times when I'm getting well over a hundred frames per second in DCS even on my new machine. However, when playing the same mission on both computers the old machine is faster time for time. In that same game, on my new machine, when I fly out over water my frame rate jumps much higher. Its the comparison value that is not right. My faster machine on paper is not faster in fact. Having said that... 1. What is process Lasso? Is this a well worn program, something I can trust? 2. TrackIR and Voice attack are running on both machines... I don't see them as the problem. 3. I've tried the bare bones approach and the old is still faster. 4. My Samsung NVMe driver is up to date... I'll test to verify speed... but think it's OK. 5. Motherboard on the New Machine: Prime X299 Deluxe with updated BIOS 6. I'm making the assumption that GTX 1080 (New machine) is or should be faster than GTX 1070 (Old machine). My version of the 1080 is not the GTX 1080-Ti. Bonz...

Not sure if my onboard graphics have been disabled... The only item listed in Device Manager is my NVIDIA GeForce GTX 1080 Card. All Drivers are up to date. I don't think Ccleaner is loaded on my system... it's not listed in Programs and Features. I do have ASUS software running... for my motherboard and one of my three monitors and presumably I don't want to kill them. As for disabling my swap file... What I've read tells me that with 32GB of RAM on my New system and 22GB on my old system... it's not a lack of RAM that causing my micro stutters. I have two different Motherboards as well ... both BIOS' have recently been updated. Other than with DCS... both computers work fine. It could be a setting within DCS, but I've been up and down and sideways with all those settings... At one point I attempted to set all Options the same on both systems with no obvious differences. It's conceivable that I missed a setting. So I'd like any suggestions along this line as well. Bonz...

If anyone is having or has had micro-stutters during gameplay please read this and comment. I'd like to fix this problem and so far have been unable. I worked with ED/Support for a number of weeks/months last fall and was not able to determine the cause. I should state that ED was responsive and did suggest several possible solutions but ultimately to no avail. Here's the problem/situation... I'm having trouble understanding the cause of some micro stutters that I'm getting on my new machine. I have two active computers ... Old Machine: i7-3430K CPU @ 3.2 GHz with 22 GB RAM, Windows 10 Pro with an 1TB SSD 850 EVO C drive, NVIDIA GTX-1070 Video Card New Machine: i7-7820x CPU @ 3.6 GHz with 32 GB Ram, Windows 10 Pro with a 1TB SSD 960 EVO C drive (on Motherboard), NVIDIA GTX-1080 Video Card Other equipment includes (On both machines): TrackIR... Latest Logitech G13... Game Keyboard Fraps... used to compare frame rates Voice Attack with VIACOM Pro for DCS Other equipment NOT on both machines: On my new machine: SteelSeries Siberia 840 cordless headset Thrustmaster HOTAS Warthog Controllers (Throttle, Stick, and Pedals) Five other hard drives On my old machine: Sennheiser gaming headset CH Product Controllers (Throttle, Stick and Pedals) No other hard drives (My old machine had several extra hard drives before I purchased my new machine and it ran fine) Both machines have an array of other software doing various things. Both machines have DCS World 2.5 running and functional. My Old machine consistently loads faster and runs smoother. My New machine takes noticeably longer to load and has micro stutters... just enough to be noticeable. Frame rates playing the same mission compared: Old machine: 60 consistently... sometimes better New Machine: 30-40 consistently... sometimes better sometimes worse. I'd like suggestions on what could be causing this. If anyone has had this same problem and was able to fix it that would be ideal. Thanks for any and all help. Bonz.

I have version 2.5.0 running on two machines... one with a 1070 video card and one with a 1080 video card and the 1070 runs smoother... both fantastic. Great job by development team... Started my downloads last night (Central time)... didn't take as long as I expected. Maybe I beat the drumbeat. Bonz

Thanks, but not sure I know what "Internal Build" means. However, I believe I've tried using the Group Stop command as well... Not sure of the results due to the way I set it up and so testing still needs to be done. Bonz...

I'm building a single player mission for my own M.E. training. Using trigger zones and player movement, I have a Jeep that leads the "Player" to the runway then moves to another place to await the "Players" return. Then leads the Player back to the Hangar. I tried using Trigger zones and Hold and Resume commands to get this done. However after each move the jeep returns to the original starting position before completing the next task. What am I doing wrong? Bonz...

Thanks to all... it was the COMM issue, the swapped radios. I also learned about how to really set up a Tanker Mission profile. Thanks

Looks like it requires a restart of the game to dumb what's in the controllers from Control Manager... Any way to dump without shutting down? Bonz

OK... Not sure what I'm missing but I'm attempting to set up a practice Air Refueling mission and for some reason the tanker doesn't answer my call and doesn't deploy the drogue. I've set up the KC-130 with five waypoints... 0-4 0 - Airborne spawn 1 - Begin Tanker Track (Rectangle with about 35 mile leg. 2 - End Tanker Track 3 - Descent waypoint towards the tankers destination 4 - Land at Destination I setup the players AV-8B aircraft a few miles behind the tanker... heading towards the tanker track. On the set frequency (131.0) for the tanker I ask the tanker if I can rejoin... I get no answer. When I come along side, the Tanker aircraft continues along as if nothing has happened. The drogue stays tucked away. I must be missing something Bonz :smilewink:

I calibrated my CH Controllers using Control Manager. I was able to start the AV-8B after that but then in DCS Control Setup all three (Fighter-stick, Pro-Throttle, Pro Pedals) of my controllers were labeled the same... something like "CH Products Controller"... Hard to tell which controller is which? How do I get around that? So that I can see each controllers name in DCS. Bonz...

I'm still looking for an definitive answer to this question. How do two players play on the same LAN without using two accounts? Is that possible? Or how would someone join in the same aircraft using two computers over a Homegroup LAN using two accounts ... one without any aircraft and the other with the needed aircraft... Is that possible? Legal?

Well I have several USB devices hooked up... That could be a problem, lets hope that's not it. I did try the dead zone solution, but it didn't work... however I wasn't paying attention to where my throttle was... Ill try that again with my throttle pulled all the way back. As for keeping the controller calibrated using Control Manager... I will try that, however I have a question. I prefer to use key binding set up in DCS world. If control manager is used does it interfere with what DCS sees as available controllers and hence my ability to bind keys? Bonz...

It's definitely the Throttle... I did the start up procedure with two different sets of controllers. Works great with Warthog throttle. Doesn't work with CH Products Pro Throttle. It appears that the throttle is no quite fully back... I've tried the suggestions above... Idle cutoff, Engine Stop, etc... I checked the Little Idle cutoff lever under the throttle. My throttle controller hits the hard-stop before the SIM Throttle is all the way back... Again I tried several key bindings from the User guide t can't get the throttle back to the hard stop... at least that's what it looks like.... Help? Bonz...

This is strange. I've watched several youtube videos to determine what it is I'm doing incorrectly. However, after two hours of trying I'm asking for help. I assume I have a bug or activation or configuration issue... Not a procedures issue. Quickly, what I've been doing... I start a mission created in Mission Editor... very basic just one AV-8B at some airport. Then: 1. Battery - On 2. Gen - On 3. Both boost pumps - On 4. Fuel Prop - on 5. Fuel Shutoff lever - Down 6. Nozzle - back 10 7. Parking brake - off 8. Engine Start - Start No indication of RPM???

The Manual I'm talking about is the user manual for DCS World. It explains how all the functions of the basic program work including Options, Mission Editor, etc. I'm sure that functionally not much has changed, however, the manual was written to a much earlier version of DCS World and a significant number of format changes have occurred so pictures used in descriptions no longer match what they are trying to explain... The same document is used for both DCS World 1.5 and DCS World 2.0. So... Can I figure it out? Yes. Is it a pain in the ass? Yes. Is it a priority? No, not if it means a delay in game content or DCS World 2.5. My point in bringing it up was to find out if an updated version is in-work or already out. I can usually find what I need by muddling through the existing manual or by watching a YouTube video on the subject. I would describe myself as an experienced flyer but relatively new to DCS World... Not quite a year. So when you say not much has changed... New-bee's are the programs lifeblood. We should be making it easy for folks to learn. I think that is happening... YouTube and individual aircraft manuals etc. Plus this forum is also helpful. I'm just suggesting an improvement. Love the program. Bonz... P.S. I have all the aircraft manuals with the possible exception of the AV-8B. The ones I've used so far are good, very helpful.

In that circumstance... how would l fly with my son in law in a two place aircraft or against him in two separate aircraft? Without buying aircraft for the server computer? One of us would have to use that computer to fly. Sounds like I would need a third computer to act as Server? Bonz...