reilar

I used the AI version of the missiles.

You can use RCtrl+Enter to check you control input.

The problem I had seemed to be related to moving ship targets and also if I air-started the AI Viggen too close to the IP. I've filed a bug report on this: https://forums.eagle.ru/showthread.php?t=200624

DCS 1.5.8 release and OB, and 2.2 OA: 1. When target ship is moving, AI will not initiate attack with RB04 or RB15 (see mission file AJS37 Ship-strike Moving Tgt.miz). If the target ship is stationary, AI will initiate the attack with all other parameters the same. 2. If AI Viggen is air-started and is closer to IP than about 9.8 km, AI will not initiate attack with RB04 or RB15 (see mission file AJS37 Ship-strike Close to IP.miz). If the air-started AI Viggen is further away from IP (e.g. 10 km), the AI will initiate the attack with all other parameters the same. Neither of the above is a problem when using other Viggen weapons, or if the AI is any other aircraft than a Viggen. The attached files are created in the latest 1.5.8 OB version (1.5.8.13716.422). Edit: Regarding 2 above: After further testing it seems related to time rather than distance. If the AI Viggen is closer to IP than 45 sec it will not initiate the attack. Distance doesn't seem to have anything to do with it. AJS37 Ship-strike Moving Tgt.miz AJS37 Ship-strike Close to IP.miz

Thanks Piston85! It worked for me as well when using your mission. I could even add more Viggens loaded with either RB15 or RB04 and the missiles were fired away as they were supposed to. Unfortunately I couldn't figure out why it works in your mission but not in my own. I will investigate more tomorrow. Anyway, thanks for your effort.

Still doesn't work for me. I've tried to remove and add the Viggen unit. I've also tried with different targets types (Grisha, Tanker, Civil ship). No joy. I have left the Anti-ship default task. I've tried to set Perform Task / Attack Group or Attack Unit. Also tried the different tasks in "Start Enroute Task". Nothing works when using RB04E. I've managed to get it to work with RB75 though. I suspect that it is the RB04E (the AI version) that doesn't work with AI Viggens. Have you got it to work with RB04E? You think you can attach a simple mission for either Caucasus or Normandy where it actually works for you.

I can't get this to work with the Viggen. I set up a single AI Viggen with 2 RB04E (the AI variant). Then I remove the default Anit-Ship task. 40 km from target (a Grisha) I have a waypoint (WP1) with: Perform Task / Attack Unit UNIT: "the Grisha" WEAPON: --Antiship missiles (or ASM) REL QTY: All I also set the next waypoint (WP2) 20 km closer to the target so the Viggen will head against it. When the Viggen reaches WP2 no missiles have been shot and the Viggen heads for the next waypoint. AJS37 Anti-Ship.miz

+1 ^ Would also like have that.

Funny! I was just looking for that a little earlier today. Could have sworn that I'd seen that as an option before. Now I couldn't find it anymore. Yes, wonder when that get away? Would have been nice to have it back.

If you have a spare axel on your Joystick/HOTAS you could map the rudder trim to that axel. Otherwise, if you're restriced to button mappings for the trim, I agree that the steps a too coarse. If it could be implemented like it is in the Viggen module, where the change rate increases the longer you hold the button, would have been very nice.

It turned out VA didn't hear my microphone and Asus Sonic Studio 3 was the culprit. When I uninstalled Sonic Studio everything started to work as expected. I have now tested out VAICOM and it works like a charm. Very convenient to work with. A little voice recognition training I think helps (I'm not sure how much though) and now most of the keywords are recognized. A stellar application. Worth every cent. Thanks for your effort, Hollywood.

Downloaded and installed VA (1.6.9) and VIACOM Pro 2.5 today. Installed VIACOMPRO in the Apps folder (C:\Program Files (x86)\VoiceAttack\Apps\VIACOMPRO) Imported VAICOM PRO for DCS World.vap. Configured my Warthog Throttle as Joystick 1. VA seems to recognize my HOTAS buttons by the look of the output window in VA (and the squelch sound). But none of my commands are getting recognized. I get no response in VA or in DCS. In VAICOM Preferences' Keyword Editor, Windows Speech Recognition can hear my keywords and VA recognizes different keywords with high confidence. I have tried all three DCS versions but nothing happens when I issue my commands. For example in A-10C (a two-ship): 1. MIC button down (UHF) VA says: Joystick: 'Transmit TX2 press' Listening resumed 2. I say: Two, close formation (nothing happens) 3. MIC button release: VA says: Joystick: 'Transmit TX2 release' Listening suspended Nothing happens. No confirmation sound or beep other than the squelch when I press and release the joystick button.

If the ship is moving you will slip backwards if you apply brakes or the parking brake. It seems that the brake force in some way are related to the ground and not the ship. Probably related to this: https://forums.eagle.ru/showthread.php?t=196922

In the thread https://forums.eagle.ru/showthread.php?t=181548 Cobra says: KB Release mode switch is now clickable (may not function correctly yet) So I guess it doesn't work yet.

