Jump to content

531-Ghost

Members
  • Posts

    438
  • Joined

  • Last visited

Everything posted by 531-Ghost

  1. Good to hear PoleCat! I'm sure those that go the Cougar route, will be glad to hear this! I'm not claiming or bashing anything actually. Just thought J.Q. Public would like to know the current state of affairs is all, not history. Thanks for the update.
  2. Nice work hannibal! Goes well with the rest of your pit!
  3. Nice link there PoleCat. And tell us about the Company Product Support for the Cougar, PoleCat. How does it rate? Not to start a pissin' contest, just thinkin' the buyer would like to know... Anywho, :thumbup:
  4. Absolutely! So, pay no attention to this link :music_whistling:
  5. I've never opened any of my CH Products to lube anything. Never had to replace a POT. I'm not saying that from time to time someone may have to have a POT replaced or something may need to be fixed for whatever reason. When and if they do, CH Products Product Support is second to none. Period. And, as far as them being "toys" let's face it, . . . . . . . . . . . They're all just toys. Cougar too.
  6. The beauty with CH, if you can only afford a stick, get a FighterStick or CombatStick. Then, as you can afford to add to your CH Controllers, you can add a ProThrottle, then ProPedals, MFP... Use Control Manager to map them as a single device for older games or as seperate devices for newer ones. In any event, get what suits you. Me personally, I got tired of throwing good money after bad and went with the full CH Products line up. FS/PT/TQ/PP/MFP/MFP and Eclipse Yoke for all my simming needs.
  7. Okay, fine, when someday comes, you'll know where to go ;)
  8. I've uploaded my overlays here. :music_whistling:
  9. http://simhq.com/forum/ubbthreads.php/topics/2628897/1/Review_RC8_DCS_Black_Shark_Eng.html
  10. With more to follow! ;)
  11. Very nice! :pilotfly:
  12. No, I have no issues with my CH Products. Control Manager v4.2
  13. No issues with mine. :smilewink:
  14. Yes they are. At least the version I reviewed.
  15. RC8 Review English Version. I can post this error report: Error running Config/autoexec.cfg: cannot open Config/autoexec.cfg: No such file or directory 11/30/2008 12:00 V808201900 World::LoadPlugins: Loaded plugin module CockpitBase.dll Dispatcher: initial random seed = 5272625 Dispatcher: apply random seed = 5272625 Cosmos: Mission date assigned - Year:2009, Month:6, Day:1 loaded from mission Scripts/World/GPS_GNSS.lua Map objects for beacon site Потийский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Сухумский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Тарханкутский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Железный Рог NOT FOUND! Ojbects created. Map objects for beacon site Мыс Херсонесский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Анапский NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Айтодорский NOT FOUND! Ojbects created. Map objects for beacon site Батумский NOT FOUND! Ojbects created. Map objects for beacon site Мыс Фонарь NOT FOUND! Ojbects created. Map objects for beacon site Мыс Евпаторийский NOT FOUND! Ojbects created. Map objects for beacon site Ялта NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Кыз-Аул NOT FOUND! Ojbects created. Map objects for inactive beacon site Мыс Кодошский NOT FOUND! Ojbects created. ComplexTask::open_state(). Precached tasks data loading. ComplexTask::load_task_data(). "Follow_Line" task data loaded. ComplexTask::load_task_data(). "Follow_Vector" task data loaded. ComplexTask::load_task_data(). "Follow_Vector_Old" task data loaded. ComplexTask::load_task_data(). "Approach" task data loaded. ComplexTask::load_task_data(). "Cannon_Ground_Attack" task data loaded. ComplexTask::load_task_data(). "Rocket_Attack" task data loaded. ComplexTask::load_task_data(). "Level_Bombing" task data loaded. ComplexTask::load_task_data(). "Dive_Bombing" task data loaded. ComplexTask::load_task_data(). "Missile_Ground_Target_Attack" task data loaded. ComplexTask::load_task_data(). "Missile_Ground_Target_Level_Attack" task data loaded. WARNING: multiple connectors "smoke" in model ".\Bazar\Terrain\Structures\High\TEC_A.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "light proj FFFFFF 25 25" in model ".\Bazar\World\Shapes\FARPS.lom" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_LIGHT" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_BEACON" in model "KA-50" WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50" WARNING: multiple connectors "RED_LIGHT" in model "KA-50" WARNING: multiple connectors "Gun_point" in model "KA-50" WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50" WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50" EagleFM initialize time .. 472.410600 DXDefTexture: failed to load Ka-50 font lamp.tga, D3DXERR_INVALIDDATA. Chunk is not present: ABRIS/Options.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Options.lua Chunk is not present: ABRIS/Loader/NAVIGATION.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/NAVIGATION.lua Chunk is not present: ABRIS/Loader/ROUTES.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ROUTES.lua Chunk is not present: ABRIS/Loader/ADDITIONAL.lua ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua ABRIS load default failed Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'MRP' Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'ARCADE' Cockpit::avDevice::link_all: no such device in hash - 'MRP' Cockpit::avDevice::link_all: no such device in hash - 'MRP' loaded from mission Scripts/Aircrafts/ka-50/Cockpit/ARK/ARK.lua Cockpit: ccClickable.cpp. Custom data unavailable cockpit initialize time .. 13213.748675 input layers loaded : Aircraftka-50 loaded from mission Scripts/Aircrafts/ka-50/Cockpit/ARK/ARK.lua cockpit post initialize ..161.764414 cockpit sounder deleted I got this just after flying in Sim (Real) Mode. I CTD'd and when I pressed the .exe I got an error report that the .exe could not open the game. I re-booted, and got the same error report. Un-installed/re-installed and the error went away. My system specs: Motherboard http://www.msicomputer.com/product/p_spec.asp?model=K8T_Neo-FIS2R&class=mb AMD Athlon™ Processor for Desktop http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_9485_9487,00.html Corsair Memory TWIN3X2048-1333C9DHX G 1 GB PC3200 DDR RAM (vs1gb400c3) http://www.dealtime.com/xPF-Corsair-Memo...l-Free-2nd-Day- nVidia GForce 6800GT Nspire 300W Dual Fan P4 ATX Power Supply http://www.xpcgear.com/ns30dufanp4a.html Yes, I know I'm at the low end of what is required. However, I will say this, even on my current (to be upgraded in two weeks) this sim flew very nicely!
  16. HERE :music_whistling:
  17. Yes. I'll load it up at the CH-Hangar later today. I've got one for Game Mode as well as Sim (Real) Mode.
  18. Well, if you are programming CH Products, there are a couple ways to do it. One is assign the axis in the game. Or if you wanted to use the keyboard assigned keys on either of the axis all it would take is a wee li'l script: CMS.B* = [js2.a2 < 70]; // Mini-Joystick Up = KU-31-Shkval-Slew-Up CMS.B* = [js2.a2 > 180]; // Mini-Joystick Dn = KU-31-Shkval-Slew-Down CMS.B* = [js2.a1 < 70]; // Mini-Joystick Aft = KU-31-Shkval-Slew-Left CMS.B* = [js2.a1 > 180]; // Mini-Joystick FWD = KU-31-Shkval-Slew-Right Then, assign: KU-31-Shkval-Slew-Up ; KU-31-Shkval-Slew-Down . KU-31-Shkval-Slew-Left , KU-31-Shkval-Slew-Right / to CMS.B* (you've got 128 CMS buttons to choose from so fill in the * with a CMS button #)
  19. And then there is this trimming method. Much easier if you ask me.
  20. For those of you following this thread and wondering how to do the same thing, check out this thread at the CH-Hangar.
  21. Seems some of the keys assignments needs a little help along the way for the Command File to work, properly. There is a thread at The CH-Hangar discussing how to get it to work. HERE
  22. Unless you have a cockpit with switches and buttons to program them to. :smilewink:
  23. Okay, here ya go, a .cmc (Command File)
  24. I'm not home, yet. :smilewink: You do know how to save a .txt into a .cmc, don't you? If not, The Dummies Guide will help you out. :joystick:
×
×
  • Create New...