coder1024

you know happens when you assume? :D Why do you have curvature in a throttle axis? I would think you'd want the same response regardless of where the throttle is. As opposed to the flight stick where you might want curvature to allow small inputs from center.

so full 6DOF with FC2? I thought they said it was limited somewhere. Or is this with a mod? Is that pit clickable?

I read the pits were not full 6DOF. But are none of them clickable either? If so I guess it just means you have to learn a bunch of keyboard cmds :)

aw, boo hoo! you're saying FC2 doesn't have any clickable pits? not even the SU-25?

the eshop is down; after adding something to your cart you just get a blank page. someone plz kick the server :) EDIT: nevermind, its back up now. I just successfully ordered a copy of LOMAC. once that arrives, I'll get FC2 and check it out :)

ok thanks. might want to update the system requirements to list that. does LOMAC actually have to be installed? what if I buy LOMAC digitally and have no CD to verify?

If I do not own LOMAC or FC1 what do I need to buy for FC2? Is it necessary to buy LOMAC + FC2? Or can I just buy FC2?

yes, windows joystick shows correct movement. but for some odd reason when in the pit in DCSBS you move the handle quite a ways before seeing any response in the cockpit collective. I'm curious whether this is just a graphical error though. Do you see the same thing? When you get in the pit and unpause, look at the collective and watch it as you raise the joystick throttle. Does it track 1:1? Or do you also see a significant dead zone? Maybe the 3D update is just wrong but the actual collective effect is correct. Not sure.

if it was a bad sensor, though, then I'd see the same issue in the axis tune window or in the windows game controllers screen which shows the axes right? both places indicate that its responsive for the entire physical range of the throttle. I would think those windows are reading the same data as the sim in the pit.

ok, I uninstalled, verified the folder was deleted, and then re-installed and patched (I installed to D:\DCSBS, D: is a secondary internal Raptor 10k RPM drive). After doing this, I setup the controls, went into a mission, and it worked! So looks like I'm good now. Not sure what happened, but its working now. I'm curious about the collective though. In the axis tune page, there's no deadzone, the entire physical travel shows a response in the window. Yet, when I'm in the pit, I have to raise it quite a ways before the stick in the pit moves at all. Any idea what that is?

There's one more column there not visible. Its for TrackIR and its mapped to the absolute camera axes.

I checked and yes, the Saitek X-45 is set as the preferred device in the Windows Game Controllers control panel in Win7. Here's a screenshot of the axis settings page. You can see the throttle is not assigned. I verified each axis is correct on this screen using Axis Tune for each and they all work as expected. With the above settings, I clicked "Save As" which produced a file containing the below. I then clicked OK and exited the sim completely. I came back in and verified the settings still showed the same thing. ["axisCommands"] = { [1] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_X", ["filter"] = { ["saturationY"] = 1, ["saturationX"] = 1, ["curvature"] = { [1] = 0.21, }, -- end of ["curvature"] ["deadzone"] = 0, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2002, ["name"] = "Flight Control Cyclic Roll", ["category"] = "Axis Commands", }, -- end of [1] [2] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_Y", ["filter"] = { ["saturationY"] = 1, ["saturationX"] = 1, ["curvature"] = { [1] = 0.21, }, -- end of ["curvature"] ["deadzone"] = 0, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2001, ["name"] = "Flight Control Cyclic Pitch", ["category"] = "Axis Commands", }, -- end of [2] [3] = { ["action"] = 2003, ["name"] = "Flight Control Rudder", ["category"] = "Axis Commands", }, -- end of [3] [4] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_SLIDER1", ["filter"] = { ["deadzone"] = 0, ["saturationX"] = 1, ["curvature"] = { [1] = 0, }, -- end of ["curvature"] ["saturationY"] = 1, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2004, ["name"] = "Flight Control Collective", ["category"] = "Axis Commands", }, -- end of [4] [5] = { ["action"] = 2007, ["name"] = "Camera Horizontal View", ["category"] = "Axis Commands", }, -- end of [5] [6] = { ["action"] = 2008, ["name"] = "Camera Vertical View", ["category"] = "Axis Commands", }, -- end of [6] [7] = { ["action"] = 2009, ["name"] = "Camera Zoom View", ["category"] = "Axis Commands", }, -- end of [7] [8] = { ["action"] = 2048, ["name"] = "Camera View Horizontal Shift", ["category"] = "Axis Commands", }, -- end of [8] [9] = { ["action"] = 2050, ["name"] = "Camera View Vertical Shift", ["category"] = "Axis Commands", }, -- end of [9] [10] = { ["action"] = 2052, ["name"] = "Camera View Longitude Shift", ["category"] = "Axis Commands", }, -- end of [10] }, -- end of ["axisCommands"] Despite all this, when I get in the pit and un-pause and move the X-45 throttle the yellow throttle levers move but the collective does not move. If I start exiting, doing settings, going back in, repeating, it eventually gets hosed up where the settings page shows mappings copied across multiple columns which don't make sense, etc. At this point, you have to clear them all out manually and re-do it. But the same problem is there, no collective control, and the X-45 throttle is for some reason controlling the yellow throttle levers.

I'll double-check. And look for the throttle mapping just in case to make sure its not setup for any of the axis. Maybe it was somehow linked to the same axis and is being checked before the collective or something in the code.

The thing is I setup the control for the collective axis not for throttle. I mapped the Saitek axis to the collective axis in the options window. No idea why its linking it to throttle instead. See the contents of the .lua file I pasted above; it indicates "Flight Control Collective" for that joystick axis.

