Fish

Just a thought...... you could take down the bushes and grass and trees to zero. don't really need them, and might try a lower resolution to 1600x900, should not impact your experience much since you are playing on a laptop screen. Also make sure your laptop is running in performance mode, and that the processor is working t max (turbo) speed all the time. Find it in the power settings. it should be working at 3.4ghz. You can check this with CPUZ or some other tool. Finally, This game is a real hog of performance, and i think even a good laptop is going to struggle with it. The processor is decent but the GPU while good for a laptop, is very basic. GPU benchmarks

do yourself a favour, and bring your ram up to 16gb. Ram is cheap now, and it will improve your experience with DCS.

Hmm, On mine its 22 & 23. Also in the config theres a toggle up and toggle down action for the flaps. Both of these put the flaps in the mid (10deg) position, when released, and put the flaps in the 'up' and 'landing (20deg), positions respectively when 'held'. You can do this easily with a dx controller buttons, but it creates all kinds of problems if you try it with a key or key combination, since your 'held' keys will interfere with other keystrokes. There are some usb i/o cards (example here) out there which have digital 'switch' channels, and some have analog channels also, and maybe this is a better approach to controlling your flaps for the A10. (might not suit if your using it for something like xplane or fsx, or WW2 sims, if you need analog flaps). I'm sure you would get better advise from pit builders.

done some time ago, but still relevant [ame] [/ame]

+1 But don't dumb anything down, please. ED what about a 'Boom operator' module..........now that would add realism..

Might be better saving for a cheap 10" tablet.

For landing's and other stuff, there's lots of demonstration videos you can sit back and watch, to help get you started.

Hi Nick, First of all i'd like to say I love your modules, they are excellent, and I hope you continue to make modules of this standard. How long will this be until 1.5 is final? Nothing ever becomes final really, once on thing is complete, another starts. Is there a reason why you can't implement the activation scripts used on your other modules, to fix the problem with the Mig21, and issue an update. That way we can both fly it in release branch, and test it in the dev branches, without having to go through activations. I've lost several activations due to my pc upgrade and overclocking. New chip and CMOS reset, particularly cause a problem. Thanks

Trying to disassemble, but cant remove the retaining clip (with the square center, left on the phto), out of the main housing (without damaging the switch or disconnecting the wires) Any help welcome.

For me the issue with the HOG mini stick is the 'grip'. Finger 'slides off the very small shiny surface, and i cant 'sheath' it because the housing restricts it. If I could remove the housing, perhaps i could put a rough cover over the stick. Anyone know if the 'housing ' could be removed or is it integrated into the controller/stick? Has anyone got photos of this dis-assembled ?

Cheers for that. Hadn't even thought about VoiceAttack, and TS keys yet...... Target profile is looking 'less' unattractive, and i've put my foot in the water already with and Elite Dangerous profile. UPDATE, Got CubPilots method working for the Voice attack PTT key as F14, and TIR center and pause using F15 & F16, all working from the spare radio buttons, Throttle Btn2 & btn3. Also got the modifier option for additional controls. Also a bat file to run the autokey profile, TIR, voice attack with the correct profile, and the DCS world Alpha. So far so good. Does what i need. So everything fires up with a single click. Very neat. Thanks Polaris & CubPilot, and links in this thread. Batch File @echo off REM TIR.exe assigns F15, F16 keys to the Warthog throttle, Mic Switch, BTN2. start C:\Users\Gerry\Documents\Warthog\DCS\Autohotkey\Software\Compiler\TIR.exe timeout /T 1 /nobreak start "" "C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe" timeout /T 2 /nobreak start "" "C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe" -profile "DCS Fish" timeout /T 3 /nobreak start "" "E:\DCS World OpenAlpha\bin\DCS_updater.exe" exit AutoHotkey AHK file. #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. Process, Priority, , High 1Joy2:: ; y Joy x , y= controller ID number in windows, x= joy button number KeyWait, 1Joy2 ; Wait for 2Joy4 to be releasd x := A_TimeSinceThisHotkey ; Just assigning x here, for shorter "if's" If (x < 500) ; If hotkey was held for less than 0.50 seconds, 500 ms Send {F15} ; Send the key F15 Else if (x < 5000) ; If hotkey was held for more than 0.50 seconds, 500 ms & less than 5000 ms Send {F16} ; Send the key F16 return return 1Joy3:: ; y Joy x , y= controller ID number in windows, x= joy button number Send, {F14 down} ; Sends a press to application SetTimer, WaitForButtonUp3, 10 return WaitForButtonUp3: if GetKeyState("1Joy3") ; The button is still down, so keep waiting return ; Otherwise the button has been released Send, {F14 up} SetTimer, WaitForButtonUp3, off return

