Jump to content

lwalter

Members
  • Posts

    363
  • Joined

  • Last visited

Everything posted by lwalter

  1. Thanks! I'll try all of your suggestions next weekend and I'll let you know.
  2. Here is a screenshot of my DCS settings I saved a track file but the flickering is not part of the track file itself. It's more of a state of DCS itself. If I open the track file while DCS entered this flickering state, then it will flicker, else it won't flicker. here's a video : flickering2.zip I could reproduce this issue with a simple mission with a plane taking off from any airport. Open the mission, fly the mission, quit, fly again, quit, mission editor, change plane, fly again, and so on, and after a while I get the flickering...
  3. Here's the mission.My WW2 Normandy Mission.miz is there an easy and recommended way to remove the MB339 mod from DCS so that I can test without it?
  4. Thanks for checking! Are you using the latest beta or the stable? The crash happens for me on the beta when starting a custom mission with my F86 ready to take off from Rucqueville. I did more checks: I tested all DCS official planes + the A4 and MB339 add-ons with this mission. All are working properly except for the F86 and the MB339.
  5. I don't know if this is specific to my config (see signature), but lately with the latest beta, I get bright flickering happening more and more frequently, usually after 20 to 30 minutes of play and when starting a new mission. I experienced it very rarely in the past but now, I'm almost sure to get it each time I play DCS. The screen flickers between normal colors and very bright ones and very rarely it sometimes get stuck with very bright colors. To fix it, sometimes it's enough to stop the mission and press "fly again", sometimes I have to go back to "mission editor" and restart and sometimes I have to completely restart DCS.
  6. Thanks to all for your answers! (@Tom, I don't have any assist on for my WWII planes) Full right rudder before even increasing throttle was the key! I also noticed that it had a big tendency to lift its nose very early and that it required lots of trimming even during normal flight. Are there any good trim settings for takeoff? I'm assuming quite some nose down at least?
  7. Does F86 work for you on the Normandy map? I've tried twice to takeoff from Rucqueville with the F86 and each time DCS crashed. FYI, I tried all the other planes I have and I don't have this issue.
  8. After some training, I managed to smoothly takeoff in the P51, FW190, Bf109, I16, but the Spitfire remains impossible to takeoff :( I tried all the techniques I used for the other planes: stick completely aft, stick on the right to avoid rolling left, small amount of right brakes, dancing on the rudder, whether applying them all or just combinations of some... nothing works. The Spitfire keeps turning left like crazy at start. Does somebody have any advice? Is there one of the other planes I could related to?
  9. Do you mean that for FW190 you need your stick fully back to lock the tailwheel? I thought I read from the manual that just a little stick backwards was enough. Maybe I haven't understood properly. I also read from the FW190 manual that you didn't need to let the stick move forward during the takeoff roll, that it was doing a 3-point takeoff. Once again, maybe I completely misunderstood.
  10. Now that I can taxi, takeoff and land the P51D almost with ease, which next WWII plane should I try? I'd like to go from easiest (I supposed this was the P51D) to hardest for taxi, takeoff and landing. These are the plane I have: FW190 Anton and Dora, Bf109, Spitfire and I16.
  11. A big thanks to both of you: yes my brake axis had to be inverted and I managed to finally land this P51!
  12. I'm new at trying to land the P51. I read several guides, watched several videos, but still can't land this plane. When hitting the ground, my speed is lower than 100 mph and my descent rate close to 0. I don't bounce, it seems almost like a perfect landing to me and then the nose decides to go down and hit the ground :( I don't break at all so it's not because I'm breaking too hard. I also tried to pull the stick fully aft, but whether I do it or not doesn't change anything. Does anybody have any clue what I'm doing wrong or what I should do to avoid this problem?
  13. Thanks so much!!!! That solved the issue! :thumbup:
  14. I reinstalled CTS from scratch, redownloaded everything (full update), but still gets this issue. The profile starts indeed and let me switch planes, but my warthog throttle is not recognized in DCS. So I checked further and this ID for which there's an error corresponds to my Warthog throttle. It's no longer integrated into the virtual controller, but stays separate.
  15. When I launch the profile, I get the following error Error: (internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404" I did a full update and retried, but same error... Is there something I could try before reinstalling CTS from scratch? my config: Warthog stick+throttle, MFG rudder, 2 MFDs
  16. I just bought the CEII and the Yak52, which are not yet supported. In the documentation, I read that you can use the generic DirectX profile, but if you want to use it for different airplanes, with different number of engines, landing gear behavior, etc... do you have to duplicate this profile? And if yes, how would you do?
  17. There are obvious bugs, like the missing kneeboard, that haven't been fixed for months. And this forum seems very quiet. Is the development team still active? Do they have another forum where they want you to register bugs?
  18. As always, you’re very reactive and helpful. Thanks a lot !!!
  19. Since I tried the I16 right after loading DCS, I switched from the default A10-C profile (the one from CTS)
  20. any news on this issue? We're in March 2020 and kneeboard still doesn't display, neither with K or right-shift-K (and yes, these keys are associated with kneeboard display commands in my settings and they're recognized in the settings)
  21. Selecting I16 profile returns following error: "Runtime Error: Divide by zero in AirBrakeProc ( line 1704 in DCS/DCS_Global_Subs.tmc )Aborting script (check output above for reason)... Script stopped!" My config: Warthog stick & throttle, MFG rudder pedals, 2 thrustmaster MFCDs
  22. Wow! that was fast again! Thanks a lot!!!
  23. SU25T doesn't have any bindings for the sensors (e.g. E/O, LLTV). They should be assigned to the Left MFD OSB 2-4 according to the doc. I reinstalled CTS from scratch, reloaded the bindings from the profiles, but they're still not there. My setup: Warthog stick and throttle, TrackIR, 2 MFDs
  24. that was fast! thanks a lot!
  25. Excellent! :thumbup:
×
×
  • Create New...