overalien

Not sure if this is relevant but my logs consistently show this as some of the last entries: 2018-04-20 16:12:24.904 WARNING NET: Session has expired. Logging in again... 2018-04-20 16:12:25.050 INFO NET: Login success.

I am having this problem with three monitors. https://forums.eagle.ru/showthread.php?t=206430&highlight=monitors+freeze definitely specific to 2.5 release version. 1.5 runs stable.

Same problem with 3 main monitors and two Lilliput MFCDs. Various setting downgrade combinations did not work for me. It seems as if the game slows down to a crawl with about 1 frame every 30 - 60 seconds. It has not frozen entirely - sounds stays on and one or two frames are rendered every minute or so. Getting great and smooth framerates before the freeze. I recently changed to the multi-monitor setup and that seems to have triggered it. DCS 1.5 runs rock solid stable with exact same settings. Only 2.5 gives me this problem. *EDIT: I also tried 3D Settings management by Nvidia drivers instead of by game settings and this made no difference. Specs: Core i7 8700k @5.0 GHz, 32 GB RAM @3600, GTX 1070 OC, 3 Main Monitors and two Lilliputs in windowed mode (No NVIDIA Surround) - Centre View @6039x1440

Yip. I'm still here too. :thumbup:

saw them here: http://downloads.guru3d.com/download.php?det=1484 says "x32", but text says "x64" - are they for real? anyone try 'em yet.

"whatever you do... don't mention the war!" almost killed me laughing, man! :megalol: inappropriate perhaps, but the guy who made this hit the spot for me.

such a pity about the shadow thingy, since otherwise the drivers seem smooth and stable. anyone know whether the shadow bug is driver related or LOMAC related?

Hey ARM - howzeeet! You could try linking to a hosted game using a different connection. At least this will eliminate the possibility of some "sensitivity" of the LOMAC client session to a modem or line problem - DSL has signal attentuation as far as I know and you might be close to some magic threshold for LOMAC. This is just speculation to help me sound like I know what I'm talking about :megalol:, but at least you might be able to eliminate the connection quality question. You're welcome to pop in here at my joint to try it out if you have no other buddies with a DSL link close by. PM me ;) and we'll see what we can sort out. overalien ___________ All your AMRAAM are belong to us.

For the record, I also ran out of activations recently and I asked ED for help. I received a new serial, with a fast friendly and hassle-free response. No problem.:thumbup:

yup, FPS increase here as well, although not quite the 10 -15 FPS reported. tearing with TIR about the same as it's always been (running GByte 7800 GTX with 16AF and 8AA). :pilotfly:

yep, had those problems too, at first. It seems to be important to run shoot with a toggle switch and only to toggle it on when issuing commands - then turning it off again immediately. if you use a "hold key" function or leave it listening all the time, you get this kind of behaviour with LOMAC. have you tried that?

i use shoot with .net 1.1 and I love it. It takes a lot of nursing and experimenting to get it to work well with LOMAC, but a little bit of patience rewards you with good results. some lessons I learnt: take a little time to train the MS speech recogniser - it only needs about one or two additional reading sessions (over and above the default training) to start recognising speech more accurately (that's only about 20 minutes of your time) - you can also train custom phrases via shoot to increase accuracy good hardware (boom mic on headset) and a quiet environment are very important if you have a dual core processor, use procaff to run shoot on the second CPU and LOMAC on the first - gives more stability shoot dislikes background noise and gets very confused if the microphone is on all the time - it's best to only turn on the mic when issuing a command and then turning it off again shoot works best with LOMAC if you use a single button toggle instead of a "button hold" push-to-talk configuration (i use scroll-lock) - this way you have little chance of conflicts with other keys in LOMAC i set up my HOTAS Cougar to "emulate" a hold config on the radio button by programming a "press" and "release" sequence on the button (each one sends a Scroll-Lock keypress) - that way, shoot starts listening when you hold the radio button and stops when you release it, without any key actually being held down i used a "tree structure" when programming shoot for comms commands - that makes the xml file smaller and easier to modify afterwards (my config file is attached - it is currently limited to comms commands only) i modified the feedback sounds so that it's more obvious when shoot acknowledges a command hope this helps somebody out there to benefit from this great little app. ;) LOMACFC.xml.txt

thanks, kon. :D i've never used the loadout section before because I just assumed that the there would always be a default loadout. this has happened a few times, so i just assumed it would always happen - one of life's little lessons, i suppose. i'll be sure to check it out.

I'm still new to online MP, so this might be a well known problem - sorry if that's the case. ;) I have had intermittent problems when joining online sessions via Hyperlobby: I start on the ground with no missiles. The "rearm on ground" function does not fix this and the only way to get things going is to exit the game completely and try again (sometimes a few times without success). Any help would be appreciated.