MadDog-IC

Checked on mission #7 Fighter sweep and flight starts on runway nowhere near a truck and take off successfully. Are you referring to how it was some time back, as the F-15 Bear Trap campaign had a revamp about a year ago, and I just re-tested Mission #6 with the english version of DCS 1.57x and it plays out fine. SEAD and STRIKE aircraft are programmed to not jettison weapons under any conditions (Especially whilst being attacked), this was a new setting when dcs 1.5x came out. And all radio commands to send in SEAD worked appropriately, with the result of all SAMS destroyed and strike package hitting the runway. Sounds like your are playing an older version of DCS or a non-english version that wasn't updated, because these issues don't exist in my english version. The modified versions in english are available on the Eagle Dynamics website under user files. https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=100&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter Regards, Ian.

That particular mission has a intro track recorded within it, so it has a saved view from the machine it was recorded on, this will over ride any local versions of snapviews, etc. You have to delete the Config directory (which has the View directory and snapview.lua files) within the mission to fix it, Presents mission has one also. You could also download my edited versions of the Su-25T Single Player missions from the user files section that removed that problem, and other issues: https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=100&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter Regards, Ian.

Good work, I have just done the same with Skull leaders P-51 cockpit mod, took a bit of trial and error, but I am sure I have got it now. Regards, Ian.

Was reading your post earlier, I wasn't able to get the A-10c richardo cockpit working some time ago, even though the directories are correct as per your previous post. Long story short, I just fixed it, turns out my file manager (Total Commander) had an option turned on that plays around with the case of letters on Directory names, displaying capitalized first letter and lowercase on the others, this is what was wrong, they have to be all UPPERCASE for it to work. Regards, Ian.

You can only fix this by getting the registry clearing files to remove the keys from your windows install, and then reactivate after doing that, you will loose an activation for each module you need to do it to. You should have deactivated all modules before the upgrade, but most of us are guilty of that, as it can be a major pain. Has been mentioned many times in forums so shouldn't be hard to find the info on where the files are. Regards, Ian.

Here are the default A-10c single player missions all fixed up to work better and with 4 player Co-OP. A-10c single player missions made for 4 player co-op Regards, Ian.

I find that very surprising, I would lodge another support ticket to ED, respectively asking to get the BS2 upgrade module delinked from your online account as it is no use to you anymore, other users have had this done successfully in the past, so I know they will do it. Don't accept no for an answer. As I have stated previously, this is totally normal procedure and the way the module manager works, install the full version and forget about the prompt for bs1 to bs2 upgrade. If you can't live with being prompted for the bs1 to bs2 upgrade, I repeat the only fix is to have Eagle Dynamics delink the BS2 upgrade module from your actual logon account, that is the only way as it is the same as you never having the module, you will never be prompted again to install it. Yes just live with it, or do the above with ED, The whole reason for buying the BS2 full module was to forget about the bs1 to bs2 upgrade module as you can never install it, unless you have BS1 and installed first, as you say you no longer have BS1 so the bs2 upgrade module is dead in the water, not installable, not upgradeable, not anything. However the new BS2 full version is installed and working correctly and is capable of being upgraded and patched as time goes on. Playing with the registry at this point and for this problem will not fix anything, and may only serve to loose key activations and or cause other issues with windows. I will however provide a key remover file to remove the Blackshark 1 keys from the registry. You have me totally confused, I am getting really repetative and getting mixed messages from you, if you have both the BS2 upgrade and BS2 full version being asked to be installed, why if you have BS full installed and working fine, do you even want to try and install the BS2 upgrade, it is the exact same module as the full, just with the requirement of having to have BS1 installed first. I have a similiar setup as you, I bought BS1 on steam years ago (so it is always installed), then I bought BS2 upgrade, and finally bought BS2 Full. I have the BS2 upgrade still installed, but DCS always insists on asking me to install the BS2 full version as well, I don't and I move on and play the game. (Not a big problem) I consider the issue resolved. Cheers, Ian. Remove BS1 key.zip

