Captain Orso

If you can use Oculus Touch controllers as stick and throttle, I don't think it will have anything to do with the module you are flying. Support for the Oculus Touch controllers will be through DCS above all else. If RAZBAM has a device-bind defined, you will be able to assign it to a Touch button to it. If DCS emulates Touch motion as analog stick and/or throttle input, you will be able to assign it to an axis RAZBAM has provided for assigning a stick or throttle lever to as well.

It might be because of how you activate zoom. I've fired --guns especially-- hundreds of times in zoom without issue. I have a Thrustmaster Warthog Throttle & Stick. I use the throttle <thumb-hat-forward> for VR-Zoom (forward = zoom, release = return to non-zoomed). When I was using TrackIR it was about the same. If you use something like the <pinky-button> or <paddle> as a modifier and then use something like <paddle><thumb-hat-forward> for zoom, then when you press the trigger while zoomed, your controller is actually sending <paddle><trigger>, which is not fire the gun. BTW, there's an own AV-8B-NA Harrier subforum above for specific Harrier questions like this one ;)

Actually, it's not. The mouse pointer stays in the exact same place within the window, if you don't move the mouse. When you turn your head, the visual cockpit representation moves.

May 8th is end of war in Europe day so... :music_whistling:

I think it must be the Channel Map. In the first 20 seconds or so Wags is flying over a bunch of towers that look like they must be radar towers. They are not setup for carrying cables so they cannot be for power cables. Also there is too much abrupt difference in terrain height at some points, so definitely not Normandy. I'm betting on south-east England on the coast.

You mean TDC, not SSS.

No, on page 1-254 of NATOPS AV-8 TACTICAL MANUAL, NWP 3-22.5-AV8B, VOLUME 1, A1-AV8BB-TAC-000, CHANGE 2, AUGUST 2002, it states that you can enter lat/long in 6 different formats, and UTM as 15 digits (ODU has an indicator to select if UTM is being entered): All entries must begin with N or S for a Latitude, or E or W for a Longitude Coordinate. DD = degrees MM = minutes SS = seconds m, mm, and mmm = tenths, hundreds, and thousandths of minutes repectively s = tenths of a second NDDMM NDDMM.m NDDMM.mm NDDMM.mmm NDDMMSS NDDMMSS.s The length of the entry before and after the decimal point determines which format is being entered, and it is therefore superfluous to require setting and entry format.

It's been quite a while, but IIRC I was using VIACOM2 with the P-51D and could never get it to really work well and much of it had to do with some craziness between VA, DCS and my keyboard and arguments that I had with Hollywood that entering '\' using the Germany keyboard by pressing the '\' (actually <AltGr><ß>) key would not work, but pressing the 'Ä' key on my German keyboard (same key pressed on a US keyboard to get '\') would work, at least visually, but not when running the script, which made no sense to me at all, because why should VA even know I'm using it to edit a script for DCS and to somehow interpret a US keyboard because DCS only knows US keyboards. I couldn't get Hollywood to believe me, and I couldn't get what I was doing to work without his help, so I dropped it. Whatever it was I was trying to do back then --I don't even really recall-- I never got it working, so only half of what I wanted to do with VA worked so I dropped it for a fully to look for a working solution.

You are not following any of the folder requirements of a mod. Lets say you want to mod the default joystick/throttle bind definitions of the P-51D, bc that is a very typical modding done by many. The original file is in 'c:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\P-51D\Input\P-51D\joystick\default.lua' --depending on your DCS version and it's installation location--. Start with a folder named how you want to address the mod. I strongly suggest using highly structured names. For example my P-51 HOTAS mod folder is named 'DCS P-51D Cockpit Controls - HOTAS' Then you need to mirror of the folder structure of the original file starting with the level below the installation/version folder. In this example the installation/version is '..\Eagle Dynamics\DCS World', so 'Mods\aircraft\P-51D\Input\P-51D\joystick'. You should now have 'DCS P-51D Cockpit Controls - HOTAS\Mods\aircraft\P-51D\Input\P-51D\joystick'. Copy the original 'default.lua' into 'DCS P-51D Cockpit Controls - HOTAS\Mods\aircraft\P-51D\Input\P-51D\joystick' and edit it as desired. When complete, open OvGME -> Mods -> Make Mod-Archive... Under Directory-Mod root folder navigate to and select 'DCS P-51D Cockpit Controls - HOTAS', insure your mods archive folder is selected under 'Destination path for Zip file' and click [Make]. That's it.

The warnings and cautions are stacked, each in their own queue. Pressing their respective reset buttons removes the top warning or caution. I'm not sure if they are in the order of the indicator lamps or order of importance or order of recording, but I'm generally just pressing reset until the darn things stops panicking.

Yes, I do... ... :noexpression: wha...? Are you looking for some help? :huh: Just pulling your leg a little ;) What exactly do you need help with?

I don't use Voce Attack, because DCS doesn't play well with non-US keyboards (RACISTS!! :D ). However, "there is another" - O. W. Kenobi Press F10 to get the overview map. There you will always see the mouse pointer. It cannot hide; only be turned off.

That would already be a huge improvement.

