PaladinX

Just checked my settings: They are in these conditions when it happens. So im not exceeding the "recommended" settings somehow. So can you confirm im running out of memory with these settings with a 64 GB of Ram setup? This leads to sudden end of a mission and debriefing after 10-15 mins of flight?

Hi Polovski, thanks for your response. That means, the Game ends the flight and brings me to the mission debriefing because im running out of memory? Without any warning? Is there any possibility to analyse how much RAM is used in that moment? Or do i seriously have to change the graphic settings, fly a campaign mission and see if it crashes? Then start again...? my hardware: 7800X3D with 64 GB (!) of DDR5 and a 3080 Ti

Dear all, been playing WOFF since years without bigger issues. Today i updated to OTT 1.05, works fine, but - it randomly ends every campaign mission and goes into debriefing?! Example 1: Free flight, i can fly for hours without any issue. Example 2: Campaign mission, defend observation balloon, flying to the target area, circling for about 13 mins (target was 23 mins) - suddenly debriefing screen (i was not hitting any key!). Mission ended, everything fine, blabla, next mission. Example 3: Campaign mission, enemy patrol, flying over the frontline, enemies sighted, i start dogfighting (not even shot a single bullet) - suddenly debriefing screen. WTF? Is this a known bug? Some setting in the workshops?

How do you get that variometer in your screenshots HUD`?

Update: The hints regarding a button stuck was the correct one! What was wrong: The VIRPIL Constellation Alpha has a 4-Step-Trigger (!), means a lever switched forward (button 1), switched backward with contact to the trigger (Button 2), then the trigger itself (Button 3) and a second step on the trigger (Button 4). If this lever is forward, it sets button 1 to "up" --> Means its pushed all the time --> Means, when i want the game to recognize an axis, the button permanently sends data and the game does not "see" the axis im moving... When i bring everything in the standard position and all the buttons are shown as "up" - then it works. So basically my fault with the buttons on my Joystick. Cant blame the game for it!

Hello everyone, i need some support: Bought and installed WOFF 2 today successfully. When it comes to the workshop and my input configuration, the problem starts. I use: - Joystick: Virpil Constellation Alpha on a Virpil WarBRD base. - Throttle: HOTAS Warthog Throttle - Throttle: Saitek / Logitech Throttle Quadrant - Pedals: MFG Crosswind Pedals - Trim: Saitek / Logitech Trim Wheel - Track IR Problem: When i am in the input configuration and want to bind the joystick axis to elevator or ailerions, it beeps and tells me "only joystick axis can be assigned!" WTF?! The input shows me correctly that the X-axis and Y-axis move, when i move the joystick, so the axis are recognized. I tried with all other devices unplugged, only with the joystick plugged in. I use this configuration with WOFF 1, IL2 1946, IL2 Great Battles, FSX, P3D, MSFS, DCS without any issues. Why does WOFF 2 not allow me to bind my usual joystick x- and y-axis to the ailerons and elevators? PC WIndows 10, 8600K, 32 GB Ram, RTX 3070, etc... Any ideas? Regards, Jan