JG14_Smil

Hi Gary, I am having good luck with 378.66. Seems better than the 381 drivers for me and DCS will accept them and run. Be sure to do the rename the saved games folder routine in DCS (although I see you've done a clean install and should not need it). Good luck!

So... will it ever be used to be able to see individual ID's in multi-player? If not, please stop wasting time on it.

That's how it starts.. :) Great work and good luck with your build!

The whole point of this is for MP servers, if it works as it should. Why would this be a game changer from what you already have?

When you say full screen, are you doing the ALT ENTER each time? For me, stutters aren't caused by DCS settings. I also use 8x MSAA and 16x AS without problems and I can't use full screen due to my mismatched multi-monitor setup. Optimizing the system takes a lot of experimenting and following threads with ideas to try. I know I stopped those constant stutters, mainly from this thread: https://forums.eagle.ru/showthread.php?t=68060

This is not meant as a bashing post. I just couldn't take it anymore and I did a clean install of 368.81 drivers. What a difference! It feels like I am flying an airplane again in 1.5. TrackIR is quite smooth. No stutter. I could not say that with the latest Nvidia drivers, even after much experimenting. 2.1 has made my 4 year old Titan obsolete. I am just not going to run those new drivers and instead enjoy this wonderful performance while I still can. Going to learn how to roll back to 2.0...

I know exactly what you mean about that arm pain from a center mount joystick what is too high. I had to re-design my center console twice to get it right. I would like a cut out seat, but I am able to fly with out any troubles. I should note I don't dogfight anymore and never need a maximum deflection of the joystick. You can try speeding up the joystick input with the Saturation X parameter to see if it can help keep the stick away from the seat. You have black X's for pictures. Here is a picture of my old Ka-50 center mount and seat. My L-39 setup (same joystick) leans forward a bit more and is a bit taller. Good luck with your build. Do not continue to fly with pain.

I see I have been wasting my time with this feature. I did note that the player pool bort number did not change, but I had no idea no one else could see my changes. Hope they perfect it for use.

Hi Gary, I believe there is a 32 and 64 bit runtime. I saw where one person had to load both for a fix. Did you do a clean install of gfx drivers? It is best to uninstall them, then use a cleaner utility while in Safe Mode to completely clean the old drivers out before loading the latest drivers in. I use Driver Sweeper. Sounds like you gfx drivers are still old ones.

Player is for single player only. Make everyone a client for a MP mission. They must be from separate flights and not wingmen from the same flight.

I came here to see if there were any memory issues with the Normandy map(?). I note that my system is very sluggish after I exit DCS and the Normandy map. There is like a 5 second delay if I click the shutdown routine for Windows. I've never seen that happen after DCS before.

I learned a little about trk's screwing up. I had saved a trk of a friend and I flying aerobatics and it worked perfectly. I later re-calibrated my joystick and edited axis in DCS and the plane won't make it to the runway, it instead makes a wide turn and gets stuck in the grass (when I replay the trk). The trk could not work the rudders properly due to the different calibration and L-39 brakes did not work correctly.

Thanks Pete, I'll look into my FB settings. Might be getting blocked.

Yeah, I tried sneaking my 368.82 back in after it started working and it wouldn't go for it. The smoothness from the 368.82 is now just a memory. I may just reload them and run 1.5 until I cant anymore. This is a loss for me... time marches on. I'm sorry Gary.. I missed your question. It all runs as it should, but the latest drivers seem to force more out of the card. Things like runway textures get sharper, but it just makes DCS a more choppy experience. I used to feel like I was flying an airplane in 2.0, now I feel I am back in a choppy simulation. It is not a matter of settings. I think the 4 year old card just doesn't do it well.

Latest Nvidia drivers fixed my problems. Please close thread if you can Mr Mod.

382.33 drivers got DCS 2.1 to run. You don't want to hear what I have to say about the way I think it looks now.

Tried a clean install of 372.70 and still cant run 2.1. will try 378.92.

I give up. Why was this thread moved to the Normandy section?

All my covers were scratch built and I left a concentric lobe near the pivot point to actuate the button or roller switch. L-39 covers are different with a different type of pivot point. I have another idea on how to do it with them, if I do go that route. I will most likely just open them up with a macro when I set other controls like fuel shutoff position at startup time and not wire them up. Easy peasy :) Added later: https://forums.eagle.ru/album.php?albumid=254&pictureid=5058 only picture I know of... you can see a red button just above a toggle switch as a cover was not added to one switch. Use normally closed buttons so they turn on when cover is opened. Button is right under pivot point and cam lobe does the work.

Use a power strip and then shut that off if you want to kill all power to the PC.

This seems like another funky one and others have the exact symptoms I do. Just going to have to wait for the fix.

https://forums.eagle.ru/showthread.php?t=187933 That will help you Stormbat. I'll give the command line repair a shot Automan.

Here is a crash file and log. I tried repairs and deleting my saved games folders.

Cant fly after update. Click fly and it never finishes loading.

All my Ka-50 covers had buttons under them to actuate them in DCS. Flew for years and not one malfunction. L-39 does not need backlighting as cockpit lights are flood lights so I may use snap action switches under my covers if I do go that route. I also don't hear the switches like I did in the Ka-50.. that was a cool part of having the covers work. By not hearing it in the L-39, and not looking at the DCS pit, there is no need to have the covers work each time, just leave them open and let the actual physical covers prevent accidental switching. I will repeat that the easiest way to make it work without buttons under the covers is to edit the auto start routine so it opens every cover and leaves them there (and nothing else). Very simple.