I'm with you. That's basically what I'd like. I'm just asking for a but more comfort added to the basket. Basically, I don't need a pointer. I need a carrot (that's when the input focus can be caused to jump from one input field to the next, like filling out an online forum and pressing <Tab> to jump to the next field). I don't need to be able to put the pointer on some random point between switches or somewhere in the cockpit. I mean, I can't scratch my knee with it, and it is of no use unless it's on an input field. No one is in the cockpit with me, looking over my shoulder for whom I need to point things out to. I need to operate switches and dials and things. I need to designate which of those switches and dials and things I'm operating at any given time, and using a mouse is very flexible for designating, but only if you can control what it's pointing to easily.

Is that a question, or an offer? :)

The problem is that DCS uses windows to control mouse movement, and windows is only concerned with the mouse pointer coordinates within the video frame (ie your monitor). Windows doesn't care if there are virtual buttons anywhere on the screen, or the DCS is slewing those buttons across the monitor, controlled by your head movement. So to have a pointer relative to its position within the virtual world cockpit, the pointer must be inside the virtual world cockpit ONLY, and be completely unconcerned with the windows mouse pointer.

I have no idea how the current system allows for very fast anything. What? because turning your head and moving your hand in the same direction causes the pointer to move twice as fast? Twice as fast and twice as uncontrolled so that you then have to stop and start to adjust the pointer position before you get near the switch you need to operate. Moving the pointer with the mouse alone would be far quicker, because far more controlled. It is exponentially (literally) more difficult to use the current system, because you move the pointer with both your hand and your head simultaneously, and pointing with your nose is completely unnatural and leads to neck tension, which is unhealthy. And as you have already attested, you can only fine tune your input by freezing the movement of either your head or your hand, which will always be a possible cause for error and attests to using one or the other is by far superior than both. No one said anything about a virtual hand (a la Thing from the Adam's Family) creeping around your cockpit (although I'm sure there are some who read this and are already thinking - KEWL!! lol). My thoughts are more along the lines of a frame or highlighting around the switch being addressed with a dead zone so that it doesn't easily jump to another switch unintentionally. It would only be moved with the mouse (NOT through head movement). There could be many solutions to it not being in view the entire time. Have it fade out after a few seconds of inuse. Drag it onto the stick or throttle to simulate grasping one of those and then the carrot blinking out. So many simply solutions; all 100 times better than the acrobatic mouse games we have now.

Apparently ED has been revamping a lot of equipment used in multiple modules (eg. Litening Targeting Pod) into API's, so that they can "simply" be "plugged" into nearly any module. Maybe with a little luck, they'll get around to doing this with JTAC's as well. It would probably be the API with the widest usage, as nearly every aircraft capable of CAS would probably need to have it. Time will tell.

I've never heard ED even acknowledge that there is an issue, so unless I've completely missed it, I know of no progress with this in any way.

This might be of interest

If there is anything in DCS which has bugged me from the start 5 years ago and still bugs me just as much, it's having the mouse pointer fly around the cockpit because I've turned my head. The lazy stupidity of this solution gives me violent thoughts every time. Just the other day while flying online I was desperately trying to quickly change some switch settings in my cockpit and fighting with the combination of head and hand movement. I'm not a f*cking world class acrobat nor one of the Avengers. I'm just some 60 year old smuck trying to enjoy himself and asking himself why doesn't ED simply fix this situation. WHY ED?! Any solution is better than none!

I'm not sure, but I think the mission is written that if you kill the HQ units, you "win" - at least that's what the description and everything sounds like -- I've never actually gotten that far. At any rate, I didn't want to run the mission that way, because it's too binary, too black and white. The enemy knows we're there and will send their general staff into air raid shelters, and certainly not sit around like fish in a barrel waiting to get blown into a fine, pink mist. I wanted to do as much damage to all the units around the HQ as well, to disrupt their preparedness. After all, that was the mission goal, to delay their jump-off, and if the general staff survives, but the entire force is in a shambles, they're not going to do anything either. I also went with rearranging loadouts - heavily, plus I also decided to primarily fly the SEAD/SEAM mission, because [MAJOR SPOILERS STARTING HERE]

I've started and restarted this mission so many times... *sigh* ... but not because of the design itself, but because DCS AI is just exactly not that at all... Without trying to give away anything and spoil the fun for anyone, but if I tell my flight to anchor somewhere and they fly a circuit right over the top of a know SAM sight... shm That's not BD's fault. It's the fault of the stupid DCS AI. 9/10 of the effort I've put into trying to complete this mission as I would like to has been in getting around that. You really have to lead the AI by the hand like a little child that it doesn't do obviously stupid things, and after a while I'm just disheartened completely - again, no fault of baltic_dragon.

That might be true, but first ED has to perfect the ground radar and make the ground radar API available. Then it would probably be fairly easy to shoe the Harrier II Plus in. But before that I think RB wants to get the South Atlantic (Falklands War) project out to the public, so IMHO they'll be putting their efforts into the Sea Harrier before the Plus.

And on the stern is a bumper-sticker that says WE BRAKE FOR NO ONE!! :D