Jump to content

Achiral

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Achiral

  1. If you want to keep the stick and throttle separate (so the default DCS profile still works), but also use TARGET for external commands... In your .tmh file, replace this line: if(Init(&EventHandle)) return 1;with these three: Configure(&Joystick, MODE_KEEPENABLED); Configure(&Throttle, MODE_KEEPENABLED); if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;
  2. It's been many years since I've used NVIDIA, but when I did, I found EVGA to be the best for me. Typically good pricing, good factory overclocks, and they didn't give me any issues. I bought a GIGABYTE once due to its lower price (for the model at the time), and had the fan bearing die within a year. Got it replaced and that bearing went too. Replaced it with an MSI, and had that start failing (random vid card errors regardless of driver version used) about a year later. As with all things: YMMV.
  3. You can also prevent TARGET from creating the combined controller at all by changing if(Init(&EventHandle)) return;to if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return;I have not tested this with the newest TARGET release though.
  4. Oops :music_whistling: I had made a bunch of changes back and forth at one time while figuring out how it all worked, and had multiple target.tmh files that were doing different things. You will also need to Configure() the devices you want to keep separate. So it will end up like: Configure(&Joystick, MODE_KEEPENABLED); Configure(&Throttle, MODE_KEEPENABLED); if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1; I think that should be all.
  5. Actually, you can use TARGET with both Joystick and Throttle while maintaining them as independent controllers (i.e., not combined into a new virtual controller). It's just not very well documented. In your .tmh file, you will have a line like if(Init(&EventHandle)) return 1;Change that to if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;That second parameter being passed restricts the script from creating the virtual controller - so the joystick and throttle (and any other TM controllers for that matter) will remain separate in the device list. I don't think there's any way to do this with the TARGET GUI though.
  6. The benefit of a bigger screen is that you can increase the field of view in DCS, fill a wider part of your vision, and have it represent 1:1 what the in-sim camera sees in the cockpit. A 27" (diagonal) 16:9 monitor is about 23.5" horizontal. If you place that 24" from your face, it will fill about 52 degrees of your field of view. You would want to set the in-sim FoV to that same 52 degrees so that you see 1:1 what you would see sitting in the cockpit. If you changed to a 34" 16:9 monitor (about 29.5" horizontal) at that same 24" distance, it would fill about 63 degrees of your FoV. You would then want the in-sim FoV to match that same 63 degrees. A 42" 16:9 monitor (about 36.5" horizontal) at 24" distance would fill about 74 degrees of your FoV. In all cases, the cockpit frame and any instruments would appear the same size. You're just adding more screen real estate to the sides so you don't need to pan around quite so much. Note that 24" from you is quite a bit further than a real cockpit's front panels would be, but it's much, much closer than the outside view.
  7. Correct, alias is always passed by reference with a prepended &. Well, almost always. One case where it wouldn't be is if you assign the alias to a constant via define. Once done though, you would need to access both by reference... alias xxx = "test"; someFunction(&xxx); define yyy xxx // yyy is now the same as xxx - i.e., an alias someFunction(&yyy);Note also that I messed up my define examples in the last post (it was late). A define does not use =, nor is the line terminated with ;. Hopefully, I can edit that still. The above format is correct. To be clear on the quotes - double quotes for string literals, single quotes for characters. So if you wanted to define a constant for gear toggle as keyboard g, you would use... define gear_toggle 'g'But for a string, you would use... define my_color "red"
  8. A few things... String literals need to be in double quotes, not single. A later reference to an alias needs to be preceded by &. strcmp() returns a 0 if the values are equal, and >0 or <0 if one value is higher. So... alias test3 = "test"; alias test4 = "test"; // ~/~ int myfunction() { if ( strcmp(&test3, &test4) == 0 ) { printf("OK 12 \xa"); } }You can also pass an alias to a function... alias my_string_var = "blue"; // ~/~ my_function(&my_string_var); // snip int my_function (alias my_local_var) { // don't think you can set default parameters in TARGET // remember to refer to &my_local_var with the & }For printf, %s works, but you need that & again (and no quotes)... printf("OK 2 %s \xa", &test3);As an alternative to using an alias, you can also use define, which then does not make use of & when referring to it. Swapping it for alias in your first example... define test3 "test" define test4 "test" // ~/~ int myfunction() { if ( strcmp(test3, test4) == 0 ) { printf("OK 12 \xa"); } }
×
×
  • Create New...