Captain Orso

Every aircraft I own I tested to see if the Nav or Position Lights are forced on during hot start, even though I have "Synchronize Cockpit Controls with HOTAS Controls At Mission Start" selected, and a HOTAS physical toggle switch assigned to each ON and OFF positions, and the switch set to OFF. I am always forced to turn the lights off after spawning into the cockpit. Happens on the carriers and SC as well with Hornet and Harrier, although it is prohibited to use position, anti-collision, and landing lights on the decks of these ships, at all. All these aircraft tested. P-51D, all variants Spitfilre, all variants P-47D, all variants Mosquito UH-1H Huey AH-64D AV-8B-NA A-10C A-10C II F/A-18C F-86

It seams that to get DCS to behave that it doesn't leave you with migraines you need independent 3rd-party tools with secret information, and asking to have the deficiency at least recognized, you get told everything works as it should and that I, as the customer, am at fault, but I can ask the manufacturer if they might update their product to fit to my unreasonable expectations. It seems a twisted world we live in. Many thanks for the Infor, MAXsenna. I believe from the forums to have read, the source for up-to-date info and access to downloads for VIACOM is thru their Discord channel. Is that correct?

I would surely like to know how that is possible, since VoiceAttack is only a voice interpreter with an hierarchical scripting framework which only outputs menu point activations. If through VIACOM you can say, "refuel me chief" for "top her up, chief" it can still only access the comms menu -> crew chief -> refuel & rearm - or do you know something of which I am completely unaware? I would sure love to know what it is.

The DCS App erases the data I spent a relatively large amount of time and effort to input and control for correctness for no reason. That is a bug. Even if I dropped every bomb on target and flew back and got a new set of GBU-38's, the JDAM programming in the internal computers should in no way be erased. The system has an OSB for doing that if the pilot decides it is necessary. It can hardly be any more obviously a bug.

The title pretty much says it all. I'm on MP server. Enter F/A-18C hot. Rearm & Refuel, adding 8*GBU-38 and a centerline fuel tank. Start GBU alignment and go into the kitchen and come back. Timer is gone. Program all 4 stations with different targets for each bomb, using PP1 and PP2. Double check every Station and PP1 & 2 to be sure everything is programmed. Because I've been sitting on the ground for god knows how long, with the engines running, while I program everything, I call the ground crew to refuel--of course I cannot tell them to only refuel, because I am retarded like a snakeye. I'm watching like a hawk, the DDI display with the SMS page -> JDAM View -> MSN (left where as it was after STEPping thru every station to check each one). Right when the crew chief says rearming complete, STA8 and PP1 disappear and along with it the programming displayed below has also disappeared. Stepping thru every station and looking at PP1 & 2 for each shows that ALL PROGRAMMING HAS BEEN ERASED!!!! Curse words uttered omitted for brevity.

The maps are just getting better and better Imagine getting the Caucasus map in this quality...

I'm not going to hold my breath until the Huey get's a nice DCS-MLU... *sigh* But DCS does seem to be working strongly toward the Cold War period, and what aircraft represents the period better than the Huey... or maybe the Phantom II... or Tomcat... Mig-21..... but with regards to helicopters, it's the good ol' UH-1 Huey! Please, pretty please, let's have the Huey massaged and oiled and made to fit in with the airframes DCS and Friends are putting out today, so that no one would guess that it's been around for so many years already. I'll even gladly play for the upgrade, like when I purchased the A-10C II instead of paying the full $79.99, because I already owned the A-10C basic, I only paid $9.99(!!). I would pay more for an Huey upgrade! You hear that ED? Free money for the taking!

Many thanks for the reply, Sedenion. At least according to my phone's OS the Google Authenticator has no permissions to look at my phone number, SIM card, or IMEI. Of course, that is assuming the Android OS itself is not spyware. But then simply owning any mobile phone opens one to being spied on, even if you use a 'burner' phone, you leave a trail. Just one not so easily followed to you as a person. With the number of forums and even large corporations being hacked and having personal data stolen - especially email address and passwords from forums, I view TFA as added security, but I also use a password generator and encrypted password database. Since ten years the world knows without a doubt how much data the US's security agencies collects on all of us, even though it is highly illegal in the US itself, and yet there was no huge wave of protesting the government or telecommunications providers who cooperated with the government. The US public in general is in that sense and albatross around or necks. What each person does with that information is and individual decision with no perfect solutions available. Thanks again for your reply, Sednion.

Hi Sedenion, thanks for the update to OMM Could you point me to information about TFA and digital-identification? I'm never heard of any concerns with TFA and use it with many accounts. Thanks in advance.

Yes, but it behaves exactly as before. If you press too long, if flips off again. It acts like: short press = [Boxed], and long press = Unboxed . All other VAR's are simply press/click any length of time = toggle state: Boxed<->Unboxed.

I want to add a Waypoint TSD -> Point(B5 -> Add(L2) -> WP(L3) -> IDENT>(L1) If you hold L1 for longer than about 1 second the Box at IDENT flips off again and on the KU IDENT is removed and you cannot enter the Waypoint identifier. This happens whether you are left-clicking with a mouse or have a key assigned to press L1 and are pressing the key. Happens on both the left and right MPD.

So true, sorry.

You will have to be much more specific, exactly what doesn't work, and how to repeat it.

Follow the link in my previous post and read.

Draken35 is the author of the plug-ins, and IIRC was also the one who pushed for Scratchpad to be plug-in compatible at all. Here's the link to the post with his latest content:

No, that is not correct. Without plug-ins to delete old data, mark it with you mouse and press <Del> {delete}. <Esc> causes Scratchpad to rescind the focus so that pressing keys passes them on to DCS and not to writing into the open scratchpad. If you implement the 'QWERTY_KB and Load Coordinates' plug-in you will get a [CLR] button to click, which will clear all content of the current scratchpad page.

I'm just thinking functionality. I'm not worried about the looks of the apps.

I've installed The Way. I found it overly complex and the use of an external program made its usage at all overly complex. Plus it still seems to have ever reoccurring issues simply displaying the F10 targeting dot. Scratchpad is completely within DCS, being a set of scripts--mostly lua--installed into '..\Saved Games\DCS.openbeta\Scripts'. To implement the additional function of a plug-in, you simply copy it from '..\Scripts\Scratchpad\Extensions\Disabled\' into '..\Scripts\Scratchpad\Extensions', and that's it. All the things written into the Scratchpad pages are saved for the next session. You can archive them for use with the same mission at another time, or simply clear them out. It's very useful and easy to use. I just wanted to hear of there was something The Way does, which Scratchpad doesn't. If anyone comes up with something, I'd surely like to hear it.

Many thanks for the reply. Scratchpad has some plug-ins which transfers the collected F10 map points directly into the waypoints of the aircraft you are flying: F-15E, AV-8B, AH-64D, F-16C, F/A-18C, and M2000C. With the Apache you can actually select which type of point is inserted per data point, so WayPoint, Control Measure, Target Point, or Hazard Point by modifying the data line beforehand. It's pretty cool watching the data being entered into the UFC

Without having to read through 26 pages of form to find out, but what does "The Way™" offer that Scratchpad doesn't?

Many servers use CTLD to put JTACs up in the air over targeted airfields. I want to use these while flying the AH-64D to fire laser guided AGM-114K Hellfire missiles in LOAL mode (Lock On After Launch). For this to work, however, the Apache must be facing the lazed target almost exactly--within something like a 4° cone, otherwise the Hellfire won't find the Lazed target. I know I can read the F10 Other -> JTAC Status display to get the target unit type and the coordinates, but that can mean going through a while number of units on the F10 map to find the one with the exact same coordinates, which can be a very daunting task while flying a twitchy helicopter which doesn't have hover control and tends to like to tip over while landing if the ground isn't perfectly flat and horizontal. The most ideal solution would be if I could press a button to get the unit added as a Control Measure and the Cxx number posted that I can select it as and Acquisition Source, or if already in the COORD database, just post the Cxx number so that I can select it as the ACQ. I mean that are probably a hundred ways it could be done better than sitting on the F10 map and comparing MGRS numbers. I mean, just getting the targets MGRS number into something I can copy into the Scratchpad would be a huge improvement. Any help would be appreaciated.

I'm not sure what you are talking about, half the time. I'm not talking about some abstract idea. I'm talking about actual technology. If you opened the ME, selected a map, added units and then saved it under a unique name, it is a mission. I have no idea what a "spurious waypoint" might be. If you open your mission in the ME, select the FA-18 you are flying in it as 'player' or 'client' and there is a continuous yellow and/or white line starting at your aircraft, then you have a minimum of two waypoints--waypoint 0 where your aircraft starts, and a second waypoint connected to WP0; you may of course have more. Maybe it would all be easier if you posted your mission so that someone could look at it. One more thought. Do you have your control definitions modded? That would probably be 'c:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua'. If yes, you should probably post the modded lua file also.

When you say, "the CPL is live also", do you mean that the text CPL appears in the lowest UFC LED display? That only happens if on the HSI page, a WayPoint is selected and WYPT is boxed, which from the description of your mission, sound very odd. Did you write this mission from scratch, or did you take over part from another mission?

What exactly do you mean? Exactly what are you seeing?

The aircraft does have an idea of where it and the target are; it's called INS. The problem is, the methods of keeping track of them are Imperfect, and over time deviation increases, because even the very best gyroscopes, including laser-gyroscopes, have deviations, which increase over time and motion. The largest difference between CCIP and AUTO release has to do with physics - it's in the trajectory. The most ideal delivery method would be to hover directly above the target and release the weapon. Why? Because there would be no influence of forward or lateral momentum (baring wind) on the trajectory. if the bomb is built to have absolute symmetrical aerodynamics, it will fall absolutely straight down. One would have to implement a lateral force to change its trajectory. The greater the parabolic arch in a trajectory, the greater chance in misaim, because the same degree of change in the "sight" causes an ever increasing change in the trajectory at increasing parabolic curves. Without going into lobbing bombs, which basically doubles the parabolic curves, the worst case scenario for aiming a dropped weapon is therefore dropping it from level flight; in other words AUTO release. Anyway, the solution I figured out is to set the target on the ground. When I get turned around and have localized the target location optically, I can then undesignate the target and the mode immediately jumps to CCIP. So best of both worlds.