Rainmaker

Okay, so...at a loss here. Screenshot will probably help more than anything. Specs: 3570K OC'd to 4.2 (yup, living in the past still and okay with it) Z77-HD3 mobo 1060 GTX 6 GB (I think drivers are from April) Oculus Rift CV1 and/or 3 monitor setup at 5760 x 1080. Been playing with this for a day or so. VR is garbage at the moment, and it makes no sense. We could all agree that I'm due to upgrade...but at the same time things don't add for that being the current reason why my VR frames suck. When I put myself over downtown Vegas at 5760 x 1080, I'm sitting on 70 FPS with my current setup...not shabby at all for a 8 year old processor. I switch to VR, struggling for 30. Initially tried without an overclock vs overclocking to 4.2, still the same result. Screenshot tells the story on usage. MSI AB monitoring utility isn't saying anything different really. That wasn't a low spike, there's still consistent overhead there and I'm stuck at garbage frames. Anyone have any bright ideas on a cause or a fix?

If that is the case, perfectly fine and I don't agree/disagree on whether it's right or wrong as I just don't know for sure...but it doesn't work that way right now (with gun selected specifically). Selecting gun, and hitting the pickle button, designates a ground point...but that's only after you use some other source to make a ground point and then clear it. After that, pressing the pickle button, creates that ground designation diamond. If you just start a mission, select gun, hit the pickle, nothing happens. Use the ground radar (as an example), select a ground designation, clear, select gun, hit pickle button, ground designation point appears (can be cleared and done over and over again using the same method).

So, two different issues with this. 1. Designation with the HUD via the pickle button in CCIP/CDIP is still wonkey. Either: 1. It isn't supposed to function at all 2. It is supposed to work, but it still doesn't work properly until you have already made a previous ground designation using something else. Either way...a bug...as you can't have that both ways. Either it's supposed to work and it doesn't, or it does work in some instances and it's not supposed to. 2. The TDC thing, if it is/was a bug, it's still there. Only works in AG/Auto. Pickle button designation also works here too as it captures the pipper location and designates. F/A-18 DCS EA Manual: CCIP Target Designation Option: When in CCIP mode and the TDC is assigned to the HUD, and the CCIP Bombing Cross is within the HUD field of view, pressing the TDC displays the TD on the HUD and it can be slewed within the HUD field of view using the TDC. The TD will initialize on the Velocity Vector or at 7.5 degrees, whichever pitch angle is greater. When the TDC button is released, AUTO bombing mode is entered based on the new target location.

He's just trolling...as usual. No use worrying about it.

Unknown on the TDC TBH. The pickle for sure still works though, and used to back as far as I can recall. You can use it the same way with the ball and chain CDIP pipper to retain your last release point. One of the few things with this jet that are helpful...ha. Perhaps the TDC function is still a thing, and maybe still bugged depending on MM as mentioned above i dunno, haven’t personally tested that to see if the issues are one in the same, or essentially, two different mechs that are a little screwy at the moment.

Go ahead and go into the game and try it. Unless I have a one-off broken install, you will not be able to do it. With HUD selected, you won’t be able to set the target point. In order to make it work, you’ll have to use the TGP, radar, etc to first create a designated point, and then you can undesignate/clear the designation and then create with the HUD. Again, there's zero questions on how. None. Zero. Nada. It’s the fact it doesn’t work like you just said it should.

@Mods. Does that really make sense to relabel my topic? I wasn’t asking how to make it happen, I know exactly how to make it happen. My question was is it a bug or isn’t it? Perhaps next time you try to change to ‘reported’ or ‘no bug’ instead of making a poor attempt at rewording a thread title that makes no sense for the post that’s attached to it?

It worked fine in CCIP guns mode...so it's not really an AUTO thing any more if it was previously. But...it didn't work until I used some other method to first make a designation.

Either/or really. It's beta after all, so we've seen things come and go as time has passed. From what I believe to be correct, yes, it should have the capability. I'm thinking it's an issue that you are not able to do it without first setting a ground designation thru other means, but I can't confirm that. For all I know, it's something that's correct. I haven't flown in bit, other things have come along (A/G radar, etc), maybe it got broke, maybe it got removed.

That's normal. #3 is the element lead. #4 is the wingman of #3, and takes orders from #3. #2 is your wingman, which is why you can give him commands directly.

Not throwing this in the 'Bugs' section as I don't know if this is normal or not and it's been a while since I've flown the F/A-18 any decent amount. On beta version. If I go into an A/G mm and take command of the HUD, the pickle button will not initially designate a ground point based on HUD FOV. In order to make it work (as I remember it should), you have to take command of another sensor (AG radar used as an example), designate a point on the ground to get the diamond, depress the uncage to remove the designation, then take command of the HUD, and it will designate off the HUD FOV. It'll will work fine after that and you can repeat as needed, it's just the initial attempt requires you to use a another sensor to designate in the beginning. Bug? Maybe yes...maybe no? I dunno, so if anyone with better knowledge can confirm or deny and move/tag appropriately it would be appreciated.

That’s not what it says...at all.

“Received AESA”. Yeah they didn’t. Not sure where you got that info from.

I can name at least 5 other things without trying that will be incorrect without a whole redesign of the cockpit and a number of systems...but you guys key off on the one thing you can actually see that’s visually different. I guess I could pretty much cause your whole world to come to an end if I listed off the others.

It still does nothing with mission playability. There aren’t any new features added with it. It’s NVG compatible...that’s all. The old ones were as well, with an additional filter. Pre 2001, no nods, so it’s completely irrelevant. It ‘breaks’ nothing.

How does changing the UFC effect your ability to fly a mission exactly?

There are some getting wayyyyy too far in the weeds on this one. Both have the same fuctionality as far as user interface goes. No special sharks with laser beams, etc with the new one. One is NVG friendly out of the box and one isn’t...that’s the biggest real life difference. The old ones delaminate a lot too, but that’s talking real world problems and not game problems.

That’s a fact.

In case you think I'm crazy :) Beginning about 4:10 in. Gear tone followed by the 'knock it off' call. It's an F-15, but same principal behind that tone applies.

The real F-15E is 10K ft for the same if that makes you happier. Not uncommon at all for the warning tone to come on, and it’s going to if you are in the parameters for it to happen unless it’s broken. The F/A-18 is in beta, so what may or may not have happened in the past is completely irrelevant really. Whether or not it currently comes on when it’s supposed to be is. If it’s on, and you are within the limits, then it’s working as it should...no since going on and on and arguing about it.

Yes. The umbilicals will seperate from the missile at launch, much the same as arming wire lanyards separate from the bomb when released.

Not an owner of the F-16, so working off association here, so apologies ahead of time for not being able to check myself. This is a long-debated topic going all the way back to the A-10C days. IIRC, the option was added to the loadout screen to select single/ripple. Is this not still the case? Something that just may not be in the F-16 loadout options but available in others?

Just ironic timing I guess...just had this video come across my feed. Tomcat dudes during OIF. Vis got pretty nasty at one point I guess. You can hear them call contact at less than 2K in some instances. Just to add some visual/audio to your discussion.

The -220 and -229 both visually look the same at the back. The closed versions you see are export versions of the -15.

In some cases...PBIT is short for preflight bit. As in the case of flight controls...you have a P-BIT which is a preflight/periodic bit, and an M-BIT, which is a maintenance bit. As with most cases and ancronyms...they overlap depending on the context.