

pchRage
Members-
Posts
198 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by pchRage
-
I had the same goal, and solved it easily with the TUSBA. You can "create" a DX "button" based on the position of the throttle (as well as the ant, rng, cursor, etc...just havent found a reason to yet). 1. Put the throttle where you want position wise (ie at idle or near idle) 2. Select the DX17 dropdown and select Throttle 3. "flip" its direction (as/if needed) by clicking the little icon next to the dropdown. 4. Save setting (File -> save) 5. Reboot for good measure (sometimes after saving tusba, windows stops recognizing device calibration till I do a full shut down/unplug/replug...) 6. Then go into DCS and in the button mapping, find the idle detent... double click it on your tusba column and when move the throttle in/out at the base and it registers the DX17 button 7. BE CAREFUL. I have several times thrown my plane into idle cutoff during BFM and had to relit... which then loses all INS
-
I agree darkman222, but we also have a boresite and funnel that do not need radar... Usually the locking issue is high aspect related and in that case, just go for broke, dont worry about the overshoot, and just fill your hud with their plane, trigger down, and you'll hit I swear I think the bug may be that its locking where the shadow of the plane is...
-
Been like that since day one of that mode for me too. I try to TMS Up over and over (and over and over and over) until the box finally squares over the bandit. Can be really challenging when its hard to see the bandit and you start chasing the box instead. As SCPanda said, sometimes I just have to TMS Down, pull the nose and use the HUD boresite to finally get a valid lock/tracking. I've never seen that happen in the F18... I don't think this is an operator error, or "by design" of the radar.... I'd assume this is already well documented in the bugs section and part of the "continued work on AA radar"...
-
the step up/down do not change the channel for me either... but! if you just click the number you want on the ICP for the preset, say 8, then hit the enter button on ICP it will select the preset for you...
-
I've found i can run 40-61mf all day with 28ish rpm... when i use all 3k i brick engines fairly consistently.
-
Using a SP test mission, 40% fuel, guns only, 4k alt on Normandy, clear weather/default/midday. Using tacview to review Turn Rate, Radius, and CAS. Tested 300mph, 275, 250, 225, 200 using 2850rpm and 61mf. Tested with and without 1 notch of flaps. It "felt" like 275 without flaps was ideal STR... This also kept engine temps in check with occasional forced open oil. 225-200 with a notch of flaps was maybe +1 deg, and the radius was maybe 400ft tighter..but harder to manage, handle buffet, and engine was staying hot... Basically im looking for ideal STR for prolonged fight hoping the pilot isnt managing his plane well, with eventual option of getting to the deck to then extend as I slowly lose to a K4
-
MFG Crosswind F-16 combat pedals
pchRage replied to rel4y's topic in PC Hardware and Related Software
Following this thread! -
Which CPU/GPU with which G2/Q2 to get the best VR so far.
pchRage replied to Nalfeyn's topic in Virtual Reality
Gman109 did you get your new machine yet? compare to your existing? -
Not sure what demo maneuver that is.. did a quick search, didnt come up with anything. I did compare two tacviews of a flight... mine and another persons, and sync'd their time to a particular evasive maneuver. the 2 tacviews shows a ~2G difference and ~5deg AOA diff. So I think this all boils down to tacview is (highly?) inconsistent for non-own-plane recorded metrics... that's pretty disheartening and to me, casts some concerns on the tool itself for detailed analysis vs generalization ...
-
Yep have done that exhaustively Zergburger, I cannot get anywhere close to those AOAs, always <= 25... only in a hammerhead or other stall-based maneuver can i get close to 27-28-29...
-
Thanks Crptalk, I understand that is true for +/- 0.2 G or so.. but didn't know it affected AOA... Even still... I've looked at many many many tacviews, and I consistently see my plane < 25AOA and others > 30. are you saying that my local tacview is more accurate in the same flight for me vs others? and by ~10degrees margin??? seems excessive
-
I was under the impression that the FLCS limits to ~25 degrees AOA. Only in stall/over-the-top/close-to-departure style maneuvers, have I gotten to ~29. I've been reviewing a number of tacviews of myself and others in F-16 and I'm almost 99.999% of the time < 25deg, whether I'm between 200 to 500 CAS sub 10k alt. Others (several) I've seen regularly sustain 30-34 degrees, and even 42+ in a snap. The speeds are in the lower band, from 220-360 cas, and these are in all aspects; climb, over the top, descending, level turn, ortho roll, oblique turn, etc etc. I understand that AOA is not the f-16s gameplan and you dont want to be in the position in the first place.......but... when its down to a 1C/scissors, etc, especially vs another f-16, I can see that >25 degrees AOA delta as an advantage. I've checked my joystick in windows/dcs, and its hitting the full range. I do not use any curves, but do take 2% off the ends to ensure I can hit 100% deflection. Testing offline, trying various maneuvers, various speeds, (hah! even tried the manual-pitch-override)...no go! Would be nice to understand the "how" and at least have the tool in the tool-bag. Attached a few screenshots from a random individual flying a 1v1.. names redacted
-
Which CPU/GPU with which G2/Q2 to get the best VR so far.
pchRage replied to Nalfeyn's topic in Virtual Reality
Cant wait to hear your comparison of those machines Gman109! how long is your backorder date? -
I have same issues. I think ive pinched and wrecked the wiring due to so many take-aparts and replacing switches. im the wondering if I should try and just do a 100% wire replacement or find a way to sheath every wire
-
[ALREADY REPORTED]Other players can see you tracer on no tracer ammo
pchRage replied to raelias's topic in Bugs and Problems
Noticed this yesterday! This is a year old Verified Bugs report, hopefully it gets a bump in priority with the ACM radar now working much better. Definitely lose the element of surprise right as it stands right now. -
with those steps, does that mean PRE + Man mode? not Auto? Trying to understand the need after handoff to switch to wpn page, re-move position and wait for lock...
-
Select center scan, select tbl 3, limit search to just sa6. note the timer says 3 seconds, but never counts down... yet the total scan count continues to increment.
-
Launches station 3,4,7,6.. id assume 3,7,4,6 so that the planes stays more balanced? right now i just hit msl step after first launch to even it out...
-
From the patch notes "....It is possible to lock on with two missiles prior to launching the first missile..." What are the steps? I tried pre mode with auto handoff. 8 miles from 1st target, handoff, wait for the "C", then msl step to station 7. move tpod to next target, handoff, wait for the "C". rifle.. only fires station 7.. station 3 is back to "S". Also tried after getting the correlate "C" on station 7, to msl step back to 3.. but it was back to "S", and toggle again to station 7 and also "S".
-
I dont think i want to be sporting a 1080 until 2022 :-) I can wait a ~month to see how 5950 looks vs current latest Intel, and then I think i pull the trigger on new build for end of year. 3080 vs 3090 for VR debate ensues :-)
-
Thanks Mud! It works great!
-
thanks for all the info Gunnars! Will give the further clocking at try with an eye on temps
-
thx for the details. gpu. psu, new cooler... hmmm leaning other direction and thinking this can be a hand-me-down :) i10 vs 59x rathole to figure out i suppose
-
much appreciated Gunnars Driver!
-
MSI Z270 GAMING M5 Cooler Master Hyper 212 EVO