void68

Well, like Exorcet said... it's nicely simulated on first sight. But there are quite some unnecessary bugs that tear my hair for a year: TGP problems, Maves not boresighting, inprecise precision ammunition and lots more. Still it's a superb aircraft to fly - you should definitevely try it and join the band of the desenchated... the more money they got from us the more they owe us!

Check for the "DATA" text on your HUD once your teammates have sent you some interesting information and look for the "+" or "x" sign on your HSD. Verify your XMT button (right upper button #6 or #7 I guess of the HSD page) is set to L16 or something and not "OFF". I don't recall the exact terms, I am not in my F16 ATM.

Did you perform a "check program integrity" or an update (perhaps a hidden one)? That defaults your .lua.

You proved me wrong... No, I have none, not yet, but you just made me a new project. However the starboard side is my cockpit entry, and it's already cramped like hell, forces me to stay somewhat "slim". I fear I have to climb a ladder into the cockpit soon...

No, it does not work. Not at all. Not with the current stable version. If you like open beta, then you will get boresighting.

Sorry for confirming my own opinion / knowledge :), but I got the usual "full movement stick" accessories (or better: for Force Sensing removed parts like cams and springs) in an extra package. I don't recall if it was the extra package with 3 different cams and springs or just the spare parts. Also telling from Winwings h/p you can change back to full movement stick. However: Winwing wrote that they don't recommend installing the MFSSB on your own, in fact it came installed. So it looks like it's a one way street. Once back you are lost. No knowledge of installing the force sensing module myself. c) option just gives you the movement within 5mm range, i.e. 5mm range for full deflection of rudders, no matter how much expo, that's insane. And no, that's not like in the real F16. It's option a)

There is a "cheat" mode like "MFD / HUD only view" (CTRL+F1 or so, can't look ATM) with a full front view with just the enlarged MFDs and the HUD visible. I use this a lot, cause in VR the MFDs' content is even hard to recognize and identify. Also you can do a Zoom Into for better resolution. Still it's hard to find targets through the ground clutter like trees, rocks, buildings. I think that simulates real life problems - your targets will do almost everything so that you don't see them. Same with IR (or radar), the days are gone where vehicles are so much hotter than their surroundings. If you take a parked truck the IR signature will match the surrounding temperature but the black, in sunlight heated up tyres will shine bright in (WHOT) IR. Impressively realistic. Try an (IR) Maverick - D in plain daylight desert and the seeker gets a pretty hard job finding a proper heat signature. That's what the MFD's brightness, contrast and IR intensity (and radar gain) switches are for. Play around with the settings in WHOT, BHOT and TV mode and you will notice that a proper setting will result in the target gets killed rather than you. With old, more arcade like flightsim times an IR sensored weapon "saw" every tank all the time, it was always the best choice (even in the old Falcon 4.0). With the actual F16 / Mavericks I prefer TV guided most of the time and choose IR only for night missions (well, I don't use Maves at all ATM due to broken boresighting) or in winter conditions. I still have to figure out if vehicles change heat signature in relation to cooling down after travel. SAM launchers (the launcher ramp) are pretty cold, as they just sit and wait and are powered via a remote generator with litte "garbage energy" like heat losses. A tank in full speed is a very hot target. The right mode, the right sensor, the right weapon, that's the key.

Boresighting was messed up with latest stable release. However it seems it has been fixed again in the actual beta but I can't confirm (as I usually don't play betas... usually but nowadays I hardly find any software that isn't in lifetime beta stage if applying last century's standards...)

I think it's for convenience: First usually we aren't trained F16 pilots and some of us are pretty limb in their arms. Imagine pulling a 10l iron bucket of water upwards each time you do a high G pitch... second real life F16 got an armrest to support your just back-for moving arm while I doubt that even in a simpit anybody built an armrest for support and help pulling 11kg out of your shoulder / upper arm joint subscapularis muscle. And 7kg for rolling, power originating only either out of your hand joint or elbow or the same, now doing inefficient rotational work subscapularis muscle... that's quite a lot.

From the Winwing site, haven't found the original quote, however. Telling from my experience I can confirm that the extra movement comes in quite handy.

I might be wrong, but itsn't it meant to move that 5mm for microcorrection, hit the boundary and then it's only the force "on top". You need very little force to move the stick what makes it fine for ... fine tuning, while after a certain amount of movement you need force? I think that's exactly like it's in the F16? Perhaps we misunderstand each other. Well, give the Winwing a closer look into its configuration, perhaps it might help :).

