Dino Might

Okay, time to get serious on this. My Bosch jigsaw just came in and I'm going to Lowe's tomorrow for some plywood. Anybody got dimensions on the Mk GRU-7A ejection seat? (I think that's the one in the F-14A) I'd like to build it out this week so I can finally get rid of my desk and floor mount my joystick.

It's exported as "LEFT_MFCD": This is what I put in for mine, using a main 1920x1080 and two 8" monitors positions left and right - both mimicking same res for combined resolution of 5760 x 3240 total res. --LEFT LEFT_MFCD = { x = 2435; y = 145; width = 1250; height = 950; }

I really need to get back to this. I'm going to do each panel individually in acrylic and mount to plywood or other acrylic frame pieces connected by DZUS fasteners. I would like to make it modular enough so I could pop out panels and pop in others depending on the aircraft, but I haven't looked at what sizing and modifications I'd need to do for that. The only major swaps I would need to make would be putting in MFCDs for the A10, so I might try to incorporate those for things like the fuel management panel and HSD if I can't figure a way to make the modular cockpit work. Rear seat is going to be bare bones with VR. May add panels at a later date if I get bored. I'm not even to the drawing stages yet, and have no CAD experience. Hopeless ambition is my fuel at this point. By the way, are you designing in SketchUp? Or another program? I've got access to solidworks at work, but don't know how to use it yet.

Heretic! Burn this man in the fires of TF30 reheat!

The B will be a nice transition aircraft, but when the A is out, that will be my go-to ride :pilotfly:

Might have missed this in an earlier answer, but what is the angular resolution of the display? With regard to angular uncertainty in signal processing, the data truncation or display resolution may make such signal processing uncertainties moot.

Great vid. My guess is that the Cat will make Case 1 in the Hornet feel positively easy by comparison. Cannot wait for this bird. Most of my time will just be in a mission with my F14, one CV, one tanker, and nothing else.

No sooner did I post this did I find the answer on another forum. It's the stupid sensor in the HMD that is used to tell it whether you are wearing the device or not - this sensor toggles mouse control automatically. Placing a piece of opaque tape (I used part of a post-it note) over the sensor will render it inoperable (it's an optical sensor), and then you can manually activate the mouse and keyboard inputs with Win+Y and they won't go away anymore. Hope this helps others who, like me, were about to give up on VR.

I've searched threads and believe this issue has already been discussed, but can't make heads or tails how my situation is similar/different. When I start DCS in VR, I can use the mouse normally, with the cursor not being affected by my head position, and I can interact with the menus, load missions, click stuff in the cockpit, no problemo. It works perfectly. But if I alt-tab at any point, the mouse loses focus from VR and will never regain it, even if I alt-tab back in. I have tried alt+C, win+Y, alt+Enter, and other "fixes" to get mouse focus on the HMD, but it only stays on the mirrored portion in the monitor. So, to use the mouse, I then have to take the HMD off, move it with my hand, and mouse on the monitor to click the radio dials or other cockpit controls I want to use. Everytime I am in the HMD and I click the mouse, it makes an annoying click sound and does nothing, not even showing a cursor. This is infuriating, because I want to be able to alt-tab in and out, and get back to the original mouse functionality in the HMD as when I start DCS in VR without having alt-tabbed at all. Is there something I am missing that is an easy fix to this problem? Or is the HMD UI just bonkers? I'm about to return to TIR and junk the HMD because of this.

So, I'm not really sure how common it is to be repeating stuff, and I could definitely see it being both useful and not useful in high stress situations, but I always thought it sounded pretty cool (probably because the lines were rehearsed - I bet in reality, there'd be more stumbling). I hope you guys keep a lot of the "random byproducts." If possible, a large deck of sound files with the option to turn on additional ones (even with some stumbling or miscalls and corrections) could be pretty neat. If there is a way to load up custom sound files and then add-in via the lua files, that would be nice. I'm even envisioning someone making a huge GUI for it, with all the sound files organized into type and stimulus.

Hahaha, me too. So, not to take away from the great work on display here, but will the sound Lua be editable in such a way that an enterprising individual could replace some of the calls with Anthony Edwards lines, or maybe a few recordings from Final Countdown? Definitely want to use the module as-is for 99% of the time, but just for laughs once in a while, I'd like to hear, "do some of that pilot shit."

