Jump to content

Recommended Posts

Posted

I apologize for the flurry of questions coming back to DCS.

 

 

I've been able to successfully save snap views on the A-10 to where I like them, binding them simply to the numpad keys (removed the R CTRL modifier).

 

 

What I'm having trouble with is getting snap views to stick. I press the R CTRL+numpad 0 combo to supposedly enable toggling snap views. It will stick to the snap view I have bound to numpad 0, but no other snap views toggle. I have to hold down the associated numpad key to view them.

 

 

Does anyone have any suggestions?

 

 

 

Thank you.

CaptKornDog

Posted

Does anyone have any suggestions?

 

 

If you use a Headtracking device, you need to pause it when using SnapView toggle.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
If you use a Headtracking device, you need to pause it when using SnapView toggle.

 

 

I do not have headtracking devices.

 

 

(I've also tried deleting the SnapView.lua)

CaptKornDog

Posted
I do not have headtracking devices.

 

Strange .. I use Snapviews a lot and they do work on my end, the keys that I press are:

 

RCTL KP0 and then KP# (without LWIN)

 

Note that the momentary snapview keybind is LWIN + KP#

 

So, I believe that most likely the fact that you redefined the default Snapview keys is messing with the Snapview toggle. Return them to the default (LWIN + KP#) and then the toggle should work.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
Strange .. I use Snapviews a lot and they do work on my end, the keys that I press are:

 

RCTL KP0 and then KP# (without LWIN)

 

Note that the momentary snapview keybind is LWIN + KP#

 

So, I believe that most likely the fact that you redefined the default snapview keys is messing with the Snapview toggle. Return them to the default (LWIN + KP#) and then the toggle should work.

 

 

No joy reverting them to default, unfortunately. R CTRL+numpad 0 sticks the view bound to LWIN + numpad 0 now, pressing any other snapview beyond that is only momentary.

CaptKornDog

Posted
No joy reverting them to default, unfortunately. R CTRL+numpad 0 sticks the view bound to LWIN + numpad 0 now, pressing any other snapview beyond that is only momentary.

 

That's strange .. I use the Snapview a lot on my flights, mostly to handle the small MFCDs of some aircrafts, for example this is on the F-16 .. I was testing my freedom of movement within the cockpit, some HOTAS binds and also the Snapviews:

 

LP1nuZ9QbaQ

 

... and I use just the default keys ... tough I'm very fortunate that my particular HOTAS allows me to place two comands together on a single button, so I can pause the headtracking and then press the keypad number in just a single button.

 

The only remaining sugestion that I have, is to rename the file \Saved Games\DCS.OpenBeta\Config\View\SnapViews.lua

 

Then restart DCS and re-create the snapview that you want to see if it hopefully works now.

Best regards,

 

Eduardo

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)
No joy reverting them to default, unfortunately. R CTRL+numpad 0 sticks the view bound to LWIN + numpad 0 now, pressing any other snapview beyond that is only momentary.

 

I’ve had same issue for years now. Worked around it with VoiceAttack which holds momentary snap till i release it with another command.

 

If you want to try that route, let me know and I’ll give you my profile. There are some tricks to it.

Edited by Chic

A Co, 229th AHB, 1st Cav Div

ASUS Prime Z370-A MB, Intel Core i7 8700K 5.0GHz OC'd, RTX 3090, 32GB DDR4, 1TB SSD, Win 10

Samsung 65" 4K Curved Display (Oculus Rift occaisionally), Track IR5, VoiceAttack, Baur's BRD-N Cyclic base/Virpil T-50CM Grip, UH-1h Collective by Microhelis & OE-XAM Pedals. JetSeat & SimShaker for Aviators.

JUST CHOPPERS

 

  • 3 weeks later...
Posted

Hi there CaptKornDog,

 

 

I had this same issue for years also! I was however able to solve it, albeit by using another piece of hardware i happened to have and some .lua code i found on the web.

 

Even after this solution i still found there are some drawbacks that make it less than perfect for what most of us would want this toggle capability for.

 

I own a Logitech G-13 Gameboard, it's a really great piece of hardware and i use it in many other games and sims. Through searching at length on You Tube and elsewhere i found out there is a Lua scripting capability with the Logitech Gaming Software that adds more advanced functions to the hardware and allows more options in your gameboard profiles.

 

After much digging on the web and trial and error, i found a ready made script for the G-13 that enables turning any key on the board into either a toggle key or a hold key.

 

This code will work on any Logitech input hardware (joysticks, keyboards, gameboards, even mouse i believe) that uses the Logitech Gaming Software. You can even add a message to be displayed on the devices LCD screen to tell you what key is currently active and when you deactivate it. It only take a few minutes of changing some text in an editor. It doesn't require ANY coding or programming knowledge at all.

 

The main "slight" drawback with using this solution in terms of DCS sims is that when you press one of the toggle keys to access the Snap View, you can then only interact with that view (click OSB's, switches etc. with mouse clicks.

 

You can not interact with it or use any other joystick or keyboard commands while in the Snap View. This is obviously due to the G-13 generating constant presses of the LWin + KP0 etc key and therefore not allowing any other buton or key presses to be generated/read by the sim.

 

As far as i know there is no way around this unless someone on here has a solution. Maybe altering some of the default DCS keyboard .lua file code might work? I don't have the knowledge to do that myself and am not going to try!

 

For any Logitech hardware users out there i'm happy to post the .lua code for your hardware to enable this capability? It's not mine, and dates back to 2013 i believe? It's very easy to set up for your hardware if you read the instructions at the top of the code itself.

 

Happy to pass on and help with set up if anyone interested. :pilotfly::)

Windows 10 Pro 64-bit - Intel Core i9-13900K - 64GB Corsair Vengeance RAM @ 3200 MHz - ASUS TUF GAMING B660-PLUS WIFI D4 - Zotac NVIDIA GeForce RTX 4090 - 2TB  INTEL NVMe SSD (Windows 10) - Samsung SSD 970 EVO Plus 1TB (DCS) - Crucial CT1000 1TB NVMe SSD - WinWing F-16EX Stick - WinWing Orion Throttle Base with both F-18 & F-16C TQS Throttle Grips - Saitek Pro Rudder Pedals - Logitech G-910 Keyboard - Logitech G-502 Lightspeed Mouse - Logitech G-533 Headset - Occulus Quest Pro VR - TrackIR 5 with Track Clip Pro

  • Recently Browsing   0 members

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