Jump to content

Prophet

Members
  • Posts

    1339
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Prophet

  1. I don't think you understand the problem I am describing. It has nothing to do with calibration, CH control manager, or drivers. It is purely about default axis assignment. I will take pictures when I get home from work.
  2. The CH Control Manager software is not able to assign the axis in DCS.
  3. I have recently upgraded to a TMWH from the Cougar. I had a perfectly functioning Foxy profile, and I had no need to try to figure out this Target scripting. Until now. For now I have not messed with any other aircraft except the A10C, mainly because the default DCS profile is really good and I am just getting used to the HOTAS. But I have discovered, and resolved, one very annoying problem. By default there is no way to assign the TMWH keys for TIR or voice comms. Pretty standard these days to have. The MIC switch is relatively unused, and so I decided to map this. The problem is, once you create a Target profile and run it, the script creates a new name for the devices and you lose the default key assignments. And what is even more frustrating, you lose specific toggle commands like EAC Arm/Off. I have figured this out so not only do I regain those lost commands, but DCS also recognizes the new device and assigns all the commands automatically. Now I am only mapping the throttle, but I am sure this can also be figured out for mapping both the JS and Throttle and for all the other aircraft as well. And I believe any other device one is using that is not by default included. So first, here is the script I am using. First I have excluded all other devices except the Throttle. Then I have assigned all the throttle buttons to the default DX assignments except the MIC switch. Where I have a short press of the MIC center button (MSP) as TIR center, a long press is TIR pause, and MIC up (MSU) is CAPS which is what I use for TS3 PTT. include "target.tmh" //program startup int main() { Configure(&Joystick, MODE_EXCLUDED); Configure(&LMFD, MODE_EXCLUDED); Configure(&RMFD, MODE_EXCLUDED); Configure(&HCougar, MODE_EXCLUDED); Configure(&T16000, MODE_EXCLUDED); Configure(&T16000L, MODE_EXCLUDED); Configure(&TWCSThrottle, MODE_EXCLUDED); Configure(&TFRPRudder, MODE_EXCLUDED); if(Init(&EventHandle)) return 1; // declare the event handler, return on error //set pulse and delay lengths SetKBRate(50,100); ////////////////////////////// //Throttle Axis Definitions/// ////////////////////////////// MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS); MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS); MapAxis(&Throttle, SCX, DX_X_AXIS); MapAxis(&Throttle, SCY, DX_Y_AXIS); MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS); ////////////////////////////// //Throttle Button Definitions/ ////////////////////////////// MapKey(&Throttle,MSP,TEMPO(USB[0x6A],USB[0x6B],1000)); MapKey(&Throttle,MSU,CAPS); MapKey(&Throttle,MSD,DX5); MapKey(&Throttle,MSL,DX6); MapKey(&Throttle,MSR,DX4); MapKey(&Throttle,SPDB,DX8); MapKey(&Throttle,SPDF,DX7); MapKey(&Throttle,BSB,DX10); MapKey(&Throttle,BSF,DX9); MapKey(&Throttle,CHB,DX12); MapKey(&Throttle,CHF,DX11); MapKey(&Throttle,PSB,DX14); MapKey(&Throttle,PSF,DX13); MapKey(&Throttle,LTB,DX15); MapKey(&Throttle,CSU,DXHATUP); MapKey(&Throttle,CSD,DXHATDOWN); MapKey(&Throttle,CSL,DXHATLEFT); MapKey(&Throttle,CSR,DXHATRIGHT); MapKey(&Throttle,EFLNORM,DX16); MapKey(&Throttle,EFRNORM,DX17); MapKey(&Throttle,EOLMOTOR,DX18); MapKey(&Throttle,EORMOTOR,DX19); MapKey(&Throttle,APUON,DX20); MapKey(&Throttle,LDGH,DX21); MapKey(&Throttle,FLAPU,DX22); MapKey(&Throttle,FLAPD,DX23); MapKey(&Throttle,EACON,DX24); MapKey(&Throttle,RDRNRM,DX25); MapKey(&Throttle,APENG,DX26); MapKey(&Throttle,APPAT,DX27); MapKey(&Throttle,APALT,DX28); MapKey(&Throttle,IDLELON,DX29); MapKey(&Throttle,IDLERON,DX30); MapKey(&Throttle,EOLIGN,DX31); MapKey(&Throttle,EORIGN,DX32); //add initialization code here } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here Now if you run this profile, and go in to DCS controllers you will see you no longer have the Throttle - HOTAS Warthog (long device ID). Instead you have a Thrustmaster Virtual Game Controller (root) (long device ID). In the ...\DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C\joystick folder you will see all the provided default profiles. These profile names are the exact same as the name in the DCS controller window, and in the Saved Game folder where the diff.lua files are just without the device ID. So I copied the 'Throttle - HOTAS Warthog.lua' and renamed it to 'Thrustmaster Virtual Game Controller (root).lua'. Done. All default keys automatically assigned again.
  4. The spacing of nodes just allows you to control the curve. If its linear, you only need 2 points. But if you have a non-linear curve, it allows control of it. As for the default view. You need to edit the SnapviewsDefault.lua. I have always found the vertical angle offset to be very annoying especially with the Russian HMD's, as you are looking down your nose at that circle. [13] is the center view. I edit the vAngle to 0 on all of the aircraft.
  5. I have noticed that with my CH Pro pedals, that it uses the default profile. So then I must go through and reassign the axis, and just because they exist and I am a bit compulsive about it, I clear the category of commands. I believe I have figured out why this is happening. The default profile file; ....\DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C\joystick\CH Pro Pedals USB .lua The filename has a space after USB. Remove that space after USB, then in game the Yaw and Left/Right breaks are assigned, and the key commands are grey'd out and unable to be assigned. And the rudder and wheel brakes are automatically assigned. Small 'bug'.
  6. Sure. The issue is that the files provided have the device ID of the person who created and uploaded them. This device ID is different than your device ID. So if you follow the instructions that are provided with the profile, it won't work. DCS will just load the default profile. And you will bang your head trying to figure out why. It only requires a very small change in the instructions.
  7. So I am in the controls editing screen, and I get a crash. Then, the game won't start at all, crashes immediately at the splash screen. I can't seem to see why it initially crashed, but in the crash log from starting DCS it seems to indicate an out of memory error. I have 16GB of system RAM, and a 1080Ti. Evga XOC and task manager show I am not even close to being out of memory, system or GPU. A reboot seems to fix it, for a while. I had these sudden crashes upon starting the game yesterday too. dcs.log-20180429-163253.zip dcs.log-20180429-163042.zip
  8. The easiest, but longest, solution is to just download the profiles in DCS for the given controller. The only slightly longer solution is to copy your device ID Hex and paste it over the device ID hex in the provided profile.
  9. I would actually say its the other way around. Your instructions provided with the profile don't work. You insist they do. Why? Don't know. But the fact is, your instructions don't work. And you know they don't. Because you even said so in 2015. If this thread was about helping people, you wouldn't be insisting the instructions are correct when they are proven to not be. But you'd have to set your ego aside I guess. Here let me quote where you knew this in 2015. If you need to load the profile from in the game, then step a and b are irrelevant. And thats whats hanging people up. The reason I deleted it, because I was going to provide more detail. But given how offended you seem about it all, you can pound sand for all I care.
  10. You can insist as much as you want. The instructions dont work because the hex of YOUR controller is different than the hex of MY controller. And since the Hex is different, the default profile is used. Edit - And looking through the comments, I can see this problem being referenced in 2015. Its just a simply edit of a. 1) as it no longer applies. :shrug:
  11. From what I have read release and OB were the same versions. But now the Open Beta has just been updated to 2.5.1. So if you are on 2.5.1, its the open beta.
  12. Keep in mind, I had to delete my BS2 upgrade installation and then redownload BS2. Otherwise it kept asking for a key at startup, and i couldn't enter a KA50 cockpit.
  13. Here we go. Its a sticky from 2 days ago. I think the page wasn't showing for me because I just did it. https://forums.eagle.ru/showthread.php?t=206574
  14. Yeah, thats why I didn't see it anymore because I already did it.
  15. I just found a place on the ED website where I entered my BS1 key, my BS2 key, and it gave me a new DCS:BS key. But for the life of me I can't find the darn page again.
  16. I just found a place on the ED website where I entered my BS1 key, my BS2 key, and it gave me a new DCS:BS key. But for the life of me I can't find the darn page again. No ticket submission needed.
  17. I mounted my monitor on an articulating arm for that very reason.
  18. I can say I quite honestly haven't flown much at all in the last few years specifically because of these 'mods'. These mods aren't new. Quite honestly ED should have been well aware of their existence and the impact on competitive MP. Hopefully now that its on the proverbial radar, something can be done.
  19. Its nice to know that 3rd party devs can work on their own system. Thats makes it quite interesting.
  20. Anyone able to compare this to the iVibe? It looks like the same exact thing, just different software. The iVibe has absolutely no support anymore, although Craig me try and sue you, and I got a small software problem. It wont come to the foreground. So I can't change anything or look at anything. Might as well toss it and get something else. Price seems pretty good hear. Just wondering about the vibration strength and how good the effects are so far.
  21. Just fly 1.5 until then. I am pretty sure when they get it merged that 1.5 will auto-update to 2.0.
  22. I'm surprised one of the scripting experts hasn't created some messaging trick.
  23. I am late to the party here. I finally got everything working in FC3 and A10C, now getting to the Mig21. Except it crashes every time, even a blank mission with just the MiG21. Seems like there were problem at launch of 1.5. But supposedly fixed? I have uninstalled it and manually deleted the files multiple time. In /Mods and /CoreMods. Not sure what else to try.
×
×
  • Create New...