eliasr

A10C or F16

+1

It worked! Thanks! :joystick: Saitek....

I have the same issue, but only with this module and it isn't the first time. I think it is unfortunate if drivers affect the validation check, but I also wonder why it only happens on the mig21. I'm on my 6.th of 15, so its not a troublesome issue at the moment, but it is an annoyance that I have to go about manually removing the keys from the system because of this fault.

Mine was caused by the MIG 21 bis activation failing. Reactivation was accepted but it never progressed. As the error happened again i had to press exit on the DRM box multiple times and finally it would load.

Even a smaller upgrade to the combined arms would be nice. Currently it is rare to see JTAC missions in multiplayer, because either there are only a few people that has CA or they don't feel like playing it.

I updated from 1.5.3 u2 to 1.5.3 u3 today. For some reason, spawning in the a10c caused a crash (more details below) I noticed i could spawn in the f15c on some missions. I also noticed that the hawk tab that should be in special in options was not there. I tried validating, nothing came up as an issue. I also ran the updater again to be sure i had everything, but nothing was missing. I re-downloaded the Hawk module, this caused the hawk to show correctly up in the special tab in options. However the a10 would still crash my game. I noticed in a log that there was an access violation (c05), so i followed some troubleshooting steps, including deleting the saved games folder (and unfortunately also the logs that contained this error) It didn't work. Now i finally re-downloaded the a10c, and it is working. So with the c05 error, it is most likely that for some reason i had a bad file or a missing file - so a question remains: Why wasn't that caught in the verification of the files and being repaired? Is the verification including the modules at all, and if no, wouldn't it be a good idea to implement a verification for the modules to avoid potential crashes that can be hard to identify and caused by a module? But it isn't all lost, there is still a dump file in my logs from the first crash, i hope it may be of aid to you in improving the game even further:beer: Logs.zip

Gj Aarnoman Now we just need to find the ka-50 Would be nice to have access to these trainers aswell: http://war-hawks.net/training/

Ok, tjekker det.

I would put my money at the f16, but so i also would at f18. Right now i struggle with using my cold war jets for anything else than light air targets and coldwar / ww2 targets, however they can be fun to play. For the more modern i always end up with selecting f15 and it would be fun with a little more diversity. To me the f16 is more iconic than the f18, as the danish airforce has used f16 for so long time.

Yes that would be good. for 1.5 i'm wasting so much time in the server browser, trying to find a server with players, without >200 ping and with rules where i can comfortably say that i qualify. Right now the fav stars are the only ones that aids me, but it also means i have to favorite some of the lesser favored to avoid searching a lot.

I have the same issue with the hawk, asked ATC for startup on a server, and it crashed. I was able to recreate the crash on a different server. I was not able to recreate the crash in single player. Reproduction steps: Load in a hawk on a multiplayer server open atc menu request startup (if necessary you might have to set radio frequency, this was not confirmed) I did not have a crash doing the same with the f15C - so perhaps it is only the hawk that is the issue. Before i did my validation test (the last crash) i also verified my files on steam. No files were missing. I'm not using any mods. Logs.zip system_nfo.zip

Instead of just giving the "invalid serial" message on the login screen. It would be a great aid if the modules which has an invalid serial key is listed.:thumbup:

Great work! All i need to do now, is to set my CDU shortcut keys up and move the coms menu ( http://forums.eagle.ru/showthread.php?t=88889 ) Changing module works like a charm, and connections are also more failsafe now. I did not experience the issues that Montes had. A minor detail: height and width for the size of the MFCD's and CDU seems to be switched. That is, altering width actually alters height... or at least it is in mine. But it was really easy to set the right values in this update.

Thanks for the update. I just noticed it yesterday. It is some time ago I last worked with Lua, but I will eventually get around to fixing the export issue. I ran into another problem though. When I press start in DCSPanelServer ( v 1.0.8 ) I get the error message: This version is old! Please download newer from http://www.lumatek.sk So I downloaded it again, to be sure, but no luck. I recently updated my java to 8.0_45, so i tried downgrading, but it didn't solve the problem either. I don't have a clue on that one though.