Jump to content

Recommended Posts

  • Replies 580
  • Created
  • Last Reply

Top Posters In This Topic

Posted

A 9th Air Force, 36 Fighter Group, 22nd Pursuit Squadron P-47D flies over members of the 29th Infantry.  July 1944.

I hate the default 101st for everything.

Screen_240821_142141.png

  • Like 3

"A plan is a list of things that wont happen"

DCS banner.jpg

Posted (edited)

 

Edited by Nazgûl

LOMAC, FC, DCS, AV-8B, F/A-18, F-16, AH-64, Super Carrier, Persian Gulf, Syria, Kola.

i7 12700K, 4070 Ti PNY XLR8 OC, 64 RAM DDR4 3200, B660M Aorus Pro, 1T NVMe Kingston Fury Renegade (DCS), 1T NVMe Kingston NV2 (OS), ASUS QHD 31,5" VG32VQ1B, VKB Gladiator Pro (metal gimbal) + Kosmosima grip, CH Pro Throttle, TIR 5.

 

Posted
 Haven't done a proper DCS video in almost a month with family vacation, there has been little time to spend hours editing videos.
 
I took out the Apache a module I’m absolutely not great at, but we did put warheads to foreheads, protecting the Chinook MEDEVAC, as they picked up 3 wounded British soldiers, in the process we neutralized the Taliban threat that had attacked the British land rover column.
 
As I went in for landing, I discovered I had a deadzone on my collective exactly were the hover point was with the current weight of the helicopter, ground hover seems to be around mid 70s power, but my collective jumped from low 70s to mid 80s, meaning I either fell too fast to the ground or shot into the air. Concentrating on my collective and trying to find that point, I naturally paid little attention to the cycling and things went downhill, but I did manage to get back into control, and did land okish, no damage.
 
Sucky landing on an otherwise very successful mission. 
 

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted

Panavia Tornado P200 IDS MFG32

Windows 11 Enterprise 64-bit processor AMD Ryzen Threadripper 3970X 32-core processor 3.90 GHz, installed memory 256 GB (256 GB usable), system type 64-bit operating system, x64-based processor
2 x NVIDIA RTX TITAN SLI 48 GB vRAM, 3x 2 TB M2 NVMe WDS200T3XHC Raid, 2x 4 TB M2 NVMe Force MP510 Raid, ERM - 3K3U water cooling, gaming motherboard ROG ZENITH II EXTREME ALPHA
Monitor 108 cm ACER PREDATOR CG437K 7680x4320-120Hz, power supply 2000 watts

Posted

So the Winwing MFSSB base for the F16 is a cool piece of hardware, however there’s always been something off.

 

The “realistic” mode seem to be anything but realistic according to F16 pilots or pilots who have flown civilian aircraft with a force sensing stick. The force only mode seems to the most realistic one, but it has a serious downside and that is the fact the MFSSB has big nasty dead zone, the completely ruins how it’s supposed to be, trying to do accurate flying like AAR with a big ass dead zone isn’t very nice.

 

So many have used the movement + force. But that’s not ideal either.

 

I’ve had the MFSSB for almost two years now and never quite been happy with it. I got kinda used it it. But it always felt off.

 

I regularly goodled and asked others what settings they used to get the base working right, and you have as many answers as people.

 

Then doing one of my semi regular googelings I found out that for like a year people have found out the dead zone is because of a giant gap(2-3mm) between the roller bearings and sensors, that causes the dead zone as the force sensing won’t kick in until the roller bearings hit the sensor. There are several ways of fixing this, the MacGyver way just shove anything between the two bearings and the sensor, you can use a 3d printed part, or you can even use metal.

 

I did the cheap MacGyver way, and cut small strips of plastic from some random battery package, 3 layers of this thin plastic works well, so 6 small strips. And it works, it really does, dead zone is gone. The F16 answers as soon as you start using force on it.

To test I did a quick and easy dogfight with a MiG29. With some acrobatics and low flying to test the stick after winning. Stuff like trying to hit a slow moving damaged mig with guns used to be kinda a pain, with the dead zone, so getting the thing on the thing could be more complicated than it should be. But it was much easier now.

 

So in case you are using the WW MFSSB and have that problem with the base, just find what solution you want, shove it in there, and set the settings to force only and everything is great now.

 

 

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...