That's a feature. You can choose between 3 different settings: a) 5mm movement like a default stick and then force sensing b) no movement and only force sensing c) just movement (I think, can't verify at the moment) I read that a) is the real steel feeling of the F16 as they noticed that pilots like micromovement over micropressure but that can be wrong(*). Telling from personal use a) works very very well. Can't say anything negative about the Winwing yet apart from the lack of a proper programming software other than 3rd party. It's still compatible to usual "movement" joystick behaviour by deconstructing the MFSSB and put the different springs and CAM back into the body. China quality seems to have improved to somewhat... menacing. Complete F-16 set throttle and stick for 770€. edit: * just read at the RS homepage itself that my assumption is right. There is real movement, so Winwing (and RS) is reflecting this correctly. Also the Winwing FS can be adjusted on how much force input is needed for what output.

So what AG ordnance do you use with Mavericks broken, CBU105 broken, JSOWs broken? Not so much left despite dumb WWII era bombs...

I got the Winwing FS F-16. You are right, force sensing changes everything. However in my case it took just a mere week from China to central Europe and an additional 100€ for VAT and tax.

pre beta the Mave boresighting doesn't work. Pre latest update it worked. They already fixed it with the new beta. Wait for it when it goes final.

To the blood pressure cuffs inflate behind your neck? I don't get it, but as a testing device it sounds ok. You can start a simple Arduino program to get triggered when the chair moves back and closes a circuit and make the Arduion trigger another relay bank (switching up to 380V opto coupling) to start a compressor or something. Even with a analog read you can check how much the chair moved back and put it into an analog output.

Exactly, LeCuvier's .lua edit is the simple solution. In a simpit, you don't need hardly any key at all anymore, and there's no simple "oh, I hit the ejection button by accident". The problem with 3rd party util programs like RS Mapper is they work fine... for a certain period. They aren't maintenanced, they may be buggy and especially RSMapper collapses if one USB device gets unplugged. I tried to get rid of all these aux program and with some .lua editing (check out LeCuvier's guide!) my...5 Bodnarboards and several Arduinos don't need any intermediate program anymore, not even for 3 state switches. Just remember to edit the ...\DCS World\Mods\aircraft\yourAircraft\Input\yourAircraft\joystick\default.lua to route the 1x Eject directly to the joystick or boards, not the keyboard.

yes, but you can edit it, check here

Any solution for the VR players? While dragging / resizing the kneeboard with the mouse is a nice workaround still it got its hard boundaries and no way to move it to the knee. Perhaps with .lua editing, but what .lua and what parameters? Anybody did this already?

Hello Lord Vader, sure, still with 14kts it's 300'+ deviation and that's just 4Bft mid breeze. I guess with 1Bft and BA2500 calculated wind correction will be still way off target (time for another test) With insane 60kts I would understand that it's out of the limitation if the BLUs drift in a somewhat chaotic manner. But... they hit the ground always at the same spot, so there is calculation. And that calculation is wrong. Like playing darts, you aim for the bullseye and all your darts hit exactly the same 1cm² 5cm off to the right. All the time. So the shooter is excellent at aiming, he just has to correct his aiming offset. It was the same with CBU-97, always off the same distance / direction.

Thank you, I'll try once it's out of beta state.

Missed this thread, so I did a lot of CBU-105 testing in vain. However I use just preplanned, no TGP correction needed, just from the Mission Editor into flight. I just put the WP plain into the target group's center. Zero winds, full hit. 60kts wind, some logic lets the CBU fly a certain lead into the wind, it ejects the BLUs not over the target like before but windward like it should. The poles drift and explode like they should but not where they should. The higher the wind and the BA the stronger the drift. With BA1200 and ca 15° windspeed I had to move the WP around 300ft windward. So from my observation: There is indeed some calculation in the WCMDs but it's wrong - like it was in the CBU-95 before. Perhaps same cause? iooinoin.trk

Boresighting does *not* work pre actual beta and with latest stable. When you hit active pause and try it 5 times or so, sometimes it works. Has nothing to do with parallax problems if the seeker head is off several 10° degrees and the seeker head icon on the hud is everywhere else but there where it should be. I wonder why there hasn't been a hotfix yet. So there is no use going through the startup process, takeoff and try to boresight and there you are, with 6 crosseyed Mavericks. Ok, VIS and BORE aiming modes still work as long as you haven't tried to BORESIGHT them before. PRE is messed up.

I got .284 and it didn't work with native support. I wonder why PiTools didn't tell there was a new version.

Yes, of course. However in my setting the pilot has no LOS on target, so no HUD, no TGP at that altitude. Ground units tell him "bombs fall 300' short of target to the south". My idea: move SOI 300' to the north.