sthompson

Other responses seem to have missed this detail in your procedure. Earlier you said that you are only doing shore takeoffs. Are you really not touching the stick for a shore takeoff? That approach is correct for a carrier launch, but not for a runway takeoff. On a runway I pull back the stick gently at about 100-120 knots and it takes off without significant pitch up. Wheels up as soon as I'm airborne. Flaps to auto around 250 knots. Flight control setup for runway takeoff is as follows: After engine startup I push FCS reset twice and takeoff trim button once and flaps to half before taxiing. That's all. (FCS BIT test seems unnecessary.)

Now that IFF and SA are modeled (part of recent huge update) the Hornet no longer automatically distinguishes between friendlies and hostiles. You have to do some work to identify which is which. The earlier releases did it for you as an unrealistic shortcut because the relevant systems were still in development.

imacken: Everything you have reported is consistent with the effects of wind on the pipper, assuming the targeting computer is compensating for wind. The pipper is offset more than the VV in your first picture because rockets are faster than your jet. Bullets are faster still and so their pipper is offset from boresight even less. Furthermore, I would be a little surprised if the modeling is completely accurate when you fire during active pause. Your HUD says you are traveling 451 knots while in active pause you aren't moving at all. I have no idea whether the rocket physics or targeting computer simulation are affected by active pause, however. BTW, In looking at your two most recent screenshots I cannot make out the rocket impact points.

Probably due to wind causing both the VV and computed impact point of the rockets to be offset from straight ahead.

Neglected? Perhaps you should go back to flying version 1.5 for a while and then reconsider whether the free assets have been neglected.

I used to use padlock a lot back in the Flanker 1.5 days. However it was the combination of padlock with the mini-hud that made it useable, because the mini-hud always showed you where the nose of the plane was compared to the current view. This let you keep your padlock view on the bandit without losing spatial orientation. It also helped to use snap view forward during padlock. The snap view took priority over padlock so that you could see where the nose was pointing, and then the view snapped back to padlock when the snap view button was released. So you could glance forward and then have your "head" automatically turn back to the target without having to reacquire visually. It was a nifty setup, that does not work so well in DCS, in large part because the mini-HUD is non-functional in most aircraft.

There is a way: Next time you hook up to a cat, pause and look to your side to get a visual reference point. Memorize it. Next time taxi forward slowly until you see that same view and you will be close enough. Of course when the new carrier module comes out you will be able to rely on the deck crew to help you. (Perhaps!) :smilewink:

Future Plans for VAICOM PRO Hollywood: I'm really enjoying the AIRIO extension. So much better in the Tomcat than that arcade-like wheel. Today Wags posted an update on the new carrier module under development. (See https://forums.eagle.ru/showpost.php?p=3868424&postcount=150). Will VAICOM PRO be supporting the new carrier comms?

Of course when HeatBlur eventually releases the F-14A version they may want separate kneeboard files and folders for that. It would be good if KBB and HeatBlur got on the same page about this.

Yes, it's a bit out of hand. I'm finding it increasingly difficult to find information I need through this thread when I experience a problem. And since I fly intermittently, sometimes a problem has come and gone from the thread by the time I notice it myself. It would be terrific to have a dedicated sub-forum, or else a separate support mechanism. Is there something else available?

"Repair" I understand. But what do you mean by "cleanup?"

I've used both together and they coexist just fine. However I'm usually using simple coms, a single PTT button, but use separate PTT setups for each rather than try to use the same keys/buttons. That avoids the problem of having others on SRS hear me talking to the AI, but at the cost of some realism. After all, if others don't want to hear you talking to the tanker then they should get off the tanker frequency, just as in RL.

It's supposed to do that and its a property of an accurate flight model. An airplane does not fly on tracks and is not moving in the same direction that the nose is pointing if you are in any kind of a turn. The difference between the nose direction and the velocity vector explains why the nose turns back when you ease off the rudder. Here's a bit more explanation: The rudder used alone creates this effect because simply yawing the airframe with the rudder does not move the velocity vector instantly. If you step on the left rudder pedal the nose will turn left but the plane will be moving in a direction to the right of the nose. (Try stepping hard on the rudder in a jet that has a velocity vector indicator on the HUD and you will see what I mean.) Instead, the velocity vector lags behind the longitudinal axis of the jet while you are on the rudder. This creates sideslip. It is the sideslip that causes the nose to turn back a bit when you ease off the rudder as the plane weathervanes back towards the velocity vector. You just need to allow for that. BTW, the sideslip also produces asymmetric changes in the airflow over the wings on the two sides of the plane, and thus affects the lift vector too while you are using the rudder. That tends to induce a roll if you do not counter it using the stick. So smooth flying requires coordinated use of stick and rudder in a turn, not just one or the other. This is especially true in less powerful planes where you can't rely on just hitting the afterburner to get moving in the direction the nose is pointing. It's a big deal in prop planes.

The NATOPS manual seems to answer this question. If the A/P is engaged but none of the UFC options are selected then the A/P operates in CSS mode. That is Control Stick Steering. The A/P maintains pitch and roll (if roll is more than 5 degrees) or pitch and magnetic heading (if roll is less than 5 degrees), but you can change these with gentle inputs on the control stick, and can fine tune using the trim hat. More aggressive movements of the control stick will disengage the A/P, which explains why I sometimes get a violent pitch response when pulling hard in a turn!