Totally agree, two of the best little campaigns I have played, also recommend Operation Bactria and although haven't played Operation Crimson Dawn , just because it was made by Baltic_Dragon, who has a high regard as one of the best campaign makers. Cheers, Ian.

Always appreciated, thank you, surprising how many people download them, but never comment on how they went when playing them. I am also guilty of the same thing, I download good missions left and right, but might not play them for months, so I don't give any feedback, so I kind of understand it. I make more of an effort these days to thank the authors of fine work more often than I use to. Cheers, Ian.

Here you go. Regards, Ian. DCSW - Su-27 (FLANKER) (1.5x)_VAC.zip

Surprised by you request, you have all the skills to do a mission by the sounds of it, can't be that hard to fly the waypoints to the target area and get amongst it. I know there is a big difference between theory and putting it all together under pressure in a hostile environment, the best way to learn is doing it yourself (based on youtube stuff I suppose) or in Multiplayer with someone that is willing to teach you combat strategies. There is one CAVIOT though, the default set of A-10c single player missions are broken in a lot of areas, some of which you have already encounted by the sounds of the other message. This will put any noob off. Not to toot my own horn, but you may be better served by grabbing my corrected version on the ED user files section (link below), the should work a lot better, baring any recent introduced bugs since I corrected them. https://www.digitalcombatsimulator.com/en/files/?PER_PAGE=50&arrFilter_pf%5Bfiletype%5D=&arrFilter_pf%5Bgameversion%5D=&arrFilter_pf%5Bfilelang%5D=&arrFilter_pf%5Baircraft%5D=&arrFilter_DATE_CREATE_1_DAYS_TO_BACK=&CREATED_BY=MadDog-IC&sort_by_order=TIMESTAMP_X_DESC&set_filter=Filter Regards, Ian.

Whilst not related to your issue. The hotas issues I just found I have since last update: Can't use any aircraft controls through my hotas that require a RIGHT control, Alt or Shift modifier key like Rcntrl-Home to start the Su-27 motor or the trim hat, but if I issue the same key combinations from the keyboard they work fine. Explanation: (With the X-52 pro, I have all key commands programmed through the SST software to issue actual keyboard commands to DCS, and do not directly mapping any joystick buttons to a DCS function). Game no longer knows the different between a Left Alt, Shift, Control and a Right Alt, Shift, Control modifier key command. Trying to nut this one out, as the only thing that has changed on my system is the DSCW patch revision. Now Fixed - Installed the latest driver from logitech for the X52-Pro Hotas. Know problems for a while, fix is to delete: c:\Users\YourUserName\Saved Games\Dcs\MissionEditor\Settings.lua Time to do as I suggested in other post about renaming the aircraft directories that are affected with issues and let DCS rebuild them from scratch defaults, then input your changes, such as axis, etc. Hang in there it has been a rough ride for all of us, I understand how you feel, been there done that. Regards, Ian.

First have to determine if it is a bug or a problem with just your installation, not to doubt you are having an issue, but as I have fully tested the whole Su-27 training missions only a few patches ago it is unlikely to be bugged, not impossible, but the original missions had very few issues. Re-tried both of these uncorrected original mission in game it self and both worked fine. Some times the control setups for some aircraft can become corrupted or don't update correctly with a patch adding, removing, or modifying the function of certain keys. If users have unexplained issues with controls, it may time to rename your saved games folder and let DCS rebuilt the controls from the defaults or just backup the following folders to a temp directory and re run DCS to rebuild from defaults and re-setup controls back to way you had them and re-test that you have fixed issues. c:\Users\YOURUSERNAME\Saved Games\Dcs\Config\Input\su-27\ c:\Users\YOURUSERNAME\Saved Games\Dcs\Config\Input\su-33\ c:\Users\YOURUSERNAME\Saved Games\Dcs\Config\Input\su-25T\ Regards, Ian.

