stubboyo

Cursor Enable is activated by pressing down/in on the cursor control on the throttle in the real Viper. It remains WIP for DCS. It should switch between BORE and SLAVE modes for the AIM-9 when held while in Air-to-Air mode. It should also toggle sub modes for the AGM-65 when implemented. While it’s nice to have, having full cursor control is more important in my estimation.

Currently, in DGFT override mode, you have to use the MFD button to change the AIM-9 from SLAVE to BORE mode. Since at least the Mid Life Upgrade Tape 3 there is a HOTAS command for this: press and hold Cursor/Enable (cursor Z) to switch to BORE if SLAVE is selected, or SLAVE if BORE is selected. http://falcon.blu3wolf.com/Docs/MLU_M3.pdf (page 8) This likely represents an older tape than what is modeled in DCS, but it seems unlikely this functionality would have been removed. This allows the pilot to very rapidly select DGFT, use the HMCS to designate a target for an AIM-9, and engage. -Rabbit

The delay should probably be even longer than that. Pilots talk about up to 3 second delay for the missile launch: http://spotter-ssol.blogspot.com/2012/06/kosovo-mig-kills.html "When I pressed the pickle button, it seemed like an ETERNITY before the missile actually launched, but when it did...WOW!!!!" https://www.thedrive.com/the-war-zone/14344/heres-the-definitive-account-of-the-syrian-su-22-shoot-down-from-the-pilots-themselves "Mob quickly selected an AIM-120 AMRAAM and fired once again. He noted how long it took for the missile to fire off the Super Hornet's "cheek" station located along the outer edges of its air intakes"

If you load the .luas they should already be bound. Are you using the axis assign screen instead of just they button assign screen? I may have used the wrong binds for the parking brake - you can just put the brake on, not take it off. I also used a bind for the idle detent that only allows you to start the engine rather than turn it off - this is nice so you accidentally don't turn off your engine, but requires you to use the keyboard for shutting down. Hope it helps.

https://1drv.ms/u/s!ApPsQLVO18yXhF9wGWsZzbQMrUfA?e=7fBh3l Here is a layout I made for the X-55 for the Viper. It is originally based on Snelle's layout for another sim, but I made several changes. You will need to run the registry fix included that make the mouse nipple bindable as an x- and y- axis. This regfix is Snelle's and not mine at all. I would link to his original work, but that's a no-no. I also never installed the Saitek / Logitech software - just plugged in my stick. While you lose the ability to do advanced programming for the stick, you're saved from having to deal with H.U.D. and a lot of other headaches. Also this way you can bind the Mode switch to Master Arm / Safe / Sim, which is super cool. I included binding for the comms switch (VHF/UHF), though this isn't really necessary in DCS until they get the integrated radio working. I also use the paddle switch as a shift layer, as there weren't quite enough buttons, and the autopilot override is not used that commonly. Binding for the X-56 should be very similar, but you can move the CMS functions from the throttle hat to the stick's side hat to more closely mimic the real HOTAS. I added the arrow keys as the dobber on the ICP and the numpad keys as the main ICP keys. There are .luas for the keyboard, throttle, and stick, as well as the regfix and a diagram included. Edit: I swapped out the gsheet for a .xlsx file. I hadn't realized the gsheet was just a link. Let me know what you think F16C X55 profile.zip

This looks good. Thankfully the SSC is the same for the Viper and Hog. Would you consider adding Master Arm / Safe / Sim to the Flaps control? It seems natural and would be nice to have on the HOTAS. I'm guessing your have rudder pedals and your wheelbrakes are bound to these. The real HOTAS does not have it, but I like having a trim reset option - maybe that could be the CMS push function. Rather than binding the button to eject, the Viper has a large Emergency Jettison button which is very helpful when you're jumped by something. Again, fumbling with the mouse and trying to mash this button is not fun. Other things I have bound to my X-55 throttle: Parking brake - nice not to have to fumble for the mouse for that one and roll forward,. Manual pitch override switch - a lifesaver if you find yourself in a departure Cat I / Cat III toggle - this is very helpful to have so immediately after you drop your ordinance you can do some fancy pilot stuff to keep from getting murdered. - Stubboyo

For those of us that don't have a suitable control on our HOTAS (X-55 / X-56), it would also be nice to make it bindable to a single button as a 3 way toggle which advances with each press: DGFT -> MRM -> Off

