m4ti140

Do you guys know if the pre-1992 avioncs upgrade manual/checlists for the F-14B are available anywhere? All the copies I found are from 2002 and as a result the avionics described in them differ significantly from what we have in game, considerably limiting their usability.

Doesn't flap handle fully up (emergency up, which it sets to regardless of whether you use the normal flaps up keybind or the emergency flaps up keybind) disable manoeuvring flaps?

But full up position is emergency up, it should set it to detent instead, shouldn't it?

Other suggestions: Since you've kinda pioneered DCS with axis bindings buttons and switches to help binding things like LANTIRN to controllers and footwell PTT to toebrakes: the two more axis threshold inputs I would be happy to see are the wing sweep hat (to be bindable to slew sensor) and speedbrake - particularly the latter, as it would enable users of Saitek sticks (X52, X56 etc) to bind speedbrake to the slider without doing voodoo in Saitek software.

For me it seems to always time out on the first attempt to enter cockpit and then it works after a subsequent reconnect, although it still takes a while to load into cockpit. Loading from SSD with a page file on it, 16 GB RAM. Reducing cockpit texture quality didn't change anything. This was all on a small server, haven't tried a more crowded server yet.

Need separate cutoff and idle binds that just switch the throttle into selected position (instead of hold for cutoff). I have an X52, and the way I set it up is by putting axis bands below the physical throttle detent and then setting it to press the idle key momentarily when going out of this position and cutoff key when going into this position. For multi-engine aircraft I use modifiers, but since here it's press-and hold I can't use modifiers anymore. This would be workable with in a single engine aircraft but with the Tomcat it's an issue. I understand that the current binding is more suitable for Warthog users, but it would be nice to have the regular, separate idle and cutoff bindings as well

Settings>graphics>resolution of cockpit displays

It is now actually done with a real Russian accent by a Russian, I'll leave it at that.

It's not out of beta, this is early access.

In the real throttle the axis is spring-loaded, so if you only have absolute axes available there's no way for you to replicate the real functionality.

Add EUP-53 description to the list.

The EUP-53 is a turn rate indicator, showing the rate of turn in degrees per minute assuming the ground speed of 500 km/h. What you've implemented in game is a roll rate indicator. It stays at zero during actual turn. Here's how it should work. Notice how the needle travels left and right when it's rotated in yaw axis. EDIT: Embedding is broken, here's the link:

How is this not a bug? Did whoever moved this read the OP? I wasn't talking about what schurem was saying (he hijacked the thread). The two buttons on the throttle quadrant are missing mappings. There's no way to access them in any other way than clicking on them.

Caucasus is not a good place to compare textures. On PG there's definitely a difference in ground texture quality between low and high. Same with Nevada.

And found another glitch :) The axes for ASP target base, dive angle and target distance don't work at all. Corresponding cockpit controls don't react when these axes are actuated. The target range is the biggest issue, since it pretty much has to be mapped to the throttle grip (and to an analog axis if one is available) for effective optical ranging.

I'm gonna bring up a separate thread, since it might either be a huge problem for SRS users, or something completely trivial that doesn't matter at all: the transmit switch on the throttle is clickable, but it doesn't actually bring up the comms menu or do anything at all and the click zone is stuck when the throttle is moved. Conversely, pressing the communications menu button does not not animate the button in cockpit.

The bindings for the two buttons enabling and disabling afterburner are nowhere to be found. They would make a lot of sense to be mapped somewhere to the throttle quadrant or the throttle itself, but it's not possible currently.

Confirm, they are not there. I was trying to bind them but they're MIA from the menu

OK, I'm having troubles getting desktop app to work. First of all, it completely fails at discovering the tablets and if I enter the IP manually, it gets forgotten the next time I launch the app. Second of all, it keeps crashing and reloading to default state in the monitor editor

Are you planning to add the MiG-21 radar screen?

Title. Basically, the only way to simulate a scramble from alert without major lua sorcery is to either just use the "parking hot" or "runway" option for take off in the mission editor, or just start cold and dark and then go through the whole alert setup checklist just to do the launch checklist immediately after, which defeats its purpose. Would it be possible to add an additional "alert" option that would preset the aircraft to the standby configuration, right before the alert five launch checklist?

I think you're missing the whole point of FCLPS here. The reason you had to do those is because you were flying a real jet. It was a form of simulation of carrier landing. DCS is a flight simulator, which defeats the whole purpose of doing those, since you can just train on the real thing from the start and if you crash, you can just reload the mission. I get it that you want immersion, but there are practical limits to it. Sure, this could be done but there are more pressing issues. Not all essential systems are even implemented yet. They will surely do this eventually but I'd rather they focused on actual avionics for now.

They're making an extension (AIRIO) to VAICOM specifically for F-14 to cover RIO comms

It doesn't. And with an absolute axis, you can just center it: in X-52 there's a tactile notch on the elevation dial; when you reach central position, it jumps into it and requires slightly more force to move past it. Pretty sure it's similar on Cougar (both have been based on F-16 throttle, though X-52 is obviously not as exact of a replica as Cougar).

It's quite the opposite, I wish this game had an integrated voice client like BMS and that servers enforced its usage more harshly. People who do not cooperate with the team and essentially use fellow players as smarter bots is what makes me steer clear from most public servers. If you don't want to deal with other players you can always play offline, instead of bringing anti-social attitude to the multiplayer environment. That being said, I wish SRS allowed for more than just in-cockpit comms, e.g. a mess hall/briefing channel for people in the lobby, since I agree that Discord is insecure, bloated, and generally unsuitable for serious voice communication. Regarding speaking other languages in public voice chat - if it's allowed on the server, change server, if it isn't, report it. It is a rude behaviour and I agree that it may put people off - well, it puts me off, as it generally goes in conjunction with people ignoring the radio altogether and messing up whatever you're doing due to lack of coordination. All things considered though - this is a very detailed sim and lack of cooperation online removes a lot from the experience