Jump to content

GPatricks

Members
  • Posts

    487
  • Joined

  • Last visited

Everything posted by GPatricks

  1. Rel4y - Got a customer from the US trying to reach you for TM Cougar parts (Rich L.), he's having trouble getting accepted to this forum so I had him email you. PS - my Pro Throttle and Fighterstick with your mainboards and MRpots works perfectly, been using it more in the last months than I did for 10 years! Thanks!!
  2. Ok, I must be an idiot as i've stared at this for an hour, read all the posts and DCE shows up in DCS World (with no mission) I get this error when I run FirstMission.bat - C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\luae.exe: cannot open C:\Users\xxx\Saved: No such file or directory. My FirstMission.bat file is - start "Generate First Mission" cmd /k ""C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\luae.exe" C:\Users\xxx\Saved Games\DCS.openbeta\Mods\tech\DCE\Scripts\BAT_FirstMission.lua && exit" I see the error truncates the path of Saved Games, no idea why, is that it? What the heck am I missing? The install looks fine, I made all file adjustments required.. likely something simple i've overlooked? Double checked camp_init.lua also, as i'm not 100% sure how the path should look due to the instructions in bold, this is what I have now - path = "C:\Users\xxx/Saved Games/DCS.openbeta/Mods/tech/DCE/Missions/Campaigns/FA-18C Battle Group Delta/", --path of campaign folder within USERPROFILE (use / for folder seperation as \ is an escape character in LUA) Thanks for any help.
  3. I only tried the Tomcat but now I have to click past about 10 registration questions for all the of the modules that were out for free trial. How can I get rid of these nags?
  4. Title says it, it crys out for a Spitfire vs. 109s/190s BoB scenario! I see there are 4-5 MP servers up now (all MT), looks promising.
  5. Is there a way to stop the sim from asking for a registration of all the Free Trial modules (I only tried the F14!) every time it starts? It goes through about 7 then show a list of all the others, bit of a PITA every startup...
  6. Well said Jester, I would welcome the Zero! Be nice to have a Wildcat off the Carrier to get into history mode but the Corsair or Hellcat will work. I shot a LOT of superior planes down in my A6M in Aces High way back when.... real trick is sitrep and not to get Boom n Zoomed..
  7. Thanks BIGNEWY, been holding off on trying my new F18 until it arrives, good to know it will be soon..
  8. Imagine a Dynamic campaign taking us through the Korean War and beyond. Start with the F86 and Mig 15 (and some appropriate prop planes from the era) and then China and Russia get involved. C'mon, the planes are already there, let's go!
  9. Yeah, I can't even respond to him, what are you 12?
  10. Release 13.3, and I apologize but the Alt Launcher is for BMS 4.34.2, sometimes I forget where I am!
  11. By default the CH gear outputs DX button presses and HOV for the hats. I've only used JStick Gremlim for simple keymapping and had no issue, hopefully someone can read that error message for you.
  12. Take a look at Joystick Gremlin and VJoy, JG is fairly user friendly but quite powerful. VJoy is required to be installed for JG to work, but it's JG that you work with.. then again, if you just do the sensors you have to change nothing..
  13. Sokol1, IF CH Control Manager is installed (at least in my case) no amount of plugging/unplugging would get MMJoy or Win10 to see the USB device again. As soon as I uninstalled and rebooted, the device returned. Have an issue with Joystick Gremlin and Teamspeak 3 you may have come across. Teamspeak does not accept DX button presses as a PTT input so I needed to program the CH Throttle to output "Scrolllock" (default TS3 PTT) when DX2 was pressed. Easy as pie, great program, I press DX2 and Scrollock is pressed. Odd thing is, unless JG is an open window on the desktop (not minimized) the button press does not work in TS3. With it minimized to the system tray it works in Windows itself as witnessed by the "Scroll Lock On/Off" graphic that my system puts on the screen. Any idea of a setting I may be missing?
  14. If you set the new Fighterstick and/or Throttle mainboards with the exact VID/PID/Name as the original using MMJoy2, as I did, with the CH Control Manager still installed several things happen. 1. As soon as you save the setup to the device it will disappear from the MMJoy USB list 2. It will not show up in CH Control Manger 3. It will not be able to be calibrated in Win10 The only way to get it back is to uninstall CH Control Manager and reboot, then (in my case) it shows back up in MMJoy2 and you are able to work with it once again. What this (to me anyway) seems to show is that CH Control Manager "sees" the addresses and takes command of them from MMJoy2 but doesn't actually "work" with them, but instead renders the device unusable. it's a shame Control Manager has been abandoned, it was the best gear programming software out there for many years, too bad they (or Bob Church) won't release the code so some genius out there can update it!
  15. I say it's useless (to me) because it no longer will see the CH gear and it actually causes issues if you try and fool it into seeing the CH FS/PT by assigning/matching the CH Name/VID/PID during setup. If you must use Control Manger, just install the new sensors and it works fine. The microstick on the PT is just an X-Y axis (and DX Button 1), for DCS and BMS everything is assigned easily in the sim (well, for BMS I use Alternative Launcher). In fact I just set up DCS to use the PT microstick as the Radar Cursor X-Y axis 5 minutes ago! Rel4y (or someone) may come up with fix for Control Manager but I wouldn't hold my breath as even CH has totally abandoned it..
  16. Before and After Pics of today's MTWSims CH Pro Throttle 12 bit Mainboard install (blue board), went without a hitch, works perfectly! We found the CH Control Manger to cause a myriad of issues with the new boards once set to the same PID as OEM CH, until some workaround is found my advice is to uninstall it completely before installing the boards. It's fairly useless at this point anyway.
  17. The CH Pro Throttle USB will still work fine in CH Control Manager with the Sensor Upgrade, but I don't believe it will work with the new Mainboards without some work. There is a before/after pic of the sensor installed in this thread (Post #71).. It's a 5 minute job, very easy.
  18. MTWSims CH 12 bit Mainboard installed and calibrated (using MMJoy2), all functions perfectly! Just a few little tweaks to do once rel4y gets back to me!
  19. They are on very tight, I could open them up a little (they were closed to fit the pins on the older version) but they are not going anywhere, and I did NOT want to rip a connector off! :thumbup:
  20. Here are a couple pictures of the sensors installed in the Pro Throttle USB (before and after) and the Fighterstick USB (Y axis pic on top, X axis with OEM still installed on bottom), waiting on the mainboard pics until we get a couple things sorted out...
  21. Pictures tomorrow my friend!
  22. Just ran the carrier landing training mission without having a clue how to fly the F/A-18 and trapped (#1, so not perfect) the 1st time. Even had to pause to find the flaps switch, other than that she flew like a dream down to the deck. Now I get to learn everything else, but I can see how the carrier addition is very cool to have...
×
×
  • Create New...