![]() |
|
IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
OK, I deleted the control axis for the single throttle. It was, of course, unplugged as well. I had calibrated my throttle quadrant. I tried it against the test gauges in Controls with my previous settings for it---all were a big 0.
I attempted to re-log the levers into Control Axis, and the setting for the single CH throttle immediately popped into the window before I could move a throttle lever. I finally was able to move a lever quicker, was able to get the proper info into the window, but when I tested the throttle it was showing only a partial movement on the test gauges. Logging the levers properly proved impossible. So much for a throttle quadrant. I am curious, has anybody been able to get a throttle quadrant, CH or other, to work in this game? There is still the matter of the game losing force-feedback on my Microsoft stick. In nine years of flight simming with every one available in that period, I have never lost force-feedback in a stick. This is definitely new. I suspect there is some arcane techno conflict here. ROF and the Third Wire flight sim I currently have installed both work perfectly, and ROF is certainly a complex monster. Clearly, my equipment is working. |
#2
|
|||
|
|||
![]() Quote:
I use the Saitek throttle quadrant and it works perfectly. I do not have a Force Feedback Joystick, but as far as I remember it, that was a major problem from the very beginning of the game. I hope, someone with a Force-Feedback Joystick may help you here. As for the throttle-Quadrant: Have you tried to put ALL other axis to 0% or 100% when you set up an axis? Because if you (e.g.) want to set up axis y but you have axis x ond 56%, it may select axis x instead of axis y you want, because axis x is flimmering and flickering a bit ond 56% what the game recognises as movement... As for the rest, i can very much understand your frustration. Getting trough the GUI (and its bugs...) and understand it is a very enerving issue, but at least for me it was worth the time... This might as well help you with bombs on your bombers: http://theairtacticalassaultgroup.co...ead.php?t=4625
__________________
AMD Penom ll 6x 1055T Processor 2.8 GHz // 8GB Ram // XFX Radeon HD 7870 Black Edition DD (2048 MB Memory DDR5, GPU 1055MHz) // Windows 7 Professional 64 Bit Version Saitek x52 // Saitek Throttle Quadrant // Saitek Pro Flight Rudder Pedals // Track IR 5 |
#3
|
|||
|
|||
![]()
Hello Leit. Nice to see you up and running again. 'Fraid I can't give you much help on setting up your controls, though I know several people with set ups similar to your own who have made it work. Some good links given here though and your best source of info is probably the ATAG forums these days.
Can't tell you much about bombing in a Blenheim either. I appear to have become attached to the rotol Hurricane - it's the aeroplane of a gentleman! However, I do use a MSFFB2 stick and I'm afraid to say force-feedback only works properly for card carrying Democrats in this sim. For the rest of us mere mortals it's a rather hit and miss affair. Some claim ffb works for them if they fire a few rounds before take off. Others that ffb cuts in whilst flying slowly. For me ffb starts to work when the airspeed exceeds @300kph in single seaters. Once it's working it stays working until reduced to landing/approach speeds when it disappears again. This makes take offs and landings doubly exciting! Good luck with it. |
#4
|
|||
|
|||
![]() Quote:
See my post #6 here http://theairtacticalassaultgroup.co...ead.php?t=4635 This could also explain the lack of bomb dropping- you assign a DX button, not a keyboard emulation key through CH manager? - if the joystick numbering changes and bomb drop is a DX key this would explain the 'no bomb drop' Quote:
this indicates (to me at least) that there is some 'noise' on the CH throttle axis that is picked up when you try to assign axes. Can you please confirm that Anthropomorphic Control is NOT ticked in the realism settings as Hugso suggests- this really can screw things up particularly with any noisy controllers. Quote:
I also did a test last night using one of my custom controllers, assigning 2 axes as throttles#1, & #2 and they worked fine ingame. Again can I remind you that you MUST hit APPLY for any assignments to work ingame. They will work perfectly in the bars in the assignment screen but if you hit BACK they will revert to the previous setup and thus NOT work ingame. Can I suggest this as a plan of attack:- 1) make a backup of all the ini files in 'Docs/il2 sturmovic cliffs of dover' in particular ConfUser.ini (a very apt name ![]() 2)start with one fixed joystick setup (no plugging/unplugging until you get one plane/setup working right) 3) go to controls section and click 'SAVE AS' and save your current setup as say 'start1' - then if it all goes wrong you can LOAD this back and hit APPLY. 4)clear all axis controls and start from scratch assigning them. 5)SAVE AS say 'TEST1' and APPLY 6) test ingame. 7)If/when you have axes working properly, only then do the same for any key/button assignments. ![]() ![]() Boring I know , but a logical approach works best to isolate and solve issues, CoD is complicated, often counterintuitive(most 'issues' make perfect sense to a coder - but not to the average user imho). Good luck |
#5
|
|||
|
|||
![]()
i never had any trouble getting bombers, blenheims or anything other, to hit ships. set discipline high though or they will take the near target rather than the ships if there is one which is what it sounds like happened. ai settings matter.
also it sounds to me like you jumped right in and expected to work everything out straight away which is a little unrealistic, there is a learning curve with any sim |
#6
|
||||
|
||||
![]()
Concerning ForceFeedback, there's a long known bug (see here and here) and a workaround.
Description Bug 191: If player spawns on ground and starts normal, there's force feedback from the control surfaces (aileron, elevator) relative to speed and flight situation (plus force feedback from ground, engine, guns, etc). If player spawns in mid-air there's force feedback from engine and guns but possibly not from the control surfaces (aileron, elevator). Steps to reproduce: Start Computer Start CloD Go into Single Player, Quick missions, start any (i.e. "Free Flight - Channel") Hit "Fly" Now, there is either force feedback from the control surfaces or ther is not. (A) If there is no force feedback Take up speed and make a looping force feedback from the control surfaces kicks in halfway through it Force feedback from the control surfaces will then always be present in airspawns, unless: (B) If there is force feedback Hit <Esc> Exit back to Quick Missions Exit CloD (Main Menu, Exit) Restart CloD Go into Single Player, Quick missions, start any (i.e. "Free Flight - Channel") Hit "Fly" There's no force feedback from the control surfaces
__________________
Ceterum censeo the mixture axis should be supported in IL-2 1946' DeviceLink. ------------------------------------------------------------- ![]() |
#7
|
|||
|
|||
![]()
Hey leit.. How have you been? I feel your pain on the FFB.. I use the same stick you do and so far for me it still comes and goes.. but you will find that it (CoD) is better than it was ... at least to me. I am sure that part of that has more to do with my rig which is much better now but I noticed that even after the last official patch and the last ATAG patch it runs better than it did on the same PC when I initially fired it up after upgrading.. The FFB thing is a downer for me though because it is so inconsistent.
|
#8
|
|||
|
|||
![]()
Hey arthursmedley and Bearcat---good to be back with the old crowd! Life has been bleak without flight sims and the good companionship.
I just reinstalled Windows 7 because it was acting squirrelly. I am not sure how much was real game trouble and how much was the op system not working right. Add to this a Rosewill headphone set did not agree with my computer, and KOed every other USB device as well as not working itself. I see from a lot of posts FF can be troublesome. At times I can get it to kick in by wobbling my stick. The bummer is that FF failure can occur at awkward moments like when you are in a tight bank with a 109 on your tail---wobbling is not an option. I'll do that loop, Artist. The weird business with the bombers was that they were not arming with bombs---how did I know? I selected the Ju 88 and tried to arm it with external bombs. This worked for awhile and then I ceased to get external or internal bombs. I made presets of various bombers but they stopped working. When your 88 did not have its requested external bombs, you can be fairly certain the problem is that the bombers are not loading bombs. Somebody posted on the Team Fusion site choosing alternate bomb loads is often difficult offline but works all the time online. As for the CH gear. I tried eliminating all settings for the single throttle before setting up the CH quadrant. Did not work. Also got rid of Anthro. Made no diff. Was easier to just stick with the CH single throttle, CH pedals, and Microsoft FF stick because they all worked (except for FF denial). I will be interested to see if the reinstall of Windows kicked the gremlins out of Clod. Was odd ROF ran fine except often denying me an external view. Last edited by leitmotiv; 06-19-2013 at 06:51 PM. |
#9
|
||||
|
||||
![]() Quote:
Load and save the bombs in fmb...use CH software for the quadrant set up, then download it...if I had a FF here I would explain how to get it working ![]()
__________________
GigaByteBoard...64bit...FX 4300 3.8, G. Skill sniper 1866 32GB, EVGA GTX 660 ti 3gb, Raptor 64mb cache, Planar 120Hz 2ms, CH controls, Tir5 Last edited by SlipBall; 06-19-2013 at 08:05 PM. |
#10
|
|||
|
|||
![]()
I always use the CH Manager. I'll see how everything works after the reinstall. A guy on the Clod Mods forum claimed the trouble is in the code used by 1C for devices in IL-2 and Dover. He came up with a fix. Bit out of my skill sets.
|
![]() |
Thread Tools | |
Display Modes | |
|
|