I'm more excited that they aren't posting updates right now, because it means we are closing in on a preorder announcement. My guess is we will have EA by the end of summer or early Fall. Gives us enough time for the Hornet shininess to wear off so that we have our full attention to give to the best plane ever made.

I'm still hoping we'll eventually be able to put a Fuzz Buster in the cockpit

comment posted in the wrong thread :(

Wondering if we are watching the same trailer. The high G maneuvers towards the back half really get my blood pumping. I think it may be the music preference, but I get really amped with strings and woodwind pieces that have a powerful, long crescendo. For me, the music and associated visuals were perfect.

GA, I have watched this trailer dozens of times and still can't get enough of it. My daughter (almost 2) really likes watching external view of DCS planes, so I showed her this, and all I got for about 15 minutes was the sign for "more" every time it ended. I also want to commend the choice of music - whoever did that piece did a fantastic job. I'm a sucker for great instrumental crescendos, and I'm also one of those that gets a little teary when there's a good score with a moving video - just one of those feelings that is hard to duplicate elsewhere. Great work. I'm sending this video to one of the former Hornet jocks I work with - I am sure he'll get a kick out of it.

I'm going to be without internet (other than phone) starting 27 May for about 4 weeks. I guess I just get to miss the initial wave of hornets smashing into everyone on AO. I hope you all post some fun videos!

I prefer SRS to everything else. AGC was a fantastic recent addition. Easy to install and use, great UI and options. It has really added a lot to the blue flag server. I still use TS3 for comms with friends, with SRS dedicated to the full team. I can't think of anything to change on SRS at the moment.

Disclaimers: I am not a pilot. The only thing I have ever flown are rectangular sport canopies on the order of 210-250 square feet. I've found dogfighting with the F-5 against players on Blue Flag that speed is king. I like a clean configuration and as much airspeed as I can possibly have at the merge, because I'm going to be losing it throughout the fight. I found myself out-turning a Flanker when I was coming into the merge at 600 kias (on the deck) and pulling very gently so as to not black out. I wasn't reading my G-meter at the time, but I was able to go from lag pursuit to lead pursuit for a guns kill on him after about a single revolution. He bled a lot of energy trying to get an OBS shot right after the merge, and I was able to get a STR well in excess of his. Not sure how fast he was at the merge. Smart enemies will pull you into the vertical almost immediately and not let you use your roll-rate to get the advantage against them in horizontal scissors. Going in with extra energy tends to be more advantageous than trying to hit the max STR number, because if the other guy goes vertical, you are hosed trying to push up with only 380 kts in your wallet.

How is pointing out an identifiable issue a complaint? I may be missing some hidden context here, but nowhere in the OP did I see anything like, "this is unacceptable! I demand my money back! I'm leaving this game...blah blah blah." <--- That is a complaint. What the OP did was point out that all footage he has seen seems to show dim IFLOLS, which will be a problem for carrier ops. It's helpful for people to post these things so that nothing important gets missed as the modules continue to develop.

Shouldn't it do that naturally with asymmetric load? What's the weight of the pod? I was guessing a couple hundred pounds. Newer pods are like 100-200 pounds. The F5 pod is an older model, right?

I can't understand the hatred for FC3 modules as regards multiplayer. If you don't want airquake, then don't play on an airquake server. It's entirely within the mission designers control the leave fuel out of the FC3 birds to make them take longer to load up and take off. You can easily strike the right "balance" with just the simple tools available. As for the avionics challenges, the M2k is just as easy as the F-15C for basic BVR and WVR air-to-air engagements. I even have the mappings almost identical for the radar panel controls, close-combat modes, etc. I can't see a "fairness" problem that is truly a concern with "FC3-mode" modules of the new releases; HOWEVER, I do see a problem with maintaining two code bases, and for that reason alone I am against the idea. With each new update, devs have to fix bugs that crop up in their modules. They'd almost certainly have more to deal with if they also managed a simplified version, because there would need to be some significant code deviations between the versions. That means less time for making new aircraft. If you really don't want to learn how to start up an aircraft, just use the autostart, or make missions with air-start aircraft. Problem solved.

^ just one of the reasons I use the taxiway :music_whistling:

That is correct. That's why the lag D/C problems are such a bother.