slimakwielki
Members-
Posts
153 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by slimakwielki
-
I don't have screenshot, but made a video from replay track (essence) on Youtube when loosing wing after bad hit. I admit that I didn't make any runway though, but did a really hard bumpy land on a field, no crash, no explosion though, and could safely open canopy thereafter:) http://www.youtube.com/watch?v=FJoC8cskHwM
-
Verdict on the TM Warthog?
slimakwielki replied to JIMJAM's topic in PC Hardware and Related Software
I had Saitek X52 (not Pro) and using it with Black Shark and A10 since public beta were avaiable. X52 can cover all Hotas actions with a little bit effort. However I could not resist having developed product in conjunction with DCS so I grabbed it. TM WH is far more precise, require a bit of practice after first not that well ergonomic value (comparing to X52, but this replica, not a gamer hotas). However TM WH is not so reliable... I would say that if You're technical/manual person and dissambling stick/throttle is not something that You could be aware of to correct/fix/improve some shaft plays after a while (or other minor faults) - go for it. If however messing with grease and all that stuff is not something that you would like to do, be aware of incoming dissapoitment (quality). -
yep, I felt like looking through camera attached to airframe rather than virtual pilot without it. Turning it on actually helped as I tend to 'counteract' anticipated g-force head move and with option on, it turned out perfectly to leveling off view :)
-
Best setup for trackir 5
slimakwielki replied to Matt18C's topic in PC Hardware and Related Software
I think this is quite personall to suit your needs. I spent an hour or 2 adjusting trackir 5 with trackirpro clip to suit me. I'm after one-to-one profile which allows clear, smooth movement without using zoom (FOV hard locked at 83), but it took me some time to deal with cockpit quirky different zones reaction behaviour. It seems that there are 2 zones: upper, closer to have a good HUD and outside view, and 2nd zone below it which allows great overview inside cockpit avionics. Going from 1 to 2 zone might be frustrating at the beginning, but comes as a nature with practice. -
Amazing job sqeezing last bits from ME... SP.On_Station_v3 run on BETA 4 full remarks: 1 While exiting mission I got runtime error (dsc requested terminate in unusual way...). 2 Tanker Arco61/callsign Arco has invalid COMM set to 150 (AM), no matter 'set freq' to 126 it won't response untill changing COMM from 150 to 126, also activate TACAN command should have set callsign to ARCO (default TKR). 3 Wizard/Deathstar AWAC has activate TACAN command (WP1) which has to be deleted (no such support in ME/Beta 4). 4 I find it quite difficult to spot for targets via TGP based on received coordinates, they tend to miles away and it makes me nervous when wingie spots them far much earlier advising about SAM presence... 5 Which flag disables barrel roll 'get mission update' trigger? 6 Is there among all missions any with built-in JTAC co-work? Great job though. Will follow project.
-
I'm not RL pilot but I do pay attention to as realistic as possible attitude. After experimenting I found TM WH X/Y (roll/pitch) curvatures to set at 15/15 (no deadzones) and Saitek Rudder Pro curvature set to 25 (2 deadzone due to loss of precision) and toe brakes to user curvature/inverted (otherwise You encounter partly blocked wheel brakes problems, not with user curvature though). These settings allows precise flight control (Note: TM WH has to be fixed/corrected first to get rid off 'bump' movements and x/y shafts plays!) as well as good feeling while performing evasive/max performance limits mvr.
-
Do you think it will be released 2010? Yes or no.
slimakwielki replied to Sticky's topic in Chit-Chat
Nope, there's no way to have A10C released by 2010. I don't want uncompleted, not stable, buggy product... Just release BETA 4 by that time please! Beta 3 is way non stable on my PC letting me play barely few missions without CTD, not to mention TGP/MAV useless due to buggy haze/fog. I would go back Beta 2 but first and foremost is to get familiar with new Flight Model so I would rather avoid collecting bad habits/feeling... -
ad1) A: It would be the best to have 3 identical 1680x1050 LCDs in order to achieve best results at max native 5040x1050 resolution. If planning different ones-You'll be limited to lowest resolution among all 3 (You can't have differenct resolutions on particular screens) ad2) A: I suggest to go through compatibility thread somewhere (I've seen it when I was getting TH2GODigital a while back) and check wheter product will be hassle free. Getting 3 LCDs 1680x1050 (22") makes reasonable choice (personally were using 3xDELL E228WFPc). Mentioned graphic card would pull DCS KA50 on high settings (5040x1050) without problems (about 30% framerate dropoff comparing to 1680x1050)
-
Flaps switch on HOTAS Warthog
slimakwielki replied to Dethmagnetic's topic in Controller Questions and Bugs
I'm pretty sure. In-game options has everything, but not well described/presented which leads to confusion... -
Flaps switch on HOTAS Warthog
slimakwielki replied to Dethmagnetic's topic in Controller Questions and Bugs
If You go *\DCS A-10C Beta\Config\Input\Aircrafts\A-10C\keyboard\Keyboard.lua (or default, or new one based on default to have a original copy - You got my drift?) and overwrite section: [225] = { ["combos"] = { [1] = { ["key"] = "F", }, -- end of [1] }, -- end of ["combos"] ["name"] = "Flaps Down", ["category"] = "Systems", ["down"] = 145, }, -- end of [225] [226] = { ["combos"] = { [1] = { ["key"] = "F", ["reformers"] = { [1] = "LShift", }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Flaps Up", ["category"] = "Systems", ["down"] = 146, }, -- end of [226] [227] = { ["up"] = 75, ["name"] = "Wheel Brake On/Off", ["category"] = "Systems", ["combos"] = { [1] = { ["key"] = "W", }, -- end of [1] }, -- end of ["combos"] ["down"] = 74, }, -- end of [227] with as follows: [225] = { ["combos"] = { [1] = { ["key"] = "F", }, -- end of [1] }, -- end of ["combos"] ["name"] = "Flaps Down", ["category"] = "Systems", ["down"] = 1049, }, -- end of [225] [226] = { ["combos"] = { [1] = { ["key"] = "F", ["reformers"] = { [1] = "LShift", }, -- end of ["reformers"] }, -- end of [1] }, -- end of ["combos"] ["name"] = "Flaps Mvr", ["category"] = "Systems", ["down"] = 1048, }, -- end of [226] [227] = { ["combos"] = { [1] = { ["key"] = "W", }, -- end of [1] }, -- end of ["combos"] ["name"] = "Flaps Up", ["category"] = "Systems", ["down"] = 1047, }, -- end of [227] You will have: "W" - Flaps Up [class button] LShift + "F" - Flaps Mvr [class button] "F" - Flaps Down [class button] You can assign those in TARGET then. These acts as buttons now, NOT toggle class, so You can press them as many times You want to get desired Flaps Position (going from Up to Down without MVR as well). As You might notice I overwrite Brake section (default 227 section with "W") to make it easier to see in Controls->Systems for You, but feel free to change it to suit Your needs. With a little bit research over files You can customable many things in pretty ergonomic value (such as adding Emergency Disconnect Lever to TM WH paddle switch by adding section to HOTAS lua file). Hope that helps! -
Inside view of TM HOTAS Warthog
slimakwielki replied to Frazer's topic in PC Hardware and Related Software
Have it for about week. Can't say a bad word so far. Oil stays there. I made those sphere shaped plastics/ball joint connection area 'touch wet' and postioned upside down for an hour with just a 1 drop excessive oil coming down removed thereafter. Works well. I will know when there won't be any lubrication there because i did try to use stick completely dry without any grease and its way not precise and generates friction-movement noise... -
Inside view of TM HOTAS Warthog
slimakwielki replied to Frazer's topic in PC Hardware and Related Software
Quick solution from experience. To solve/repair/make better: 1. Play on X/Y axis (or both): the bottom plastic bolted to bottom metal ring bit which is held by 4 silver screws needs to be adjusted by extending approp. clearance between them. That causes rubber ring from upper metal bit tightning upper plastic ball joint (any gap here causes annoying stick play). 2. So called 'lack of smoothness' while trying to slowly apply low X/Y stick movement - get rid of that f*****g crappy grease and neatly apply few drops engine oil - works like a charm. Results: TM WH corrected after 2 weeks usage issues that caused 'get this s**t returned' thoughts crossing my mind... Soon: fixing throttlies lateral and thrust plays -
WOW! What an incredible source of adrenaline!
slimakwielki replied to JEFX's topic in DCS: A-10C Warthog
I meant exdend [down] automatically while switch already positioned and decreasing speed over their operational speed. Their relay needs to have a source to prevent damage over some speed. Anyway, I was guessing load on them too, but taking into accout design to make such frame as simple/reliable I assumed that would unnesec. made construction more complex rather than having an IAS direct feed. I MIGHT BE WRONG though. Need to do some research over internet to find out answer [or kindly await more educated simmer/pilot to clarify]. -
WOW! What an incredible source of adrenaline!
slimakwielki replied to JEFX's topic in DCS: A-10C Warthog
Now I wonder what's the flaps logic to follow in such case, as mentioned above-ie: loosing IAS indicator. They do extend to MVR or DN position below certain speed obtained from... IAS gauge? -
With Beta 3, once unpaused at the mission begining, field of view tends to zoom out untill hits its limits (found in view.lua) to 120 degrees. That what makes HUD not readable. Default 83 degrees is more then enough (personally use 90 degrees and "locked" FOV in view.lua at 90/90 to prevent it from zooming out...).
-
...unless its stuck with '<GIMB ROLL> bug' in which case You have to with TGP as SOI slew it a bit before Boresighting
-
Yeah, loadout avaiable via mission editor is non-true, buggy. I went through *.lua to correct A10C loadout and add/change database weapons file and change in accordance to manual A10 Stores and DSMS section so IRL it should looks like: Pylon 1: ALQ-131, GBU12, MK-82, MK-82 AIR, CBU-87, CBU-97, BDU-50LGB, BDU-50LD, BDU-50HD, LAU-105_1*AIM-9M, LAU-105 2*AIM-9M, LAU-105_2*CATM-9M, LAU-105_1*CATM-9M, LAU-105 Pylon 2: MK-82, MK-82 AIR, SUU-25 *8 LUU-2B/B, AAQ-28 Litening II AT, BDU-50LGB, BDU-50LD, BDU-50HD, CBU-87, CBU-97, LAU 68 with [rocket type], LAU 131 with [rocket type] Pylon 3: LAU-117 with Maverick electro optical seeker 136 kg, LAU-117 with Maverick infrared IR seeker 67 kg, LAU-117 with Maverick electro optical seeker 67 kg, LAU-117 with Maverick infrared IR seeker 136 kg, LAU-88 with 3 * Maverick infrared IR seeker 67 kg, LAU-88 with 2 * Maverick infrared IR seeker 67 kg, LAU-88 with 1 * Maverick infrared IR seeker 67 kg, LAU-88 with 1 * Maverick electro optical seeker 67 kg, LAU-88 with 2 * Maverick electro optical seeker 67 kg, LAU-88 with 3 * Maverick electro optical seeker 67 kg, Training LAU-117 with Maverick infrared IR seeker 67 kg, Training LAU-117 with Maverick infrared IR seeker 136 kg, Training LAU-117 with Maverick electro optical seeker 67 kg, Training LAU-117 with Maverick electro optical seeker 136 kg, Training LAU-88 with 3 * Maverick infrared IR seeker 67 kg, Training LAU-88 with 2 * Maverick infrared IR seeker 67 kg, Training LAU-88 with Maverick infrared IR seeker 67 kg, Training LAU-88 with 3 * Maverick electro optical seeker 67 kg, Training LAU-88 with 2 * Maverick electro optical seeker 67 kg, Training LAU-88 with 1 * Maverick electro optical seeker 67 kg, MK-82, MK-82 AIR, TER 3* MK82, TER 3* MK82 AIR, BDU-50LD, BDU-50HD, TER 3* BDU-50LD, TER 3* BDU-50HD, MK-84, GBU-12, GBU-10, TER 3* GBU-12, BDU-50LGB, CBU-87, CBU-97, CBU-105, CBU-103, GBU-31 IAM, GBU-38 IAM, LAU-68 with [rocket type], LAU-131 with [rocket type], LAU-68x3 with [rocket type], LAU-131x3 with [rocket type], SUU-25 *8 LUU-2B/B, TER SUU-25 *8 LUU-2B/B, MXU-648, TER Pylon 4: MK-82, MK-82AIR, TER 3* MK82, TER 3* MK82 AIR, BDU-50LD, BDU-50HD, TER 3* BDU-50LD, TER 3* BDU-50HD, MK-84, GBU-12, GBU-10, TER 3* GBU-12, BDU-50LGB, CBU-87, CBU-97, CBU-105, CBU-103, GBU-31 IAM, GBU-38 IAM, LAU-68 with [rocket type], LAU-131 with [rocket type], LAU-68x3 with [rocket type], LAU-131x3 with [rocket type], Fuel Tank, MXU-648, TER Pylon 5: MK-82, MK-82AIR, TER 3* MK82, TER 3* MK82 AIR, BDU-50LD, BDU-50HD, TER 3* BDU-50LD, TER 3* BDU-50HD, TER 3* BDU-33, MK-84, GBU-12, GBU-10, TER 3* GBU-12, BDU-50LGB, CBU-87, CBU-97, CBU-105, CBU-103, GBU-31 IAM, GBU-38 IAM, MXU-648, TER Pylon 6: MK-82, MK-82AIR, BDU-50LD, BDU-50HD, MK-84, CBU-87, CBU-97, MXU-648, Fuel Tank Pylons 7-11 mirror pylons 5-1 That's the most accurate list I could make while going through avaiable materials and doing some research over internet. One mismatch that I was to lazy to include is TER 3* BDU-50LGB which once I relized I found not to include as I would never use it anyway. That list IMHO would conclude Real Life loadout...
-
Not that much, I would say ~2 degree on mine. Only noticed when changing HUD mode via MMCB. Can't be fixed easy I'm afraid unless someone will bravely attempt to find a way of disconnecting those 2 sphere plastics of which You can see one from top...
-
I feel same here. I've notice right throttle slight play straight up from box. Its minor, but I can already (~2 weeks) feel loosen play... The thing that concerns me is stick play (!) in pitch (Y) and Z (non-existing twist like X52 rudder implemented function) after few days usage. Again, these are minor and most users touching TM WH wouldn't notice but that's not what I expected from 330quid product. And I really treat her gently... That thing caused me to find wheter so called 'high precise hall efect sensor stick' (c'mon, its a basic EM sensor found on camshafts too) can be fixed so I dissambled mine. However I couldnt find out way of disconnecting last 3 bits (2xsphere shaped plastics which provides 2 magneses movement over sensor) without risking damage and these are bits which make whole difference :/ Well, at least I can say that quality and design of TM WH is better done that my previous X52 and S Pro Rudders which have been dissambled too few times (cleaning/correcting plays)
-
Doesn't CMS Z-axix (default "-" key, or CMS push on TM Hotas WH) toggles between activated (apart from fully-automatic mode) / deactivated ? ECM pod has to be on station 1 or 11...
-
Thrustmaster Warthog = WOW!
slimakwielki replied to ronht's topic in PC Hardware and Related Software
I have to admit that after playing DCS A10C after 3 days using TM Warthog setup in compare to earlier ~3 weeks playing time on Saitek X52 I find it very difficult to control hog... I had X52 setup nicely configured (with mapping as close as possible to 'as per warthog real hotas' setup) and could with ease take advantage of its wide-quick-combos access. With X52 there is also easy access to its keys/sliders/switches etc in terms of ergonomy. I find it much un-ergonomic with TM WH now. Most of them I can't really reach it without loosing grip connection on either stick/double throttle. Weapon Release on stick is really pain in a**e now as with precise CCIP GPLD flying demands I loose stable gip so much required at that mom. On throttle operating side switches (spdbrks, boat, china) makes momentarly lost connection over throttles and often slew stick movement/repositioning. Well, that's a Replica so I am not to expect covering player needs :) Just wonder wheter owners are happy with what they expected. -
cycle = false, that disable toggle mode (need RMB to go back from ON to Test, LMB won't toggle ON to OFF anymore that way)
-
any one got the new thrustmaster A10. HOTAS
slimakwielki replied to con3para's topic in PC Hardware and Related Software
Couldn't resist further tempation ;) Ordered TM Warthog today, estimated delivery date: 2nd Nov. Anyone interested in Saitek X52 in good condition now:) ? Going to put X52 on flybuyer now...