People (like me) who have been using the other F16 sim for a while have found a way to do it: You can get pretty close with the X-55. It has the right number of hats and buttons in all the right places, except for CMS - I just bind button C to the Slap Switch which will allow you to run a countermeasures program. The throttle is also pretty close, with the two rotaries (Range and radar elevation), as well as a hat that can serve as speedbrake, and a ministick with a cursor enable button. You have a two way instead of 4 way comms switch, and no good way to do the DGFT/MRM override switch. I have that bound to the roller on the left of the throttle with a shift state to cancel it. I have yet to come up with anything useful to do with the slider.

The F-16C can no longer use Sparrows (AIM-7) due to incompatibility with the wiring of the pylons.

Thanks for your ideas. I ended up taking my stick apart, figuring I would replace the trigger switch (it's a Tiaihua microswitch, the type usually used in mice link here). I ordered 2 from China and put my stick back together to fly while I was waiting for them. The problem fixed itself.

Thank you for your suggestions. The command I was binding was "Second Trigger Detent" which I was binding to the trigger button on my X-55. The behavior for the knobs seems to be to continue to increase while the appropriate button is pushed. I bound the trigger to the light on/off switch and it demonstrated the expected behavior - one click on, one click off. Holding the trigger down did not lead to rapid flicking of the switch. This behavior is not replicated in other modules - the missiles in the F-15C behave as expected with one release per trigger pull (no Macross mode) -stubboyo

I'm enjoying the Hornet with my X-55. All of my binds are working great (including the Mode switch for master arm), however I have a problem with the binding for second trigger detent - when I pull the trigger to launch an AA missile, it rapidly fires off missiles for as long as I have the trigger held down. This happens very quickly - even a very brief squeeze (<100 msec) will often launch 2 missiles. I know this is not the usual behavior for the Hornet. This does not happen when I use the space bar or an alternate button on my HOTAS, but it also doesn't appear to be an issue with my stick - it tests find in H.U.D. software as well as the Microsoft control panel, without any missed or duplicated inputs. Does anyone else have this issue? I think the real aircraft has a delay after squeezing the trigger before the missile comes off (which can be up to a second or more with the AMRAAM). In the mean time I just pretend I'm in a VF-1J and I'm fighting Zentradi...

If you download the regfix ministick from this site, it will add your mouse nipple as a 2 axis controller you can bind to your TDC. This means you don't have to use the Saitek software to create bands or anything and you get some good analog input. https://www.benchmarksims.org/forum/showthread.php?24506-X55-keyfile-Full-DX-Programmed&highlight=snelle I like using the mode switch as Master Arm. It is bindable just like any other button provided you select "Clear" after right-clicking on the Rhino profiler icon in the notification center. I still haven't figured out how to bind the push button next to the mouse or the scroll wheel on the throttle.

If you download the regfix ministick from this site, it will add your mouse nipple as a 2 axis controller you can bind to your TDC. This means you don't have to use the Saitek software to create bands or anything and you get some good analog input. https://www.benchmarksims.org/forum/showthread.php?24506-X55-keyfile-Full-DX-Programmed&highlight=snelle I like using the mode switch as Master Arm. It is bindable just like any other button provided you select "Clear" after right-clicking on the Rhino profiler icon in the notification center. I still haven't figured out how to bind the push button next to the mouse or the scroll wheel on the throttle.

The Rift doesn't work like that. The screen is horizontal and divided in half, one half for your left eye and one half for your right eye, so you get 960x1080 per eye. However, the lenses make it so your field of view is nearly 100 degrees, yielding a relatively low pixel-per-degree. I've been playing around with the DK2 and the resolution is just low enough that you can't read the HUD, making it challenging to fight and fly effectively. The immersion is astounding, though. When the first consumer kit comes out, hopefully with high-resolution bespoke OLED panels, this will be amazing. -stubboyo

We should be able to give this a try in DCS World. I think we'll find it's pretty easy to take down a Predator in a Su-25 - get on its six and line up. If you miss, it's not like the Predator can engage in dramatic BFM - you just circle around and have another go. I think the Iranian pilots were just showing some bravado rather than trying to actually down the drone.

I have exactly this monitor. It's great for flight sims (both DCS and BMS) and really increases the immersion. I'm running it on an i7 860 / Radeon HD 5850 at 2560x1600. I was running 1920x1280 on a 24" monitor before with good framerates. I had to slightly drop some settings to get the same FPS, but really not nearly as much as I thought I would. For gaming the 3007 is superior to the 3008 (and most other 30" monitors) because it doesn't have a scaler / OSD -- it simply displays exactly what it receives from the computer. This means there's less display lag. On the other hand the display is so ridiculously large that for fast-twitch FPS games you might be at a bit of a disadvantage because it takes your eyes longer to move around the screen. One issue with the 3007 is that there's some backlight bleed in both lower corners. This is only really visible during night missions. Hope this helps, -Stubboyo

