Wingmate

I just tried doing this, using the keyboard by itself worked but I had issues with both rudder pedals, and HOTAS, to check further I dug my old X52 Pro out and encountered the same issue with it. Thanks.

The deadzones are because there is a lot of slop in the stick (an early X55) and the detent in my rudder pedals is nearly unnoticeable at this point. I am not running any joystick software and have no macros set. In the new video I use only trim and have my control indicator showing unable to engage ap at all, part way through I unmap the pitch and roll axis from the joystick and using only keyboard am still unable to engage ap this time. I appreciate all the help.

Thanks for editing the comment so the video shows. I have deadzones set of 5 pitch, 8 roll, and 5 yaw, when I am hands off there is no input from the stick or pedals.

Here you are I was able to engage it a few times during that test and there are points whereafter it had disengaged I was unable to re-engage it without a lot of key presses. AP Test.trk

Hi, I am unable to engage the autopilot for more than a second or two. Every time I try to engage it with the Autopilot Reference / Nosewheel Steering button either nothing will happen or it will turn on for a very short time before turning off again, both the A/P REF light and the actual autopilot input reflect this. I have tried mapping other buttons to this and it has no effect. All my SAS channels are turned on and I am attempting to engage it during straight and level flight. I have tried this from hot start and spawning in the air on the Caucasus, Persian Gulf, and Nevada. I will try cold and dark later today. I have also tried reinstalling the F-14 to no effect.

You are understanding it correctly. I would suggest that yes, I made it myself while taking Graphic Communication and Print Technology and having access to things like hydraulic cutters and printing presses made it a nicer product in the end. The tabs I ended up cutting with a craft knife and a ruler, and just freehanding the corners as our corner rounder was not able to do inside curves and the tabs were not deep enough for the outside corners of the tabs. Glad I could be of help.

Alright, the larger pages are 5"x8" and the smaller pages are 4.5"x8". All pages up to and including the first tab are 5"x8", then they go to 4.5"x8" with the remaining tabbed pages remaining at 5"x8" I recommend printing the cover to the first tab with heavier stock then making every tab and the last page a heavier stock as well. Hopefully that all makes sense, if not I will try explaining it better and with more pictures. Anyways here are some other pictures the will hopefully help and some files already set to the right size with cut marks. First I found this picture while researching a different topic in my typography class a picture of an actual F-14D pocket checklist, it was incredibly helpful in understanding how to assemble the pocket checklist. https://hess.fm/blog/boldface (Fairly interesting read in my opinion) The only thing I couldn't get at the time was the larger piece of blue plastic they use for the back cover. You can ignore the file called changes if you do not want the list of changes made to the document over time, though it might screw up the page ordering as I left them in my copy. As another note this is 2001 copy of the checklist so not everything will match up with the aircraft we are getting. If anyone has a more time appropriate B model checklist I'd be interested in seeing it. Thanks for the idea about the iPad Rudel, I think I will put the full size manual on it for convenience. Hope this helps. NAVAIR 01-F14AAP-1B Tabs Color.pdf F14AAP-1B Tabs Removed.pdf Changes NAVAIR 01-F14AAP-1B.pdf

I'll check the pocket checklist when I get home it has different sized pages and tabs behind each arrow on the cover that you might want to use a heavier paper for as well (I will post a picture showing how they are setup once home as well) the full NATOPS is 8.5"x11" or at least what I printed was. It was a fun project to make still havent gotten the full NATOPS bound yet.

VF-191 was also an A model squadron they existed from 86 to 88 along with their sister squadron VF-194 Red Lightnings, maybe we will get such shirts when the A model comes out. Personally I've been hoping for a 142 shirt.

That worked. Thank you very much. -Josh

Hi Ciribob, I've been trying to get SRS set up for my group but have been running into a strange issue with the server. When I launch the server I get a windows error saying that the program has stopped working and windows will close the program, if I click on the close program button or x out of the error window I will get about a minute before the server actually closes, in this time I am able to click on all the buttons and change settings that are then saved. The only hing I have not been able to do in this minute or so is to get a client to connect to it. I am running Windows 10. The server logs are below and are from a newly downloaded and clean reinstalled, install. 2018-01-10 17:02:55.1534 | Ciribob.DCS.SimpleRadio.Standalone.Server.Network.ServerState | Unable to read banned.txt System.IO.FileNotFoundException: Could not find file 'E:\Program Files\DCS-SimpleRadio-Standalone\banned.txt'. File name: 'E:\Program Files\DCS-SimpleRadio-Standalone\banned.txt' at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost) at System.IO.StreamReader..ctor(String path, Encoding encoding) at System.IO.File.InternalReadAllLines(String path, Encoding encoding) at Ciribob.DCS.SimpleRadio.Standalone.Server.Network.ServerState.PopulateBanList() 2018-01-10 17:02:55.1939 | Ciribob.DCS.SimpleRadio.Standalone.Server.Network.ServerSync | Server Listen error: Only one usage of each socket address (protocol/network address/port) is normally permitted System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Ciribob.DCS.SimpleRadio.Standalone.Server.Network.ServerSync.StartListening() 2018-01-10 17:02:55.1939 | Ciribob.DCS.SimpleRadio.Standalone.Server.UI.MainWindow.MainViewModel | DCS-SRS Server Running - 1.4.5.0 2018-01-10 17:02:55.2109 | Ciribob.DCS.SimpleRadio.Standalone.Server.Network.TCPVoiceRouter | VOIP Listener INIT 2018-01-10 17:02:55.2574 | Ciribob.DCS.SimpleRadio.Standalone.Server.Network.TCPVoiceRouter | VOIP Listener Binding to 50021 2018-01-10 17:03:03.6185 | Ciribob.DCS.SimpleRadio.Standalone.Common.UpdaterChecker+<CheckForUpdate>d__2 | Running Latest Version: 1.4.5.0 2018-01-10 17:03:04.0805 | Ciribob.DCS.SimpleRadio.Standalone.Server.Network.TCPVoiceRouter | VOIP Listener Shutdown Requested I have created a banned.txt and it solved the first error message about it not being present but that was it. Any insight into this would be appreciated. Thanks -Josh

The game will crash after a fired M257 Rocket begins to deploy its parachute and starts its burn. It happens on every aircraft I have tried it on so far always at the same point in the rockets flight. It is easy to reproduce by just adding a 257 pod to the A-10 (or other aircraft) and firing one off in the mission editor.

If you have a copy or can find one of NAVAIR 01-F14AAP-1 chapter 22 has lots of diagrams for the HUD and VDI in the different modes.