aledmb

se tiver algum brazuca ae... sou de itajai, sc. mande pm. abraço!

yeah that's right! the G25 also has a "combined throttle and brake" option. but the brake pedal is too stiff compared to the throttle and that's bad. the solution i posted combines the throttle with the clutch, instead. thanks for your reply!

hey, you see what i meant now? that's what we need to "hear" from the manual. just put a side note here and there explaining why the switches are not functional and we're all good to go. case closed. :smilewink:

hi, i don't know if there's a thread on this here. i searched for "g25" and nothing showed up, so... for those who do not have rudder pedals, here's a way to simulate them using the clutch and throttle pedals of a Logitech G25 wheel (maybe this can work with other USB racing wheels too). i found this solution in another forum (don't remember where it was now). first, download these 2 apps: ppjoy (http://www.simtel.net/product.download.php?id=75176) glovepie (http://carl.kenner.googlepages.com/glovepie_download) the whole trick is to create a fake joystick with ppjoy and then map the two axes (clutch and throttle) of the G25 controller to an axis of this fake joystick using glovepie. here's how to do it: 1. install ppjoy. 2. go to "Control Panel" and click on "Parallel Port Joysticks". 3. click "Add" to add a new controller. 4. leave all parameters to their default values and add the controller. a new virtual joystick will appear. 5. install glovepie. 6. go to "Control Panel" and click on "Game Controllers". 7. take note of the sequence of controllers you have. take a look at my sequence, for example: [indent]Thrustmaster HOTAS cougar Logitech G25 Racing Wheel USB PPJoy Virtual joystick 1 [/indent] in this case, the G25 wheel is controller number 2. 8. open glovepie and paste this script into it's window: PPJoy1.Analog0 = 0.5*Joystick2.z - 0.5*Joystick2.slider9. change the number of the controller in the script according to the sequence number of your G25 wheel (Joystick1, Joystick2, Joystick3, etc.) 10. click "Run". 11. go to "Control Panel" and click on "Game Controllers". 12. open the properties for the fake joystick you just created (PPJoy Virtual joystick 1). 13. depress the clutch and throttle pedals and the X axis will respond accordingly. 14. launch DCS and go to "Options" and then "Controls". 15. in the "Category" combo box, select "Axis Commands". 16. configure the "Flight Control Rudder" axis using the PPjoy Virtual Joystick 1 column. as you can see, the expression assigned to the X axis of the fake joystick combines the input from the throttle (z) and clutch (slider). when you apply the same travel to both peddals, the fake axis remains centered. when you favor one of them, the axis moves to it's side. i hope someone will benefit from this as i did. :thumbup:

man, you're going too far on this thread. read the first post and think about what you're saying. i didn't wanted to start a childish discussion like this. have a nice day. :thumbup:

yeah, i think only rFactor can deal with DCS. i don't know which one to choose... the best thing in it? the ammount of systems to learn and the time it takes.

well, i just asked why some switches were not implemented. now i have an answer, though not from ED. in any case, they don't have to explain anything about this. their simulation seems to be the best one to date. and that's why i dedicate myself everyday to learn more about it. i hope this discussion ends in a way that everyone gets pleased. thanks for your attention, guys!

that's what i thought after posting this thread. the pilot doesn't need to perform all those built-in tests himself. i just want to let you know that i'm not complaining about this here, because i know the whole Ka-50 is there. i mean, all the basic and advanced features seem to be implemented and that's what we want. at least, i don't need fancy things in the sim like hearing the pilot whispering to himself "damn, it's really hot in here..." i would suggest that you put these considerations in the manual, like a topic explaining which systems were not implemented and why. just a thought.

yeah, that would be fair, taking into account the number of systems we have to learn just by reading the manual. i can't help but compare this to the Falcon manual... that one seems to be more of a tutorial. this looks like a reference. anyway, i like the text... it's very well writen! sorry for going off-topic again. :pilotfly:

hi, reading through the flight manual, i found several "not functional" switches and knobs, some of which are not clickable (not green) and others look like any other implemented one. i have noticed that, in the vast majority, they would perform built-in tests and are located in the rear auxiliary panel. as my experience with flight simulations is almost none, i would like to ask: why are there so many not functional switches? will you implement them in future patches? forgive me for asking this, i know it's a noob thing... :doh:

hi RedTiger, i'm sorry, but i think the 6DOF clickable cockpit is certainly one of the best things that happened in flight simulation in the last years. what happens is that certain technologies (touchscreens, HOTAS controllers, etc.) are still too expensive for us gamers. i'm approaching this with a mix of head tracking (to turn my head in the direction of the switch i need) and a knob on my hotas to zoom in/out. works fine after some practice. cheers!

hi, i would like to suggest that you update the pictures in the english manual to reflect the actual cockpit (which is in english). i mean the text on the gauges and switches is in english. it would be nice to have those russian names removed from the text aswell. thanks!