nemises

strange?...make sure the aspect ratio has also changed with your new resoultion.. if you are running 1920x1200 (16:10, 1.6 aspect ratio) or 1920 x 1080 (16:9 , 1.7777 aspect ratio) If that is the case, then the zoomout will be the same, and look correct, though it does draw more of the cockpit because of the widescreen res, which I guess can make it a bit less zoomy ? when zooming out..

yeah makes sence, it should be more stable using banding, since , by its nature, the bands are much wider than the actual input ..... maybe I should try a banding solution rather than mapping it straight to axis...

I just don't think this style of sim , or at least the missions developed so far are suited for large groups to play online in an airquake fashion / adversarial and unplanned. Most people playing multiplayer will be doing it on closed privately hosted peer games. I strongly suspect it will be exactly the same for the A10 However, with that in mind, the 104th Lockon Server will be running as a DCS server on Mondays and Tuesdays.. come and check it out....theres a few new features running that might just help out a little..

Mig 29a has allready been confirmed as "on the list" , as well as all of the others Erdem posted , and as well as those, they are also looking at the F16c ! I believe that these are the modules they have "in some stage of development" , and so there may be others not on that named list, but are possibly on the horizon. Bare in mind, ED think they will average 9 months between modules , so we are allready looking at a list that is 6+ years into the future!

unfortunately, the price of an inexpesive hotas, is cheap parts!.. I think the sensors on the slider, and rotary dials (potentiometers?) are very prone to "flicking" between whole values ... I definately get flickery zoom on the slider in lomac / il2 / black shark , though am used to it now (usually stay stable untill the slider or the throttle axis are moved). I think it is just an innacuracy in the design of the hotas..but given the price, it is still an excellent product imho

...presumably it is a lower poly (read 1 surface!) proxy to make sure it doesn't adversely impact scene rendering time ... I don't know that this would feature high in any "fix" list , as it is no doubt by design...but fair enough to ask I guess :)

if you search a bit, I believe it has been posted that ground unit AI is beeing adressed, either in the patch or DCS:Hog , or in the new engine!...

awesome work shrubbo!

no problems running the sim on that, I was running 1920x1280 , medium everything on a amd 4400+x2 (2.0 ghz!) 2GB mem and a 7800 GT , and it was perfectly playable (15 - 20 fps)

Step 1: Watch all of Matt Wagners Producers notes for black shark. This will cover many many topics, including startup procedures, basica navigation, weapons etc.. You can find them on this site, infact in this forum, and also on youtube (though I suggest getting the higher res versions from here)

Another thing to check is that you are not accidentally trimming your rudder.. When you press the trim button , it will trim Cyclic and rudder at same time, so be sure that your rudder pedals are centered physcially before you trim. Pres ctrl-enter to check on the position of your controls to make sure you have fully cancelled out any rudder trim.

quite possibly one of the radios wasnt powered on...turn on all of the radio's (right hand wall, lower row) ?

god, if only.... please someone ffs make a good hotas with ffb

I think if you delete all the shift-state's , then the pinkie button becomes button 36 (?) , instead of a SST shift button..havent tested tho, but thats what i understand from previous postings

Hi Gibbon, Yeah, this is normal for the lockon engine... I guess it has to do with the camera point of view getting near enough to the ground plane that the clipping kicks in... Clipping is designed to block anything to close or too far away from rendering for rendering speed purposes.. The down side is, it can clip away the ground plane if you get too close, and you see the effect you are explaining. Rather than beeing a "glitch" , it is just one of those little things about this particular rendering engine...it is by no means rare though, many other games have similar rendering pifalls... In this case, since 99% of the action should be hapenning in the air, if a sacrifice in rendering accuracy on the ground has to be made for the over all good of the engine, then fair enough I say :)

DVI and HDMI are the same pin format so you will not loose any detail..just adding in an extra potencial point of failure...but converters and cables are cheap any way, so.. I wouldnt base a purchase specificall on it, but if you had 2 completely equal choices, but one had HDMI out as well?..go for that one ... What you will miss out on by converting is HDCP , the content protection part of HDMI , but since your PC isnt outputting anything HDCP , thats not really a problem :)

yes, very good point... press "crtl-enter" while in the cockpit, and note what is hapenning to the rudders...as you could be double trimming, or accidentally trimming and getting "double transforms" like Zaltys said.

...which I guess goes for the lack of radar on the KA50 , which is only designed to combat "...guerilla doodz with RPG's running around" :) as for in afghanistan, I'd hazard a guess that the Mk1 Apaches only have laser guided hellfires as opposed to radar guided models ? ...or do "radar guided" hellfires also use a laser spot for homing, and the longbow is just for aquisistion ?

That filter will not work next time you watch something that uses ffdshow...nfi what it does... I probably wouldnt worry too much about it though... :)

I found it really intereting to read (and perhaps the Apache drivers on this forum can confirm?) , that , at least in Afghanistan, and as relates to the british Apache Mk1 drivers , they have the mighty Longbow radar, but do not even use it , or need to use it, and do everything by laser designation and mk1 eyeball.

You must be fairly patient with it also...even when you do eventually get it installed, there can be 20 or 30 seconds of seeming non activity even after running the game launcher. Make SURE that your system drive (ie wherever you have windows installed) has a few gig free, as it is very likely the installer module is unpacking the .exe and .cab into your %temp%... good luck!

I have an x52 and have had no such issue...though I now have the twist locked and use pedals. Anway, as a test, open up the joystick control panel (not the saitek SST , but the windows control panel) .. check the rudder axis...twist the stick a bunch of times and see if it sticks there also. If it does, then your joystick is a little borked...if it is out of warranty, consider getting a screwdriver and opening it up to figure out what is sticking..could just be a detached spring or a brocken bit of plastic that can be superglued. If it does not, then go through your button assigments in game with a fine toothed comb and MAKE SURE you do not have anything else bound to your rudder movement (in keyboard, mouse or joystick buttons or axis) .. it could be something silly like having your pitch axis bound to both pitch and rudder...

Hi Mikeman, I'm no expert sorry, but if you use the search function, there is a couple of huge and very informative threads on this very subject :) Good luck! Nem

Hi, Not necesarily...I map my X52 fully in game and do not load any SST profile. *edit* sory, hadnt fully read Glottis post before posting, so let me just re-inforce what Glottis has said allready except for having a blank profile *edit* Anyway, it is very easy to map the buttons you need! Go into the controller options in game, double click on the item you want to map, select the "button" field, and press the button on your joystick! .. it will automatically map that button. If you want to have a modifier, then first Add a new Modifier by the same way (there is a button at the bottom for modifiers)..in my case, I have the pinkie button set to be a modifier. In teh button assignment secion, there is a seperate section for modifiers..once you have defined the modifier button you want once and saved it, then you can set the modifier by just pressing the button on the joystick same as a normal button. very easy..the trick is to go into the button assingmend screen, rather than trying to guess what button is what from the huge dropdown.

It's been confirmed as definately the A10c next