The X-65 looks very nice and I've been stalking them on Ebay for awhile. I see a few problems though. One, it doesn't have a 2 stage trigger like the X52 pro or the real Hog. To use the gun properly, you need to be able to engage PAC1 by pulling the trigger to the first stop, and then engage PAC2 and fire it by pulling it the rest of the way. I think you'd need to use shift states (like pull the trigger while pushing the pinky button) to emulate the 2 stage trigger. The no-movement on the stick is another issue. While the force sensing technology is quite cool, I think it would take some getting used to and it's not at all like what the real Hog has. I even think that fighters like the F-18 and F-16 which have force sensing sticks actually have some movement in the stick. I think that the advantages of the X-65 don't justify the additional cost over the X-52 pro.

If you're using the SST software, by default the Mode switch just presses and holds down whatever button you've assigned to it. I learned this the hard way after assigning the Modes to Control Up, Control Down, and Control Right. I chose the profile and immediately my desktop started going crazy with icons being highlighted. To make the Mode switch useful, choose Mode 1, Mode 2, or Mode 3 in the vertical column in the SST software. Right click and choose "Advanced Command" and then in the "Press" box input the command you'd like that Mode position to use (I have mine mapped to the AAP panel).

I would recommend upgrading the graphics card. I think it's the primary bottleneck in your system now. From this chart you can see the 3850 scores only 10000 in 3DMark 06, well below most recent cards. This card also has only 256 MB of memory, which will easily be overwhelmed by the textures in the game. I run a Radeon 5850 which handled the game quite well until I upgraded to a 30" monitor (oops). The 5850 quadruples the amount of graphics memory and more than doubles the 3850's performance. They can be had for around $150 on ebay right now

To use the ministick you'll have to use the SST profile editor. Open the editor and scroll down to "Mouse X Axis" and "Mouse Y Axis." Right click on the name of the axis and choose Bands. Then arrange the bands as you'd like (I have 33% and 66% as my break points). You can then assign the upper and lower bands to the keys you use to slew left, right, up, and down. For me the X axis is for up and down and the Y axis is for left and right (not intuitive). You also need to make sure you have the most recent drivers installed -- the ministick shows up as the Saitek MagicMouse. -stubboyo

To correct the throttle assignment, go to Options>Controls>Axis Assign (it's a button towards the bottom) and then choose "Throttle Common" in the X52 column. This needs to be set to JOY_Z (the Z axis of the joystick is the throttle, apparently). The X52 is self-calibrating, just move it all the way forward, and then in a circle twice. This should recalibrate it. You can also look in the Saitek control panel -- it looks like a little throttle in the Alerts area of your Windows desktop (usually in the bottom right next to the clock). In that control panel it shows if the buttons are being pushed and where the stick it centered. Make sure your flaps are retracted. You'll also need to trim for level flight. If you don't have one already, here's a link to my X52 profile: http://forums.eagle.ru/showpost.php?p=1212158&postcount=52

I believe there's a setting you can change with the HUD in TEST mode that makes it so the SPI symbology is not occluded by the gun pipper (so you'll still see the diamond when you're shooting at it). Try looking around in the menus there after your preflight BIT. I find that the diamond gets in the way of seeing my target when I'm in effective gun range so I prefer to have it occluded. I've likewise been frustrated by the mounted MGs. My most ignominious end was getting killed by the mounted MG on an armed speedboat. It took out both my engines and hydraulics and I wasn't able to recover from my guns pass :mad: Learned my lesson to keep a good half mile between me and those pesky pea-shooters. -Stubboyo

Love the picture for "Flight Control Emergencies" :) It's great to have the airfield plates readily available and the exhaustive checklist.

Alternate X-52 Profile This is based on Ragtag's (raggz [at] getmail [dot] no) X-52 Pro profile, but I have made enough changes that I wanted to repost it. It's built assuming Track-IR and no rudder pedals with the pinkie switch for shift. I have included both the .lua file, which you will need to load, as well as the SST profile. Basically: POV1 = TMS, shifted = trim POV2 = DMS, shifted = CMS Throttle hat = Coolie switch, shifted = Mic switch Mode dial = AAP selector (Waypoint, Mark, Flight Plan) Small rotary = landing gear control, clockwise to raise, counterclockwise to lower Slider = speedbrake (aft to deploy, forward to retract) Ministick = slew The clutch button is available for VOIP. I've attached a PDF of the full setup. Many thanks to Ragtag for the great profile! Stubboyo X-52Pro.zip