Diden't notice a thing! :) Glad to have your input.

Hmm...... Apart from the response time and refresh rate, dynamic contrast etc, there is a very important factor to consider, which ‘moderates’ the phrase ‘bigger is better’, and that’s retina distance, lets call it RDi. (I for inches) It’s the distance from a monitor at which you can just see (or not see) the pixels on a device. It’s the optimum distance for getting the maximum information for the display. As you move away, the laws of physics limit what you see. As you move close inside this, you don’t get any extra information, only pixel visibility. Now lets compare a couple of monitors, 55” UHD, RDi = 43 27” UHD, RDi = 21 If you sat in a pitch black room and viewed these monitors at their respective retina distances the experience (all other things being equal, and assuming 20 20 vision), would be the same. Each would take up the same arc of your vision. You can do the math here. In reality other factors impact our perception of immersion, high dynamic contrast generally on TV’s, Sitting at a desk, as distinct from leaning back on a couch etc. And there might be a benefit in the display being at higher focal distance (close to your long vision). Challenge then for TV or large monitor, is to have it far enough away, on a desk which is maybe only 28”. I created the chart below to help clarify and make comparisons between different viewing options. If you want a copy of the file please PM me. For example, if your viewing distance was around 30”, then you would be better off buying a 27” 1440 over a UHD, as there would be little or no difference to the viewing experience, but you would get a significant FPS benefit. Disclaimer: The RDi is based on an articles I read, and this number can be different for different people, but its not difficult to calculate an approximate value for yourself.

Ha, Moved away from a deadzone many years ago, and never looked back. So 'unnatural'.. [ame] [/ame] Any how. Spare radio buttons working for me. Really like the fact that i don't have to fire up target to play.......

Thanks for all replies. I constantly re-center, so its got to be on the hotas for me. been doing it that way for too long now.... I'll give the spare radio buttons a go. Otherwise i'll do a new, or modify someone elses target profile to allow for shifted keys, as i have on my cougar. If anyone has a profile, please post here, or PM me cheers.

Thanks guys and that all works fine. But since these are not 'shifted' buttons, they are going to replace valid 'HOTAS' functions? No? (except for a radio button maybe).

Hi all, Warthog works fine with DCS A10C, without Target (after configuring the mini mouse and POV switches). However i need to have a TIR centering button on the stick or throttle Can this be done without using a target profile. And if not, can someone Please recommend a lua and Target profile set, for the A10-C sim only. Cheers

Hi Links below broken....

Serial #: 39510 Location: Dublin, Ireland

+1

Loaded up the latest drivers, and got SLI working (sorta...). Did some analysis of the stutter, with GPUz, (see image). Note memory usage was 2500mb (1920X1200 hdr off and blurring off everything else max/ultra) well within system limits. Edit: Did the same test with a single gpu (sli disabled). And pretty much the same result.....So not an SLI problem from what i can see.

There's a useful windows cmd line function called mklink, which allows you to create 'virtual folder', to point to a real folder. So on the OS drive you would see the same DCS folder, but it would be pointing to your new drive (once you have it moved it there). I did this when my steam drive got full, now i got several games on a new SSD, but the virtual folders show up as normal on the old drive. You just need to keep a note for the future of which folders are 'virtual' because you can't tell by looking at it.

Thanks for the fix!

hmm. Yes i had customised the visibility some time ago (high is too high for me and med too low, with surround screens.!). Changed it back to system med, and all looks good. Well spotted!!