this is just strange... It seems after going in and out of a mission multiple times (each time, once in the pit the collective would not respond, when I move the X-45 throttle the small yellow levers beside the collective mode not the collective) and checking the settings each time I got into a wierd state where when going into settings and choosing Axis controls, the stuff in the saitek column was copied over to the ch pedals column. Clicking load on the previously saved .lua file didn't change anything in the display. Exiting out completely and coming back in didn't either. I had to delete the .lua file and then restart and it came back with reasonable defaults. But still no collective in the pit. I was getting collective a few days ago I'm pretty sure.

Here's the relevent portion of the file. Anything look amiss with this? ["axisCommands"] = { [1] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_X", ["filter"] = { ["deadzone"] = 0, ["saturationX"] = 1, ["curvature"] = { [1] = 0.21, }, -- end of ["curvature"] ["saturationY"] = 1, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2002, ["name"] = "Flight Control Cyclic Roll", ["category"] = "Axis Commands", }, -- end of [1] [2] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_Y", ["filter"] = { ["deadzone"] = 0, ["saturationX"] = 1, ["curvature"] = { [1] = 0.21, }, -- end of ["curvature"] ["saturationY"] = 1, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2001, ["name"] = "Flight Control Cyclic Pitch", ["category"] = "Axis Commands", }, -- end of [2] [3] = { ["action"] = 2003, ["name"] = "Flight Control Rudder", ["category"] = "Axis Commands", }, -- end of [3] [4] = { ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_SLIDER1", ["filter"] = { ["deadzone"] = 0, ["saturationX"] = 1, ["curvature"] = { [1] = 0, }, -- end of ["curvature"] ["saturationY"] = 1, ["invert"] = true, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] ["action"] = 2004, ["name"] = "Flight Control Collective", ["category"] = "Axis Commands", }, -- end of [4] [5] = { ["action"] = 2007, ["name"] = "Camera Horizontal View", ["category"] = "Axis Commands", }, -- end of [5] [6] = { ["action"] = 2008, ["name"] = "Camera Vertical View", ["category"] = "Axis Commands", }, -- end of [6] [7] = { ["action"] = 2009, ["name"] = "Camera Zoom View", ["category"] = "Axis Commands", ["combos"] = { [1] = { ["reformers"] = { }, -- end of ["reformers"] ["key"] = "JOY_SLIDER2", ["filter"] = { ["saturationY"] = 1, ["saturationX"] = 1, ["curvature"] = { [1] = -0.24, }, -- end of ["curvature"] ["deadzone"] = 0, ["invert"] = false, ["slider"] = false, }, -- end of ["filter"] }, -- end of [1] }, -- end of ["combos"] }, -- end of [7] [8] = { ["action"] = 2048, ["name"] = "Camera View Horizontal Shift", ["category"] = "Axis Commands", }, -- end of [8] [9] = { ["action"] = 2050, ["name"] = "Camera View Vertical Shift", ["category"] = "Axis Commands", }, -- end of [9] [10] = { ["action"] = 2052, ["name"] = "Camera View Longitude Shift", ["category"] = "Axis Commands", }, -- end of [10] }, -- end of ["axisCommands"]

I went back in yet again and setup the axis controls then verified them all with axis tune. I then clicked the button to save the profile and clicked OK. I exited out and took a look at the .lua file it saved. I noticed that for the joystick axis assignments it just identifies them as "JOY_X" and "JOY_Y" for the cyclic and "JOY_SLIDER" for the collective. But it doesn't seem to indicate which device these are associated with. For the CH Pro pedals, it has entries in there for rudder axis but nothing indicating which device, not even something like the joystick. Just a very brief entry. So I'm not sure how, using that .lua file, the game could figure out for sure which input device these go with. I'll add the actual file contents here tonight.

When using Options>>Controls and trying to configure your axis, DCS:BS is still pretty buggy. It was like this at release and still with the latest patch seems to exhibit some odd behavior. I'm using a Saitek X-45, TrackIR5, and Ch Pro Pedals. I had it setup and working yesterday. I ran the sim today, went into Options>>Controls and the settings were all changed. It showed "Mouse X/Y/etc" in the Saitek column and other wierd stuff. I manually cleared out all the Axis assignments and set them up again. Now, no matter what I do, I can't get the throttle to actually control the collective in flight. Instead it controls the 2 yellow levers beside the collective. This is despite going out of the mission and into options>>controls multiple times and setting it and having it appear to be set. When I got things looking good in the control settings, I would click save profile. Well I went back and did load profile and it was nothing like I had saved. Not sure if its me or my machine or something else, but this part of the UI has always just been really cranky for me.

its now September and still no manual available from Amazon. what's the deal?

still no joy at Amazon.com.... 4 weeks from when exactly?

I think he was looking for comments from readers not just the TOC which lists the sections. I'd be interested in hearing any as well. Also, still nothing on the US Amazon site :( http://www.amazon.com/Ka-50-Black-Shark-Attack-Helicopter/dp/0956183603/ref=sr_1_1?ie=UTF8&s=books&qid=1244465756&sr=1-1

can someone from ED please give an update on the status of US Amazon and the manual? Have you guys talked to Amazon about this? Any ETA? Something? :)

from here.

The dynamic campaign was one of my favorite features of Falcon. I'd love to see ED provide this for the DCS series. Well designed missions are a great thing, but they're nothing like kicking off a dynamic campaign and letting the computer run a war for you and hopping in the middle of it with some friends and battling it out. Yes, if you're talking real world training, this really isn't what you want, you want to train specific skills, etc. But for a PC sim, the dynamic campaign adds a huge fun factor element to the mix. There's a place for both hand-crafted missions and also a dynamic campaign. Hopefully this will get added.

still holding out for the US Amazon site to stock it. Seems a bit ridiculous that they don't have it available yet.