Jump to content

jalexb88

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, firstly I'll mention I have done the latest update which includes fixes to the autopilot. I use a FFB stick and flying with force feedback enabled along with "use FFB trim implementation" the F14 autopilot does not work properly. For example if I engage the autopilot in ALT hold mode, there is no response in pitch at all even with the autopilot engaged, ALT switch up and AP REF light out and FFB stick in the trimmed position. If I test the same thing with a non-FFB stick and "use FFB trim implementation" un-checked then all the auto-pilot functions work fine. Thanks
  2. The force trim X/Y axis are swapped on some FFB joysticks, just hit "FF Tune" and "Swap Axis", that should fix it.
  3. I believe this is already implemented when using a FFB stick. On mine I can feel a detent that I have to "push" through to get larger roll rate.
  4. I just got the joystick yesterday, feels amazing Yeah, that's what I had in mind about the yaw axis, just something simple should suffice, maybe with very basic configurability (adjustable spring strength slider, force curve) but I understand that it would be static and not reading anything from the sim. I would be glad to test! Thanks again
  5. @Chuls First I want to say thanks for the great work on getting this to work! I've been holding off for years to get the Brunner base but now that there's BrunnerDX, I've gone ahead and ordered the CLS-E joystick. I think someone mentioned it earlier, but could BrunnerDX implement basic handling of the yaw FFB? I think I read that DCS does not support FFB on the yaw axis, but maybe BrunnerDX could send a static "spring" effect or whatever with an adjustable slider to the Brunner yaw axis. I have the CLS-E rudder pedals and unfortunately when using CLS2SIM in remote mode, the yaw axis FFB is 0 unless the controlling application (BrunnerDX) sends something to it.
  6. Sounds like you're getting caught on the backside of the power curve. Especially at high altitudes, any aircraft will struggle to re-gain airspeed if you let the speed fall too low, that's a pretty realistic effect. Once the airspeed does get up beyond a certain threshold things get easier performance-wise. That being said if you were unable to crack 200 knots in level flight with full burners, that does sound suspicious...too heavy maybe?
  7. Yes I have checked again and indeed its just the scaling in AA and Cruise being different. No issue at all finally, the pitch ladder is correct. It was the rate of movement of the pitch ladder in those 2 modes that was putting me off (slower) but if I compare the HUD with the VDI, there is no error. Apologies and thanks for pointing that out. :)
  8. I have a weird problem with the latest update: When I set the HUD mode to CRUISE and AA, the pitch ladder does not follow the actual pitch attitude of the airplane. It moves too slowly and the ladder becomes severely misaligned with the actual pitch. This does not happen in the other HUD modes.
  9. While the recent update fixed my CTD issues for the most part I got a CTD today during a quick mission I made (single player). The CTD happened right when I saw a missile hit me. This is version 2.5.4.29004 and I included the log. dcs.zip
  10. I have this happen sometimes as well... I dont think its fps issues, just the head tracking that gives stutters... Yep I have tried that and 1 times out of 3 it will fix the problem. Also alt-tab out of full screen, then doing as described (removing, waiting, then putting it back on) then returning to full screen seems to also fix the issue...sometimes.
  11. I am no expert on the F-14 and like you say the wings may snap off a bit too fast, but here is my opinion on this: To get the same deflection on a real F-14 stick as you get on a PC joystick probably takes much more effort, especially at higher speeds. A real F-14 pilot may find it easier to judge how much stick defection is too much (combined with Gs of course). Force feedback joysticks may help in this regard, I miss my old MS FF2 :(.
  12. Very impressed overall with the F-14! I have however been getting random CTDs. It only seemed to happen during a few sessions here and there before the latest update (March 22) But now it seems that the CTD frequency has increased with the update. I have tried to get the crash logs but for some reason I am not finding the logs "Saved Games\DCS.openbeta\Logs" Any Ideas?
  13. Ok, I got it working. The reason BS 2 was not being recogmised in DCS world was because I had downloaded the wrong version (1.1.1.1) with DCS world 1.2.2. I then downloaded the file KA-50_bs1update_en_1.2.2.7570_69.exe and THAT version with latest DCS world works perfect even with the upgrade BS2 inside DCS world.
  14. Hi, I have the upgrade BS2. I did have DCS world 1.2.2 installed before I put in KA-50 1.2.2, but Ill try uninstalling everything and reinstalling and see if that does it. Thanks!
  15. First off this is some of the best combat simulations I've had the pleasure to try. However, after a few months with the A-10c I've decided to upgarde my old Blackshark to BS:2. HOW do I get this thing in DCS world?? OK, heres the order in which i've done things. (Already had latest DCS:world and A-10c intalled.) 1. Ive installed BS:1 and registered it. 2. Installed BS:2 upgarde and registered it... but it works as a stand-alone product. Thought it was an addon for dcs world? How do I get BS:2 working IN DCS World?? IE selecting KA-50 along with A-10c, etc. Thanks for the help! :)
×
×
  • Create New...