AlexCaboose

Loco F-86

Name: The State | 1st Lt Loco Squadron: The State Country: USA

Wags looks much better. I tried to replicate this around 10K ft (since I don't believe the USAF tested 9Gs at 240ft ASL). You'll see that even after G-Warmups, I black out much more quickly and lose speed much more rapidly. What you've shown in the clip Wags posted looks correct, but I really don't think that's reflective of what is in DCS currently on the Open Beta live branch (not the dev branch). G Pulling.trk

I was mistaken. After checking the mission again, the Viper started with about 4700lbs of fuel.

Both jets started with full fuel. With the 2.5.6 adjusted fuel flow, the Viper was out of fuel long before the F/A-18C. Even at near empty (1000lbs or less), the Viper could not sustain proper G and the F/A-18 had no issues keeping lead.

Was doing some dogfights with some friends in 2.5.6 and it appears like the Viper is losing speed very quickly vs 2.5.5. The Hornet had no issue maintaining lead, and even at the Viper's corner speed, it wasn't able to sustain near enough Gs (5-6G at corner). Perhaps someone with more technical knowledge available at hand can also submit some proof that the 2.5.5 Viper seems to retain energy a lot better. I have a .trk file but it seems to be too large to submit so I have uploaded it here: https://mega.nz/#!sYwTCJrL!sKcpbrMR7U2q5MTC0h6QUwGehCwlveNbul2uzfiSCqo

Not really, because the jet has to be prepped for that. It should be fine for air to air things, but things like JDAMs when they come out would be degraded

I use a side stick setup - RealSimulator FSSB R3 Lighting force sensing base + RealSimulator F16SGRH - Collector's Edition. The stick includes the forward tilt built in.

I placed my pre-order back on July 10th. On the one hand, it's awesome that the reviewers have had contact with WinWing throughout the whole process. But I think it definitely makes it impossible to write a review without bias on unfinished hardware that isn't even the same as the customers get. Furthermore, as nice as the response seems to be from WinWing to the reviewers, it's been a total opposite from a customer standpoint. We're constantly told shipping is just a week away, or it'll be ready at day X. And then silence follows for a month until we get another update. Except for vague posts of things are being worked on. I'm sure the product is going to turn out great, but WW really, really need to hire an English speaking PR guy who is forthcoming and honest with realistic expectations for ship dates. It's better for a new entrant in the space to under promise and over deliver. What we have seen is the complete opposite, and leaves a sense of distrust and questions. I've spent over $1K on this HOTAS back in July for a product that was supposed to ship in August. At this time, I can't tell you when it will ship. Supposedly it's soon, but realistically, who knows.

Regarding the harrier - What is the difference between v228 and v235a for the Warthog?

Is the viper just running on the directX profile atm? Edit: nvm, I'm dumb.

Nope. And I have read the install instructions, checked the .luas as noted etc. There were other people apparently having issues last night on the Blue Flag server, so perhaps it was just a temporary thing.

I haven't used SimpleRadio in quite some time. I just got on the Blue Flag server in an F-15C and this is what I'm seeing when trying to tune the radio. Help please?

Just got the profile installed today and absolutely love it so far. One thing I've noticed though (and I've only tried out the F-15 atm) is that the slew seems incredibly fast. Any way to slow it down?

Sweet! That actually worked. Edit: I think I spoke too soon. I can't seem to get the weapon release command to be recognized unless I physically hit it on my keyboard =/

Yeah, it's through the Saitek software. As an example, the following is me holding my hat switch: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ^The above line was probably through 0.25-0.5 seconds of holding down the hat to the left. In game, that would obviously move the radar pip. THe issue is that in game, it really doesn't move. It registers a press for the tiniest fraction of a second and basically does nothing.

It's definitely not a keyboard issue per say: The joystick buttons are mapped to keyboard commands. Using only the keyboard works as intended - the keypress is "spammed" while holding it down and things move normally. Outside of DCS, the joystick registers key presses as intended. I've tested it in a number of software programs. As an example, pressing the trigger inserts a space repeatedly. The issue only seems to pop up once I load up DCS and attempt to perform an action. It's as if holding it down only registers a keypress once every few seconds. I'm scratching my head, and I really have no clue whether or not it's an issue with the X-55 itself or in some way Win 10 handles this sort of thing. =/

Apologies if this is posted in the wrong forum area. Anyway, I just upgraded to Windows 10 today and began testing as usual in DCS. I've already noticed some significant issues though - I'm using AceRevo's F-15C profile, and while in game, key commands that used to spam themselves (i.e. radar movement, gun fire, etc) now seem to only work intermittently. Perhaps 1-2 registered keypresses every 10-15 seconds (although a bit faster with the cannon). Does anyone know how to fix this? I've already checked the windows control panel and tested the joystick outside of DCS, and the "Keyboard Repeat Rate" is fine anywhere but inside DCS.