That would fix it, as the default SU-27 start up training works flawlessly here with my X52 pro setup and keyboard commands. Few people have been having issues with their hotas throttles not going to full idle 0% settings, so they might just need recalibrating in windows and or a tweak in DCS controller section as you have done. Very common for the SU class of aircraft as the throttle has to be at idle for motors to start. Regards, Ian.

Great, at least that part seems fine. I would have a guess that the unrecognised serial number is most likely the Blackshark 1 key number, that has been input correctly in the past or some other anonomly. I would say that the parameter that is incorrect, is that the module manager is trying to use the blackshark 1 key number to deactive a BS2 upgrade module instead of the actual BS2 upgrade key numbers which will just not work. Last resort fix I can see for this problem, and may cost you one activation for your BS2 keys, is to use the ED registry clearing tool for the keys of BS2 in your windows registry. Solution: ---------- Before you do anything, make sure you have all Serial Numbers for your BS2 modules, written down, you will need to re-enter them later on in this fix, you can get them from the profile page on ED site if stuck for most of them. This will delete the old DCS module keys stored in the Windows registry for Blackshark 2 upgrade and the full version also, so if you can DRM deactivate the full version first with the module manager before doing this fix, great you will not lose an activation for that module only the BS upgrade module. Download the file attached file and unpack the zip file and run the file with .reg after it by double click it with the mouse and accept any prompts it puts up to include into the registry. Once that is done, re-run the activation window, via running DCSW module manager. Re-Enter the correct Serial Numbers for the BS2 full version and re-activate. Ignore anything to do with the BS2 upgrade version if prompted. Can test in module manger to see if all seems correct now. Problem should now be fixed. Delete KA-50 BlackShark 2_Reg_Keys.zip

Doesn't mention the updater, it says to run the repair tool, you do that from the windows start button on your taskbar and go to the all programs directory and then find the DCS program directory and repair tool icon within, it will then verify your install and remove and backup any mods that don't belong to the original DCS program and replace any missing files that should be there in DCS. Default path to Game most likely: C:\Program Files\DCS World 2 OpenAlpha\Mods\aircraft\Ka-50\ How to do repair and other things with the command line. https://forums.eagle.ru/showthread.php?t=114030 Not being able to unbind from the ED website, is what I talked about in the first post, others have had issues and had to go to the support section and issue a fault report to ED for them to unbind it for them, I think they did that so you can't share or swap your keys with other users, you use to be able to, but is forbidden now. Regards, Ian.

Ok so we have a separate issue in DCS 2.0 then. I would suggest that: Using the DCS 2.0 module manager, deactivate and uninstall and delete all copies of BS2 that you can, including full version and update version, don't worry about the ones that you can't. With DCS 2.0 shutdown, using a file manager go to the DCS 2.0 game directory for the Ka-50 module and delete the Ka-50 directory if it still exists (This is to make sure all Ka-50 files are actually gone). example path to Game: C:\Program Files\DCS World 2 OpenAlpha\Mods\aircraft\Ka-50\ Now run a DCS v2.0 repair function from the windows start bar or command line. After all that, fire up DCS v2.0 and run module manager and see if you still have any corruption and or if it now gives you the correct install dialog for both the BS2 upgrade and BS2 Full versions, if so install the BS2 full version by leaving it ticked, and untick the BS2 upgrade so it is not installed. If still getting issues, uploading a dcs.log file might be handy to figure out issue: c:\Users\YourUsername\Saved Games\DCS.openalpha\Logs\dcs.log Regards, Ian.

