shilka

thanks it works. But actually I just found out that my initial problem is having zipped one more layer of folders...

I'm trying to modify a10c cockpit texture but couldn't get the dds format right. I'm using photoshop CS4 with nvidia dds plugin. I unzip A_10C_C_EDM_TEX.zip, modify the corresponding dds, save and pack it back again. But the dds "save as" dialog is rather complicated and I don't know how to set the parameters. The result is missing texture. any idea?

That would be great! A simple example showing the syntax would be sufficient. I also have problem with LoGetMechInfo(). Simply can't get it to work under BS. Was trying to get gear states.

can I export switch states using export.lua? So far I din't find any clue inside export.lua

TM Warthog HOTAS I spent the whole night experimenting different curves for DCS:BS and finally figured out the reason why changing only Y saturation and curve factor never satisfy me. Because in BS there's a build-in deadzone somewhere between 5 and 7! And angular speed achieved by using axis remains the same in either wide and narrow view but this angular speed will be adaptive if you're using keyboard. That means when you find a comfortable slew curve for your axis in wide field of view you will find it way tooooo fast in narrow field of view. That's why when I set the deadzone = 0, Y saturation to 40 and curve factor to 100 almost the entire axis became deadzone. So my solution is to use "user curve" instead of automated one. my settings are as follow: deadzone = 6 //remove vibration x and Y saturation = 0 user curve: 0 6 7 7 7 7 9 10 10 17 50 the trick is to keep the value >=7 wherever you don't need a deadzone It's basically a 3-stage curve. The portion near axis center is for narrow FoW while other sections for wide FoW or fast slewing.

I'm using the download version of BS. I have both vista and win7 installed on my laptop. Is it allowed to install the game on both os? They're on the same PC and surely have the same specification. And these two copies will never see each other since only one OS can be active at any given time.

a dummy layer... That's clever. I'll do that. Thanks:) btw I am using script from day one. But as long as you don't get any output from game you can't judge the switch state anyway. Maybe the export.lua would do but it doesn't worth the trouble.

Well I prefer to keep the SC axis for slew. It allows me to control speed better than keyboard. At least I consider it more important than that "key sync" problem. The slew control in BS requires some fine tune. I use customized curve with "0 6 7 7 7 7 9 10 10 17 50" and a deadzone of size 6. Because any axis input <=5 will be ignored by slew control. It has a build-in deadzone. "switch sync" I mean for example if during game loading your MasterArm on HOTAS is left in "on" position but the default position of MasterArm in game is in "off", you will have a opposite logic whenever you use that switch. It happens if you don't have independent keys assigned to every state of a switch but use a "toggle" key instead, like "g" for gear.

I think they exist because of historical reason... On real A-10c this button is not a simple "push-button" but a toggle button. A single push will toggle the state of the button from "released" and "depressede", and vise versa. That's why there're 2 states for this button. It will probably automatically pop up if the pilot moved the joystick during a Autopilot flight. Maybe during initial design they plan to use a toggle button here but apparently the final product used a push-button instead. The states are lost.

I want to map EngineFlow switches on TM warthog to directX axis so that I can map these virtual axis to LeftEngineBrake_ByAxis and RightEngineBrake_ByAxis (to solve switch syn problem). The maximum number of axises allowed in directX is 8 while 7 of them are already occupied. There's not enough axis left for me to use. DCS:BS by itself could support up to 32 axis on a single device so is there a way to bypass this limitation?

Actually these 30xx commands are also in command_defs.lua The problem is that it only tells you they belongs to "button ##". But exactly which button on that device (\scripts\aircrafts\ka-50\cockpit\devices.lua)? That's another story. why don't you just cut their time field to half to see if it works? regardless of the nature of the command code. check the last section of that file:

ok I found it. It's in a file \Scripts\Aircrafts\Ka-50\Cockpit\command_defs.lua

Not yet. The only lead I got so far is to go through other ***.lua files in case the functions are lucky enough to be used somewhere in the official script already. that "to be continued..." is driving me crazy~

Not necessarily the command code for LoSetCommand() function but I need a full list of command codes for cockpit events. I found some commands listed in export.lua(the same information is posted on DCS website http://www.digitalcombatsimulator.com/en/dev_journal/lua-export/) but this list is not complete. For example I can deduce that the "Engage Descent Mode" in BS is code 507 but it's not mentioned in the list(It says "To be continued..." in export.lua). I want to map the position of some toggle switches into independent keyboard shortcut so that it can be synchronized with the toggle switches on my HOTAS. For example I want LSHIFT+g for "Gear Down" and RSHIFT+G for "Gear Up" instead of a simple G for "gear lever". I'm editing keyboard.lua and it works fine so far. I can deduce the rest of command code from existing entries in keyboard.lua but an official reference would certainly save me a lot of time...

I mean that "view hat" is actually a "trim hat". It's called "view hat" merely because we need this function since we're not in the cockpit(unless you have sth like trackIR). Sorry I missed some details on previous posts. I thought they map trim to "trim switch" by default but seems to be the other way around. I didn't have a-10c beta yet.

Actually that trim mapping is not a mistake because that's how it works on a real plane. It's mentioned in DCS manual.