Home Fries

Yeah, it should go without saying that this feature should be client optional and server controlled as well. Another thought on this: I would love to see an optional lua entry in the skin file that would point to one of the default skins as an alias if someone didn't have the custom skin. For example, if I'm flying a custom VF-142 skin with 201 on the side, someone who doesn't have my skin would see the VF-142 205 stock skin instead of the VF-103 line bird.

This might be a more realistic solution with the broadband we have now. It was implemented with IL-2 Forgotten battles, but those skins were limited to just over 1Mb, not the 100Mb skins we get now. However, pumping 10 skins could be a Gigabyte of data pushed to each client that doesn't have the skins, and that will put a lot of upload stress on a server. If ED implemented something where any public skins were in use, and they could be linked to the ED user downloads, then the clients could be linked to the ED site to get the files. Only problem then is that the client would need to close and relaunch DCS to recognize the new skins (and most likely the client would need to manually install the skins before relaunching).

Yes. That explains it. FYI, here is the error as well as the data dump, just in case it helps. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at SimShaker.UI.ProcessManager.StartSeatHandler(String arguments) at SimShaker.UI.MainForm.Form1_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- SimShaker for Aviators beta Assembly Version: 2.2.8.0 Win32 Version: 2.2.8.0 CodeBase: file:///C:/Program%20Files%20(x86)/SimShaker/SimShaker%20for%20Aviators%20Beta/SimShaker%20for%20Aviators%20beta.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- NLog Assembly Version: 4.0.0.0 Win32 Version: 4.7.8.12686 CodeBase: file:///C:/Program%20Files%20(x86)/SimShaker/SimShaker%20for%20Aviators%20Beta/NLog.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.ServiceModel Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Not sure if this has been posted before, but I'm running the beta. The first time I run DCS after rebooting the computer, SimShaker gives the dialog saying that an exception has occurred and then prompts me to continue, debug or exit. Continuing brings up SSA, but the data entries for the aircraft settings are empty. Closing the SimShaker taskbar app, then reloading it seems to solve the problem. This is consistent upon reboot, and consistently clears after I close, then re-launch the taskbar app.

Reviewed and fixed the issue. The AV-8B now uses an analog airbrake (at least for extension). The fix is in beta testing right now to make sure I didn't break anything else (I use a global airbrake routine, and moving the AV-8B to analog may have affected some if/then statements).,

Thanks for the heads-up. I'll post it on trello and look into it.

What you can do is assign a modifier or switch, then apply each key on the CDU as the same key + the modifier/switch on the CDU key in the control setup. So for example if you use the APU switch on the Warthog throttle, you could assign Joy_BTN_20 as a modifier. Then you assign the CDU "A" key as Joy_BTN_20 and "A". Then as long as you have the APU switch in the up position, you can use the keyboard for your CDU. If you don't have a Warthog throttle or a controller that keeps a button pressed for as long as a switch is on, you can choose a "switch" instead of "modifier" in DCS. The difference is that a modifier holds down the button in DCS for as long as the button is held, whereas a switch function in DCS works as a toggle (e.g. pressing Hat2 Up holds Joy_BTN_7 and pressing Hat2 Up again releases Joy_BTN_7). But if you have a switch on a throttle that can act as a modifier, this is the best way to do it. Note: I give an example of this in my F-14 LANTIRN guide which can be found in my signature.

Version 2.61 is released. Change Log: Added Mosquito FB VI Mi24: Added toggle option to SC/T1 Petrovich Minor fixes to Spitfire Updated bindings since 2.60: Mosquito, Spitfire Updated SnapViews since 2.60: Both Updated Custom Luas since 2.60: None

So the next question is when you have Warthog Joystick set to 1 and the stick on the Warthog base, do the phantom buttons on the cougar stick do anything to the Thrustmaster Combined in the Device Analyzer?

Maybe not. try plugging the stick into the cougar base to see if that fixes the problem.

I agree with your assessment, but if you comment out the line I gave you above, then setting Warthog Joystick to 0 should still work. It may not fix the issue, but it's worth trying. I honestly don't know what's causing the problem, but this is just trying something to see if it works. I have tested the WH stick on a WH base with the Cougar throttle in TARGET with no issues. Do you have anything attached to the cougar stick base? I wonder if the absence of a controller could be doing anything.

Make sure you have Number of Thrustmaster MFDs set to 0. This value can be found under Global in the category titled Hardware Configuration. EDIT: I'll take a look at the Su-25 routine to make sure there's nothing wrong with the code. I don't specifically support this configuration, but you shouldn't have trouble if you set Warthog Joystick to 0 in CTS. The real difference with the HC stick and WH stick is the pushbutton on H4 which the Cougar doesn't have. However, you may want to find and comment out the following line near the bottom of DCS_World.tmc: if (!WarthogStick) Configure(&Joystick,MODE_EXCLUDED); //added in 1.67 just add // to the beginning of the line to disable it. TARGET will still look for the WH stick, but won't assign anything to H4P. If this works, you may want to go to your DB\DCS_World_Template.tmc and comment out the line there as well. You will need to comment out the line every update, though.

Did you ever have IL-2 Tank Crew set as one of your MFD shortcuts? If so, make sure you replace it with something else.

Version 2.7.60 is updated for DCS 2.7.6.12852 (added Mosquito).

2.60 is released. It adds the Mi-24 Hind and removes IL-2 BoX and Elite: Dangerous to free stack space. CTS is now once again exclusively DCS. Be sure to remove any MFD shortcuts for IL-2 or Elite when re-compiling CTS.

Two's in Trail!

I have a version in beta testing right now. It's fairly rudimentary, but if there are no bugs I plan to release 2.60 this coming week.

+1 here as well. When you have missions that periodically spawn aircraft, this bug makes OCA Strike missions completely useless, and often negatively affects the intent of the mission (e.g. OCA strikes being a means to roll back the air threat).

The P-51 is not listed because it's automatically activated (since the TF-51 is free with DCS World).

2.57 Hotfix 7 is up. It fixed a configuration management issue with Hotfix 6 (i.e. the F-14 custom lua is fixed) and updates the F-14 diff.luas. Of note, the RIO MFD3 is fixed, and the throttle curves have been tweaked so that the speedbrakes and DLC close at the mil power detent.

Hi JanRalle, Hat 2 and Hat 4 pretty much match up on the Warthog and Hornet sticks. The difference is that since the Hornet castle switch has a push button, that maps to H3L. The rest of Hat 3 maps to the pushwheel next to the Recce button. So keeping the F-18 stick attached to the base will work with other modules, but the Hat 3 mapping won't be intuitive.

Did you set your joy_btn30-32 as modifiers in both the pilot and RIO stations?

Just the LUA

2.57 Hotfix 6 is up. It only affects the Tomcat, and only if you use the Custom LUA.

Not sure what to say here. Looks like you did everything right. I can't find any issues on my end, I can't duplicate the error, and none of my beta testers have reported anything. Since the joystick file works, just use that. The only thing you lose with the keyboard is the discrete settings for the STO Stop. Hopefully the issue will sort itself out with the next AV-8B update.