Because the BS update is still linked to your online account back at Eagle Dynamics website, so long as any module is linked to your account it will always ask to be installed when you fire up DCS (hence why asked you to unbind BS2 upgrade from your online account - if you can't do it, then you put a support ticket into ED for them to do it for you). Just install with module manager - BS2 full version and ignore anything to do with BS upgrade, untick it from the modules you wish to install.

Any deactivation in the DCS module manager, just stops the game from using it or you playing it, it leaves the module installed, but not usable, yes that is correct. To remove module totally from the DCS install after deactivating with DRM button, use the trashcan to right of it. Also don't confuse deactivating module at the User account level, with deactivating the modules serial number in the DCS module manager for purposes of hardware changes, etc.

Yes, once it is deactivated, you will never be asked to install it when firing up DCS. So if the BS2 upgrade is deactivated, then the only option for DCS is to ask for you to install the BS2 full version.

Most definitely yes, will also add a disclaimer I am not responsible for any issues you may face by following these instructions as I haven't needed to use these functions so I don't know what pitfalls they may have. When you login to the ED profile page, in the license check section down left hand side, input your BS2 upgrade key number and press check button, it will then show who's account it is bound to, you also have an unbind key to unlink that module from the current user, doing this will deactivate that module totally from you account, you don't lose ownership of it, it is just rendered inert. The part I am not sure about is whether: You can re-link it again to your account if you want to use it at a later stage. You can re-link to another account that you may own. You can't link it to another users account, but if you don't want to ever use the BS2 upgrade module again, you can donate the key to another account holder relink wishing all ownship for that module to them once they link it to their account. Now do a license check for the BS2 full version modules key number and make sure it bound to your current Username you use for DCS login. Once all that is checked, you should be able to run any DCS v1.5.7 or v2.11 versions and add the BS2 full version module through the inbuilt module manager or the command line installer. Regards, Ian.

I don't believe there is anything wrong with the mission, this problem has been discussed before, several problems with ATC radio stuff, basic DCS game engine issue that needs ED to fix. Regards, Ian.

Whilst I can't help you here to much, I would check that both BS2 keys are linked to the same account in you profile on ED site, note the key number for the full version. Then do a repair on your copy of DCS and try the module manager again to see if you can install the full version of DCS using the appropriate key number, btw even when you do get it going, it may still try and ask to get your upgrade version of BS2 installed also, it use to with me, but they may have fixed that now. You may have to submit a ticket to ED support: To deactivate the upgrade version of BS2 from your account (some others have done this in past) and to make sure the new full version of BS2 is linked to your account. Did you purchase both BS2 keys with the same online account ?? Cheers, Ian.

I have several issues with the George W bush mod with dcs v1.5.7, using the Hornet 8.3 collection from VFA stingers site. Initially dcs would crash once you were in cockpit, some updated Lua files fixed that. I removed the FA-18 mod files and tested with the SU-33 PFM aircraft and seemed to work ok, except I can't land on carrier due to my own incompetence, kept crashing into the end of the ship.:doh: Installed the FA-18 Mod files and it broke all the controls for the Su-33 aircraft controls due to its "default.lua" file replacing the games default.lua for keyboard and joystick. (These files have changed a lot since 1.5.6 and now the su-33 PFM in v1.5.7), compared all "default.lua" files and modified them to allow all correct functions of the Su-33 PFM in game, as well as the modifications for the Fa-18 special features as well. Tested FA-18 basic stuff worked in game such as gear, flaps, hook, speed brake, lights = no problems. Finally everything seemed to be working as it should, so I tried a carrier landing, it all went well until touchdown on the carrier, instead of trapping, I kept on going through the carrier deck and exploding inside the carrier. Fixed going through the carrier and exploding: Replaced the F-18a.lod, F-18c.lod and F-18-collision.edm files in the MOD folder \Mods\aircraft\FA-18C\Shapes\with the originals from DCS v.1.5.7 in ..\DCS World\Bazar\World\Shapes\. Been practicing put the F-18 on the deck all afternoon, finally catching the cables. Also got the PLAT camera operational again, the original overlay program doesn't run anymore for me so I used this program to place the overlay on the LSO camera view. http://customdesktoplogo.wikidot.com Regards, Ian.

I think what is wrong, you have set the initial speed of carrier at 32kts (29kts or 59kmh is max speed of real ship), but your next waypoint is still set to the default of (10kts or 20kmh), so the ship is just slowing down to meet that next waypoint speed. Cheers, Ian.