Kneeboard builder won't start after DCS stable 2.5 install I had Kneeboard Builder working fine with DCS 1.5, OpenAlpha 2.2, and OpenBeta 2.5, but when the stable 2.5 version came out I can no longer run it. Crashes on load screen. Deleting the Config file and restarting gives the error "DCS World not installed at `bin\DCS.exe'. I then click OK and the program starts. But when I try to set the DCS World install directory and push "save" it crashes and won't restart. Always crashes immediately on the splash screen. :(

Need to redo manual config after DCS update After DCS 1.5 updated a few days ago I was having some weirdness with VAICOMPRO 2.5 in that version. It looks like the update undid the manual installation of VAICOMPRO with respect to the files in the DCS directory tree, and so I had to install again. If this is going to be a persistent problem then it would be VERY helpful if the automatic installation was slightly more intelligent or flexible. For example, my DCS installations are on the D: drive (an SSD) but otherwise are identical to a standard installation on C: (not an SSD). It would be helpful if I could input the path to DCS somewhere in the VAICOMPRO configuration so that it would update the files automatically for me after a DCS update. Could that be done? Also the manual gives no explanation for the "Auto-Import new theater" "Include custom folders" or "Auto-import new modules" check boxes in the Configuration menu, or for the two empty boxes to the right of "Include custom folders." Can you give some idea what these are used for and how to use them? Would they solve the problem I identified above? Apart from these issues I'm enjoying learning the new system. Great work Hollywood!

Alpha does not "include" any maps. You have to buy Normandy and/or NTTR if you want to run the open alpha version. There is no Caucasus map for alpha, but it has been promised for 2.5 and I don't remember whether it has been announced whether you will need to buy it separately. But you can install all three of the current versions for free. They each include some free planes, and any flight modules you have or buy will work on all three and any map. (The only exception I've heard about is the Harrier, which just came out, but that should be available on all three platforms soon.)

That's only an error if you get it when you give the "Mission Start" command. it's normal to get that when you first start VoiceAttack or load a profile with DCS not yet running because there is no mission yet.

Control keymapping problem RESOLVED I found the problem I reported at the top of this thread. Apparently Logitech Gaming Software is not compatible with recent releases of Windows 10. Uninstalling that software solved the problem.

No, I only have US English installed in language settings. And this would not explain why the keyboard works fine in almost every application except DCS. BTW, I have tried several keyboards, including the on-screen keyboard, and they all have the same issue.

I recently had to reinstall Windows 10 due to a serious crash after a recent OS update that left my system dead. I had not used DCS for a while prior to this. DCS itself was installed on a separate drive that was untouched. Before trying DCS again I repaired and updated it. This went fine. I now find, however, that certain keys do not work as expected within DCS. For example, if I push the "" key for Communications it responds as if I pushed "]" instead. And if I push "]" it responds as if I pushed "[". The set of problem keys is not very large: They are keys for the following six characters: "\][=~ All of these keys work fine in other windows programs and apps that I have tested, with the exception of the CH Control Manager, which is misinterpreting them the same way as DCS. (However, turning off the CH software does not solve the problem in DCS.) Looking for ideas as to what is going on. I have no mods installed, and I started by deleting Saved Games\DCS to clean out anything that might be in there. Did not help. UPDATE: The problem turned out to be caused by Logitech Gaming Software. Uninstalling that solved the problem.

bug fixed in Nevada towers command Your log helped me identify a bug in the Nevada towers command set. You can find the corrected file at the original post here: https://forums.eagle.ru/showthread.php?p=3158825#post3158825. To install it, first delete the existing "IndianSprings" command from your profile and then unzip and import the replacement command attached to that post. The bug caused the recipient to not be identified (and thus default to the most recent recipient) whenever the recognized command included more than just the callsign for the field. Hope this fixes your problem Tribundf! To answer your other question: I use one copy of VoiceAttack (I'm using the latest release version 1.6.7) and have a modified version of fetch_data.cmd that loads whichever mission file is most recent across the various DCS directories. It includes a command to copy the openalpha mission of the form IF EXIST %USERPROFILE%\AppData\Local\Temp\DCS.openalpha\tempMission.miz ( ECHO f | XCOPY /D /Y %USERPROFILE%\AppData\Local\Temp\DCS.openalpha\tempMission.miz TEMP\tempMission.zip ) This copies the openalpha mission only if it is newer than the one loaded from the release version. Seems to work for me.

Haven't been able to reply for a while due to real life constraints. Tonight I double checked that VAICOM is working for me on DCS 2.1.1.6837.230 on the Nevada map with my latest static ATC mod files and with the Nevada airfield mod to VAICOM that I circulated previously. I start a simple mission in the F15 cold start and call each of the airfields to get startup permission. Everything seems to be working fine for me so I don't know what your problem is. Seeing the log might help. Are you using the right callsigns? The VAICOM mods I distributed for Nevada assume you use callsigns rather than the name of the field (when they are different). To call Tonopah Test Range you would use the callsign Silverbow, for example. See https://forums.eagle.ru/showthread.php?p=3099732#post3099732 The static ATC mod files that I circulated need to be placed in exactly the locations of the originals by Whartsell, which are the locations of the files by the same names in a clean DCS installation. These locations are indeed under the Scripts folder, but you need to find the right subfolders.

Feature request Would be nice if I didn't have to exit SRS and restart it if I've forgotten to plug in my headphones and mic before starting the program. Perhaps add option to refresh the device list and automatically select "favorite" devices if they are available?

Of course it isn't entirely reliable. Mission designers are attempting to provide a realistic experience. Do you think in real life that pilots have maps that show the location of every threat or target? The behavior is by design and is not intended to be capricious. If you really want to see everything on the F10 map then it is often possible to edit the mission yourself and unhide the hidden assets.