I had the same problem. Changed a few joystick buttons and clicked ok. Music continued in the background but the screen was black. I forced DCS to end and restarted. Now the problems was gone.

^^This! Haha... Nicely put. Can only agree.:thumbup:

It sure was a fine day.

I also have a problem with this in A-10C. My default starting position is very close to the HUD. If I move the viewpoint further back I will not be able to see all info in the HUD. I have to lean forward (a lot) to be able to see the whole HUD image at once.

You have to enclose the file paths in dubbel quotes. Also, remove the start in the second command line (at least on Windows 10). It should look like this: copy "C:\Users\Mike\Saved Games\DCS.openalpha\Config\Source\options-VR.lua" "C:\Users\Mike\Saved Games\DCS.openalpha\Config\options.lua" "C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin\DCS.exe"

Maybe this thread can be of help: http://forums.eagle.ru/showthread.php?t=128371

Ok, thanks for the answer. So I ran some tests to see if I had understood the process correct. I started out at 30k feet with a throttle setting that gave me 90% rpm. I then descended to 20k feet without touching the throttle. I waited for the airspeed to settle. Now the rpm had decreased to 88%. I did some more measurements on 10k feet and 1k feet (see table bellow). I finally descended to 500 feet still not touching the throttle and waited for the airspeed to settle. The engine rpm had now decreased to 76%. To summarize: 30k feet -> 90% rpm (2200 pph fuel flow) 20k feet -> 88% rpm (2900 pph fuel flow) 10k feet -> 84% rpm (3000 pph fuel flow) 5k feet -> 80% rpm (2400 pph fuel flow) 500 feet -> 76% rpm (1600 pph fuel flow) So it seems that the engine rpm is changing even if I don’t move the throttle. Is this behavior expected and within operating tolerances or is this perhaps a faulty behavior in the simulation? Another strange behavior is the fuel flow (the values inside parentheses). I guess it is expected that the fuel flow shall increase with decreasing altitudes and so it seems to do. But under 10k feet the fuel starts to decrease again with decreasing altitudes. I’m not sure about this because I don’t fully understand how the fuel flow is regulated by the fuel flow regulator. But it sure looks strange. Can someone confirm this behavior? Is it expected or is it a faulty behavior of the sim? And by the way, I love these kind of simulations and I’m not trying to pick on the fidelity of the sim. I’m fully aware that I’m not fully understand the ins and outs of the process here and I’m asking this first and foremost to be able to understand how things are supposed to work. And if this is a bug I’m only glad that I can help the beta process to rule it out.

Hello! Can anyone explain to me what the pilot is regulating with the throttle in the Sabre. From diagrams in the F-86F manual (the same picture that you can find here: http://www.digitalcombatsimulator.com/en/products/sabre/?PAGEN_2=3#739739) I can see that the throttle quadrant regulates a fuel control valve (or actually the fuel regulator) in the by-pass fuel flow. I assume that the pilot goal is to set a specific engine rpm. He then set this rpm value by changing the throttle quadrant until he gets the rpm he wants. Do I understand the process correct by saying that the pilot sets the fuel flow to get a wanted rpm? The fuel regulator then regulates the fuel flow to keep a constant rpm regardless of changing altitude and airspeed. Is this correct?

Here is another site: http://www.sicuropublishing.com/ I just picked up the manuals for F-86F: http://www.sicuropublishing.com/servlet/the-3482/North-American-Aviation-F-dsh-86/Detail ...and it differs from the F-86E manual so I Think it's worthwhile to get it if you want to study the F model (and it covers the Block 35 as well).

Great! Exactly what I was looking for to add the Huey autopilot modes to the Warthog throttle A/P switch (PATH / ALT/HDG / ALT). UH-1H --Autopilot (using middle A/P switch on Warthog throttle) {down = device_commands.Button_28, up = device_commands.Button_29, cockpit_device_id = devices.WEAPON_SYS, value_down = 1.0, value_up = 1.0, name = 'AutoPilot ATTITUDE HOLD middle', category = 'Cheat'}, {down = device_commands.Button_30, up = device_commands.Button_29, cockpit_device_id = devices.WEAPON_SYS, value_down = 1.0, value_up = 1.0, name = 'AutoPilot ORBIT middle', category = 'Cheat'}, Assign: 'AutoPilot ATTITUDE HOLD middle' to the PATH position on Warthog throttle Assign: 'AutoPilot ORBIT middle' to the ALT position on Warthog throttle. Then you will get 'AutoPilot LEVEL FLIGHT' to the middle position of the switch (ALT/HDG). Thanks:thumbup:

File size or picture dimension don't seem to matter. As said in OP the picture dimension is resized to 4:3. But what seems to be important is the file extension. It took me quite some time to figure out why I couldn't see any of my own pages. It turned out that .PNG doesn't work but .png does. The file extension is case sensitive. Go figure:huh: