Captain Orso

Thanks for the reply. I can't believe that having only 2 bombs on the BRU-42 is a detriment to it's structural integrity. If that were the case, any time you drop only one bomb from a rack and continue flying, you would be endangering your aircraft. Knowing the way DCSers think, the notion probably never came up that anyone would ever want to put less than 3 bombs on the BRU-42. That would be... silly. Everyone wants a bomb-truck after all.

The title says it all... what?, you don't get it? Okay okay, jk about not getting it -- What do I have to do be able to use BRU-42's with only 2 (in words two) bombs per BRU-42? The LAU-88 had the selections of 1, 2, or 3 AGM-65D's for example. How do I achieve the same versatility with the BRU-42? Willing to use mods which pass integrity checks on MP servers. There is reasoning behind this request. On MP Dynamic Campaign servers on which you are only allowed a limited number of specific weapons types -- for example, only 4 GBU-12's -- but unlimited from other, mostly unguided weapons, having to spread the GBU's out over 4 stations wastes precious weapons real estate, because the weaponers are too stupid to use 2 BRU-42's with only 2 GBU's per BRU-42.

Can no one offer a solution to this? Am I the only idiot to have this issue? Should I shoot myself now?

Countless times I try to quickly find the • to move an overlay window -- kneeboard, scratchpad, srs overlay, chat window -- and it off in the freaking woods, miles away from where the + pointer is. How do I get them to be glued together or at least that when I move the + to the edge of where it reaches in side the cockpit, that the • then appears and starts to move outside the cockpit? [865 lines removed by Auto-Ban-Prevention™ Keeping you in forums and out of liable suites]

That would require having a collective controller, which very few people have. If ED wants to do that as well, I would certainly have nothing against it - more power to you, brother. But the solution which would advantage everyone would have to take precedence IMHO.

Pressing the IDLE STOP REL button, while the throttle is at the idle stop position, below the idle stop itself, would emulate moving the throttle to the idle position, which you cannot do with but a very few collective controllers, and which is exactly how every other module does it - exactly the same.

If you want it to work 100% the same as on the real Mossie, you need solenoid-switches. Somebody is doing something similar with a ThrustMaster Warthog HOTAS Throttle. Have a look here: Full switch upgrade for Thrustmaster Warthog throttle [OTTO, Cutler-Hammer, Honeywell, Mason]

1) I couldn't even find the gunsight brightness dial. I've got it set to the HOTAS, but if you could tell me how to see it... I am curious. 2) I think DeHavelind designed these controls to be operated blind, which is why the are so big. The pilot can just reach behind his seat and feel how they are set and operate them by feel, easy-peasy. In VR... I have the fuel switches all set to my HOTAS, but I have to use a modifier or two to cover all the settings.

It's not a question of why it was designed like that, although in modern aircraft, in which if you put the gear down while flying +mach it would have catastrophic consequences, and yet there is no guard against the pilot doing something so stupid, other than self-preservation. The issue is that practically NO virtual pilots have HOTASes and button-boxes enough to waste on extra levers, hitches, hooks and frippery. There are many aircraft with security mechanisms which we are not required to operate. You don't have to unlock the canopy on the P-51 to open it. You don't have to press the thumb release for the master fuel valve on the Harrier, to shut the fuel off, another example on the P-51, the water and oil radiator flap controls, you don't have to flip the switch cover open to operate the switches, you just operate the switches, and if the over is closed, it is automatically opened first - I'm sure everyone can think of one or two. The question is of whether to be user-friendly or not.

For all those having issues with Windows saying that it cannot find 'DCS-SR-ExternalAudio.exe', it is because it is not in the directory in 'path' you have provided. I'm guessing that you simply don't understand what a 'path' is and/or that you must edit the 'ctld.lua' file to reflect your installation. The 'path' is the string of characters telling Windows where to find the executable file you wish it to run. I this case the file is 'DCS-SR-ExternalAudio.exe' and the path to the exe file is exactly to where you installed Simple Radio Standalone, because 'DCS-SR-ExternalAudio.exe' is a part of the SRS installation. You ought to know to where you installed SRS, but to be sure, find the SRS desktop icon and right-click on it to open the context menu, and select the bottommost line: 'Properties'. A small window with many tabs at the top will open, and the 'Shortcut' tab should be opened. Toward the middle of the window you will see 'Target:' and a wide rectangle behind it with text inside the rectangle. This is the 'path' and executable for running SRS, eg in my installation it is 'C:\sbin2\DCS-SimpleRadio-Standalone\SR-ClientRadio.exe' without the apostrophes. Let's look closer at this string of characters. Everything to the right of the furthest-right '\' (backslash) is the targeted executable, which when run by Windows provides the Simple Radio Standalone functionality to DCS. Everything to the left of the furthest-right backslash is the 'path'. This is how you tell Windows where to find the executable. It is literally the path to the executable. I'm sure that none of you have SRS installed in the same location as I have, so go to the desktop icon and look in the properties to find the target of that desktop icon and thus the 'path' to where your SRS is installed. Copy the Target' entry (left-click inside the rectangle and press <Ctrl><A> <Ctrl><C> to copy the contents to the Window Clipboard). Open your ctld.lua file with your favorite text editor and look for the line beginning with 'STTS.DIRECTORY = "E:\\Program Files\\DCS-SimpleRadio-Standalone"'. Mark everything between the two quote characters with your mouse and press <Ctrl><V> to replace everything between the quotes with what you have on your clipboard. Now delete everything starting with and including the furthest-right backslash, upto but not including the furthest-right quote character. Now you should have only the path between the quotes. Go back through what you have just copied in and everywhere you find a backslash, add a second backslash right next to it so that all backslashes are paired together with exactly one other backslash, but not more or less that two next to each other. It should look something like this: "C:\\sbin2\\DCS-SimpleRadio-Standalone", but with your path to your installation of SRS in it. Save what you have edited in your text editor, go into DCS - MissionEditor - open your mission, find the load script file trigger and go through the selection of your newley edited ctld.lua file. Run your mission and enjoy.

Yeah, that makes me do the shimmy too .... .... I put an oil platform in my test mission and start a Huey on it "Start from ramp" and it sits like a rock. I also put a Tic..kinda...rogen... cruiser in near shore and stopped and start a Huey on that too, and it sits without shimmying too. What I haven't tried is adding wind. Also, I don't know if I'd mentioned it already, I noticed this on Friday after the Forrestal update. A guy in my group was hosting. I was sitting on the Forrestal in the Huey and I don't thing I had the engine running yet. I was remarking that the Huey was rocking back and forth but otherwise staying put; a little like while starting the engine, but much smaller rocking, and having the engine running didn't change it either. My groupe mate got in to a Huey on the Forrestal too and noted that it was shimmying forwards, fairly quickly. Going into F2 view and switching to his Huey and it could be seen very distinctly, but as I said, it was only with his Huey, and he was hosting. He host through the client btw, so DCS was running locally for him. I have yet to try how things look when I run the mission on my ded. server and join.

I'm not distributing it. I'm hosting it. In order to have it in a mission on my server, it must first be installed on my server. Sheesh

That's because it's a new feature. Go to https://github.com/rkusa/dcs-scratchpad/releases/tag/0.5.0 for the latest version, but be aware, the keyboard is not in it. That is something someone added in themselves and posted here.

Which means I'd have to start DCS to see something which could take all of 2 seconds And if I've already downloaded it at some time and am no longer certain if I've installed the newest version already? I'm not flying the A-4E at the moment, but members of my group do, and since I run the server occasionally, I provide this as a service to them. <Captain Obvious>Useless snide remarks are... useless.</Captain Obvious>

So this happens not on ships too? But on hard ground I don't think I've witnessed it happening. What was the Huey sitting on in Worlds Apart Spring?

Thanks for the offer. It was a script from the autohotkey site they suggested for is you have any issues to test your in- and output. I have no intentions at the moment of going back down that path. I'm trying to keep things simple these days, but many thanks for the offer.

I use D°M.d in the Hornet and MGRS in the Warthog, but that's just me. Others may swear by other formats. That's why I suggested the universal solution. Everybody could get exactly what they want. I even offered a solution for the indecisive, because that's the way I role . I know it's extra work for something you just put in, and I honestly do appreciate it. I'd even send a beer your way if you had a Patreon account -. I already checked in Github

Yes, of course you are right. I was wondering if I hadn't gotten that backwards later, but it was late and I was tired, and...

So Many Questions... lol Okay okay - answers answers --- Management Summery: Was this an isolated occurrence? First time I've ever seen it. Haven't tried to reproduce it yet. Will try very soon. Does it now happen to you all the time? Only once. Does it only happen in a specific situation? (Like trying to use a maverick) IDK will try to find out. What were the aircraft conditions when it happened? Air to ground, Air to Air, No master Mode. Weapons onboard. Single player/Multiplayer MP, don't recall if I was already in A/G mode, but maybe. If it is reproducible, could you make a short track file of it and upload it? Will try to reproduce it and post a track. --- For readers: I was on the Hoggit PGAW server. I had previously flown the Huey, but that probably has no influence on this. I selected a loadout from my presets and switched some bombs for some rockets and let the ground crew do it's thing. Afterwards I realized that my old presets for the F/A-18C still have the Litening II as TGP so I when back into R&R and replaced the Litening with the ATFLIR. Later, while flying I knew there were some baddies down in this one area. I was at over 10k because there might have been an SA-6 among them. I tried to use the HMD to put a target designation on the ground, and I noticed that the normal aim-point for ground targets wasn't right. Usually a dot with a circle of dashes aligned pointing away from the dot. Looking at Chuck's Guide, Section 9 - 5 - JHMCS at the graphics, I may have been in A/A for some of this debacle. I will try to reproduce this and get back with more exact info

Have I broken something? I was using ATFLIR and while trying to us the CCD to look for a target, I could not change the FOV from wide and thus also not change the zoom. FOV change button is OBS6 (top row, first from the left).

I love this addition. So useful It picks formats automatically when I'd rather have another Suggestion, put three little boxes at the bottom [D°M'S"] [D°M.d] [MGRS]. The user gets the formats he indicates, 1, 2 or all three. If the user doesn't pick any, he gets everything automatically

Go into the F10 map and put an area you which to set as a waypoint within your map display and open the Scratchpad. At The bottom of the Scratchpad window, there's a little check-box to the right of the arrow buttons. If you click on the check-box, to the right of the check-box a button labeled [+L/L] (Add Longitude/Latitude) will appear along with a white dot-pointer a bit to the left of the window. The dot-pointer is locked in position relative to the window. Using the mouse to drag the Scratchpad window so that the dot-pointer points to the place of which you wish to the coordinates input into the Scratchpad. Now click on the [+L/L] button and the coordinates will be entered into the window where the cursor is positioned (you may wish to position the cursor before hand). That's it!

Or... the devs could be very friendly and put a version file with the exact information required right were one would look for it. Now that you've mentioned it, I've found the version info in the entry.lua file - kind of buried, but if you don't know that it's there you wouldn't just look in that specific file. That means you would have to start looking through every file you find, hoping to find some simple information, which could be very user friendly presented in the root directory, just like many other software packages.

Well, I don't get it. I remember very specifically using a script with autohotkey that all it did was show the keypresses (simpler is not possible) and pressing keys which have characters very specific to Germany keyboards and getting characters shown as if it were a US keyboard. This was the issue I had in VAC and in Viacom as well. No one could explain this. I have a very standard Windows installation and a very common keyboard (Logitech G11).

It would be helpful if there were a 'version' file in 'Mods\aircraft\A-4E-C\' so that you could quickly check your installed version with the look at a single file.