rob10

Huh. I didn't realize there was a TIR beta version. Didn't think it had changed at all in many years. If you end up having to uninstall again anyway its worth trying the stable version.

Don't feel bad -- it took me a long time to realize that one.

If you click on the UNIT LIST option on the left side (triangle, diamond, box symbols) you can check and uncheck the "show hidden units" box to show or hide the hidden units in the ME. You can double click on units in that list to toggle hidden or exposed status of the unit.

RALT is limited to below 5K IIRC, BALT is not limited but may not work well at extreme heights (ie 40K). Please see my original post for possible causes and please attach a track if you want better answers or more likely a direct solution

I think they typically run at the same times, although sometimes the direct ED ones will run longer due to Steam restrictions

It will be easier to give you answers if you post a track of what you're doing. Try adding a small deadzone in your pitch controls. Did you do a proper INS alignment if you cold started? Are you seeing any advisories or warnings in your left DDI? It should mostly fly at desired altitude and press A/P followed by BALT. In the F-18 you can't "dail up" a specific altitude, you have to fly to your desired altitude and turn it on.

The majority of the bindings are done PER PLANE so what you're trying isn't possible. A few commands in the General category may be across planes

If you mean DCS, there is no BETA vs STABLE. They merged the versions a couple of patches back. Check your lighting (even reflected sunlight can mess with it) or other hardware issues. Working for everyone else using it, so I doubt it's something with DCS or TIR software.

Check the F-16 section of the forum.

ED has said NO in past. So not zero chance, but not likely coming in the near future, if ever. Mostly classification/publicly available information issue.

The easy way is to copy your Saved Games/DCS/Config/Input/FA-18C_hornet folder. But if it's getting corrupted everytime I'd make a backup copy of that file, then delete the original and recreate your bindings from scratch and see if that helps. That sounds like you have a corrupted file.

You'll need to post a track demonstrating this to get any meaningful answers likely. You can save a track in the debriefing screen at the end of your flight. Keep it as short as possible and ideally on Caucus map if it's a bug ED needs to look at. Quite possibly someone may be able to point out what you're doing wrong if you post a track.

Short version is no. They are designed for one player so the triggers would likely get messed up. Also there are copy protection issues where I don't believe there is even a possibility currently of creating a protected paid campaign from scratch for MP if you wanted to.

I can confirm it hasn't yet changed in terms of not being able to catch the wire without the supercarrier. Ran into it the other night with someone that didn't have it and I didn't know that and we couldn't figure out why he wasn't catching on good landings.

Just worked for me (5:25 pm ET). As long as you're just playing SP you can carry on and try again tomorrow. It won't make any difference to you until stored authorization runs out. Could have been a glitch in the ED server or could be something on your ISP's end. From the time remaining (2d 6h 39m) it would appear this had happened to you 17-18 hours previously. Normally it would say 2d 23h 59m on first fail. That would make me think it's on your ISP or firewall or something on your end even more.

Somewhere down the road they may let a new dev loose on it to learn their craft and they'll look at wish list to see what good ideas for improvement are there. Don't expect it near or likely medium term, but ED has been known to surprise us over the years with something they said they weren't going to do.

As Flappie said, check your anti-virus. McAfee and ESET specifically seem to be causing issues with one of the latest updates. Norton too on this one and Kapersky is often a culprit.

Since you're just starting out, be aware that Bomb in Zone is ORDINANCE (bomb) specific. So you need to specify what bomb type you're going to use rather than it being any bomb that enters the zone. Another trick (especially with buildings) is to put an infantry or unarmed unit and trigger off the death or less alive than of it. Since they will take damage pretty easily it lets you use whatever ordinance you want to take it down. Or if you want a bigger explosion, put two or three of them all with max explode triggers. The explosion trigger even at max is visually pretty small (may well be realistic) so if you're simulating hitting a bomb making workshop or something it's nice to crank up the boom.

Search function on the forum can be a little hit and miss. Sometimes your better off to use Google. And for specific issues it can be worth checking the individual modules.

Check out this thread:

Yes, you need to be on the same version as the MP server (including any hotfixes). That's very likely why you only have a limited number of servers showing.

I think the general advice on this is that you want a combined 64GB from physical RAM and pagefile as a minimum. I agree with SilverDevil that more physical RAM is better. I have no actual evidence, more a feeling, but it seems like a min 64GB physical RAM is best, and more isn't a bad thing.

If you can post a copy of your .miz file it will be easier for people to make suggestions on how to make it do what you want. Chances are it's something simple.

Just a blank waypoint almost at the end of the list. Nothing special about it. They are skipping over WP 59 since it defaults to the Bullseye set in mission editor, so if you go backwards, once you get through the markpoints, it's the first one you come to. It's also not likely to get used since it's so far up so an out of the way waypoint basically.

Currently a reported issue with JTAC and lasing.