A2597

I just want to own this. No where near good enough to make it:

Having a blast with this thing. Took me a moment to get the hang of it, (first plane with TPOD) but pretty straight forward to use. Love it! Now I have to learn all these new bombs, which I had no use for 95% of the time before.

I had no issues accessing it with pilot body off. But yea, with it on you can't at all. (Hence a hotas bind to show/hide pilot)

Got to fly tonight for a couple hours with some BuDs. In a word, Awesome! I still found myself reaching for the mouse a couple times out of habit, then going "No, I don't need to do that...". Cold start was awesome, reaching for the switches. Slowly getting the hang of the mouse wheel option. But just reaching around to close the canopy, turn on oxygen, crank the engines, etc... exactly what I was hoping for! I will be unbinding gear and flaps from my HOTAS, no need anymore. Was a little worried about hitting those as quickly as I could with a bound switch...was not an issue at all to do so. Super easy and much more immersive. Simply superb. So, crits/suggestions after using it for a couple hours (as promised). The mouse wheel option threw me, I thought it would work where I hold the button down, and then move my hand up to scroll up, and down to scroll down, with how high or low I moved it from that point being how fast it scrolled. I totally get your implementation now that I've used it, but took me a bit to re-program my brain to recognize it. Calibration...honestly not that bad. I did watch the video, and my issues were pretty minor. (Starting it before being in mission, timing out because my joystick was in the way, etc). Overall install and calibration went pretty smoothly. Oh, and my previous comment about jitters, still had some after charging, but much improved. Thank you MilesD, awesome product!

Got my PointCTRL's today, install was a breeze on the Oculus CV1, no issues there. Calibration still took me about three tries to get right. First one was my fault, I just fired up into calibration without starting a mission, menus don't work well for it. Second time the FCU timed out before I got the bottom target correct because my joystick was in the way. After that, everything working. Going to take me a moment to get used to the mouse wheel stuff for parking brakes and wing fold, but otherwise was clicking away in no time. I'm also getting a little jitter, it helped when I turned the IR LED brightness to max, charging the FCU's now to see if that fully resolves the issue. I did an IR interference, but the only IR it sees is the FCU (which makes sense, I have a single window 30ft behind me, and it is currently very overcast). When I brought the FCU closer to the HMD the jitter stopped and all was well. Will let you know if I have issues when I fly with a group of guys tonight. So far, so good! Thank you sir!

Shipments have been going out, next batch is being shipped now (see first post)

Yea, eagerly awaiting mine, post office can't move fast enough! :D

Yea, it's the source code. It needs to then be compiled into a usable program using something like visual studio.

Strange, the repo is still up here though: https://github.com/akaAgar/headquarters-for-dcs Most recent commit was yesterday. My guess is he broke something in that commit

Are you re-arming / refueling? Are you adding more fuel than you initially took off with? Different weapons? Reset trim on ground?

Massive difference. I went tm.x to warthog throttle and ch fighterstick. Massive difference.

Used CV1 can be had for around 200, and is a pleasure once running smoothly. But I have to ask, what are your system specs like? VR is demanding, and it's possible Track IR will provide a better experience as a result.

...The anticipation keeps growing... Just got my Warthog throttle, adding these to the mix is going to be amazing!

No CGI for the flying apparently. According to Cruise: https://metro.co.uk/2019/07/19/top-gun-maverick-action-real-deal-sequel-favours-stunts-cgi-10425043/

My guess, he gets shot down over Iran, sneaks into their airbase and steals one of their Tomcats to get home.

It's in internal testing. It's delayed because they are still finding bugs. Your options are: A: Get a buggy component, which will result in many post about said bugs. B: Wait for them to resolve the bugs they find in internal testing, so that you can get a component to test in open beta and let them know about the bugs they didn't identify. Personally, I'd opt for B. And I'd wager very little of the code from the Lightning pod can really be used on the F-18. Completely different systems to wire up than the A-10C. Faster than from scratch, but only because of a blueprint and less research needed.

I can't compare to the X45, but did pick up a fighterstick, and I love it. Smooth motion, and flying improved dramatically from a TM HotasX.

So looking at the throttle and engine gauge, I tend to cruise with the RPMs around 85-95. I'm guessing that RPMs at 100% is full military power, and from what I can find, you would not stay at full military power for periods longer than ~20 minutes before backing down a little. But where do you back down to? Where is best practice to keep the throttle for flight in a non-combat / patrol scenario?

Figured I'd give an update. I wound up getting a used CH Fighterstick, Highly recommended. Was going to pair with a TWCS Throttle, but wound up finding a good deal on a used warthog. My previous recommendation stays, get the T.1600 series to learn "what you want" at a lower price point. A TWCS with Fighterstick would do anyone well I think. at a reasonable price of entry.

I doubt you'll really get smooth flybys. You have to think, 40fps on a monitor means the object is moving a few inches at 40fps. In life scale, its moving several hundred feet. That said, they still never get old. Makes me feel like I'm at an airshow. Haha And VR is amazing, expect many more moment of giddiness over small things you just dont normally think about. (Try opening the canopy after a mission and physically stand up to watch the waves on the boat. Or other planes landing at the runway.)

I'll try to provide full feedback when I get mine, without having viewed the new documents / procedures on how to calibrate things. Can't guarantee it will be critical though, may go perfectly smoothly and I'll have nothing but positive feedback. LOL

I imagine that would be possible. We'll know more with the next release. (He's been making lots of commits to the github, so expecting it soon)

so work flow = 1: Identify map object ID 2: track a hit event on that object ID 3: trigger explosion to weaken object, which may be enough to kill it depending on what the initial hit was 4: detect object death, and trigger secondary explosion. And do this for over 100 objects. This sounds fun. :D

So trigger explosion on mission start. Probably have to stagger them, as the goal is a refinery so there's lots and lots of targets... Will take some experimentation, but thank you! :)

I know right! I'm doing the same thing.