ivanwfr

Could be Windows with its damned access control / Permissions! Both View folder and SnapViews.lua file must have the Security Modify Allow or Full Control checked for Users... unless you play as Administrator privileged.

Would you re-read a previous related answer I could devise about this subject and the related linked discussion and report back here after some more attempts... The DCS\Config\View\SnapViews.lua file is modified with an RALT + KP0 when you quit.

Just a quick/dirty reply for you to check whether you do it right or not: 1 - Ctrl-0 is meant to be a STATE-CHANGER (i.e. it toggles from one view handling mode to another until you do it again) ...in one mode, a Numpad press-release snaps its view back and forth. ...in the other, it selects your current view. 2 - ... ... it seems you've just ruined the "tricky" intended behavior of Ctrl-0 "toggle keystoke" ;) Also, I suggest your read once more all that has been said about Snapviews in these forums a little slower as I'm pretty sure your answers are in there ... As I could do whatever I needed to automate snap views handing with TARGET, meaning that, as tricky as it is, you should get what you're looking for. ... and I think that number pad bindings are built-ins that are not open to customization as of now.

Great job Greg, I support every bit of information and advice you've outlined here. TARGET has an opened potential as the limits are only drawn by how good you are at analyzing problems to be solved and how well you master this tool. I also think that your approach may be less painful than mine as I got into every bit of grounding detail... exactly what has the best chance to keep people away from a hard journey ;) As a side note about DX Input vs. keyboard shortcut bindings, there is something worth mentioning - as a fact that plays an obvious role in keeping things as simple as they should be: The joystick has only impulse switches, meaning, they have only one stable state, exactly like a keyboard The throttle multi-stable-states switches would behave like a pressed key as soon as you don't let them play their natural DX Input ON-OFF reporting role. A good thing to remember if you want to keep away from trouble, and more so when you switch focus to some other application answering to keyboard inputs :lol:

Yea, this one should have been bold and red from the beginning ;)

Could someone please provide the link where I found this attached document by 335th_GRSwaty ? ...and as I could not resist some photoshoping, here is a clean version of this page... graphical-layout.pdf

I know, that's why I don't open my cars engine myself anymore, we have to choose with only one lifetime...

Exactly, it can detect which program has focus -- and much more reliably than Logitech Setpoint mind you! You can do layers (in the way TARGET has them) to swich between generated event for any single key... And we're not talking In/Out Up/Middle/Down! You can do thousands of those if you're crazy enough ;) Below is a short sample of my thousands of line of script. In fact you can do whatever you can conceive that makes some sense.

AutoHotkey would help you to reprogram any keyboard hardware you find to your liking. Any physical key would do anything you need at the price of having to learn how to use it - or get help to start with. It's now a few years I use it and nothing compares to this most advanced open source scripting tool.

For the passing by reader comprehension (as I know you found the answer since), T.A.R.G.E.T stands for Thrustmaster Advanced pRogramming Graphical EdiTor (taken from TARGET_User_Manual.pdf)

It's less a matter of effort than of understanding. I've spent weeks to find out what was worth to get my head around with TARGET. The way you state your issues shows you still could get much from what is explained in the manual and from trial coding to make sure you get what you read the way it has to... It's because I had to do that and I had to rummage through Thrustmaster system files to grasp most of what is too lightly described in the documentation. Your code would show precisely what you're doing, that's why. If you're interested, I have collected my findings in this thread: TARGET - Advanced programming and I'm pretty sure I can help if I see some code... Back to the point, when you think of TARGET layers (IN/OUT UP/MIDDLE/DOWN) as if they were modifiers like Control or Shift on the keyboard... well forget it! Those layers only modify things inside a TARGET script. Meaning when one or more of these modes are in effect, they can switch between several actions associated with buttons mapped with those modes in mind.

First off, TARGET has a learning curve along which everyone builds up obvious questions with answers all spread in the documentation playing hide and seek. If you paste your TARGET code, that would make it for a cristal-clear question and there would be a related answer.

I'm willing to help but all I can talk about is TARGET and TMWH HOTAS hardware. All I know is that TARGET would make no difference in what the sim gets from a keyboard action and a script-generated keyboard event....

I too did play with ME features right after having a hard time getting better with these maneuvers and I got an alternative to those failure/success outcome: The miz is attached to my Repeatable maneuvers thread.

One condition you have to meet is to be prepared for is to take the whole thing like if it were nothing like a game, rather a study sim where you have to repeat things "many" dozens of times before you can say you do them right ;) But, more to the point of these qualifications, you'd better have a look at what's called triggers with Mission Editor to know precisely what you're expected to do. I had the same kind of issues with some of them and even had to rectify what I've detected as been wrong heading, altitude speed and timing (see some earlier posts in this thread).

You have to look for your hard disk folders in the Missions screen, under "My Missions", "System missions", ...

Follow the link in this thread first post then click on DOWNLOAD right under the picture to get BFT02_-_Takeoff_and_EFATO_V1.1.miz

Could it be a constraint coming from the server side config-files?

JOY_X of one USB input device has nothing to do with JOY_X from another. One Controls view column = One USB device. They send their data through two different input channels that have their own X value bound to two different program input handlers.

Another among the good ones:

... and more good things ...

Worth looking:

I know of TM Warthog dynamic curve adjustment solution, but this is not an in-game option as it requires advanced TARGET scripting.

Thanks Wichid for this detailed report as it's a good addition to one of those topics in real need for documentation. I understand you're talking about your awareness priorities at the moment and I guess time may have them swapped along the learning curve. Most of what you talk about does make sense but I expected you would mention using only one engine throttle for finer speed control while connected... Did you try that ?

There soon will be an "old saying" about how you have to learn from your previous deaths to make your current one last longer!