Captain Orso

Found this: Clear Canopy Glass Works like a charm in the Apache! Unfortunately, only for SP - doesn't pass controls. Haven't checked in other aircraft, but apparently work wonders everywhere.

I haven't even had the chance to pre-order this thing, and already you're smashing it up!! Stop that!!

SIX months after this first being reported... I was flying low over the water in overcast condition with no external nor internal lighting. When I looked out of the canopy at the water it appeared as if I have headlights turned on all around the nose of the Apache. I checked externally with F2 - nope, dark as the night. Then I realized, the "headlights" are caused by the the canopy glass __TL;DR ______________________________________________________________________________________________ If you can't fix it in a timely manor, please turn it OFF so the customers can enjoy the product.

Even if OvGME didn't have the option, I would say it wouldn't be technically difficult to implement, but it would still be work to do it. If I had to choose between a selection in a pull-down menu and getting some other feature, which I can't replicate with a simple Batch, I'd rather have the later - YMMV.

To do "Uninstall All", simply de-implement all your mods, and then save that status as a Batch. Mine is named "None". Before every update, I simply double-click None, and the magic happens The funny thing is, and I'd never thought of it before, no matter how many new mods I add to my mod-set for DCS, my None batch always works on all of them, always - so cool.

Lots of this you should decide and organize yourself. Principally I suggest you keep things OMM manages apart from things you manage. You don't want to mix up things you manipulate with things OMM manipulates. Create 'D:\DCS Info\Mods'. This will be the root of all your modding files. Create 'D:\DCS Info\Mods\OMM'. This will be for all the things OMM manages. Create 'D:\DCS Info\Mods\DCS Mods'. This is where you put your modding files. I organize like this: 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods' -- root for mods pertaining to the Hornet. I always start with 'DCS' and then the module, or 'DCS UI' for mods pertaining to the User Interface, or 'DCSW' for mods pertaining to the DCS world in general, for example, a fix for Persian Gulf airfield beacons. 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Cockpit Mods' -- mods for things in the cockpit, including controller bindings, and instrument panel graphics. 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Wallpapier Mods' -- for modded wallpapiers (background of the main menu). 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Cockpit Mods\DCS FA-18C Cockpit - HOTAS' -- mods for bindings eg if an aircraft only has a button press defined for controlling the undercarriage, but you want to use an On/Off switch, I would put that here [I won't go into details of that here, but if you need help, let me know]. 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Cockpit Mods\DCS FA-18C Cockpit - HOTAS\Mods' -- this is the first folder level of a specific mod. 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Cockpit Mods\DCS FA-18C Cockpit - HOTAS' is equivalent to 'D:\Eagle Dynamics\DCS Worlds OpenBeta' with regards to how files are copied. 'D:\DCS Info\Mods\DCS Mods\DCS FA-18C Mods\DCS FA-18C Cockpit Mods\DCS FA-18C Cockpit - HOTAS\Mods' is therefor equivalent to 'D:\Eagle Dynamics\DCS Worlds OpenBeta\Mods'. If you put a file into 'D:\DCS Info\Mods\DCS Mods\DC000S FA-18C Mods\DCS FA-18C Cockpit Mods\DCS FA-18C Cockpit - HOTAS\Mods', when it is implemented by OMM, the file will be copied to 'D:\Eagle Dynamics\DCS Worlds OpenBeta\Mods', which is how mods are implemented. When you create your the context for DCS OpenBeta, you give it recognizable name, like 'DCS Mods'. This will create 'D:\DCS Info\Mods\OMM\DCS Mods'. This will be the home folder for OMM to use for DCS OpenBeta mods. This is where OMM puts all the config files for the DCS Mods context. When you create the context for DCS World OpenBeta, this will be the home folder. Target folder: Target Destination will be 'D:\Eagle Dynamics\DCS Worlds OpenBeta' Library Folder is where the mod packages go. I keep these separate from OMM, bc I package my mods myself, mostly out of habit. For you, I suggest using: 'D:\DCS Info\Mods\DCS Mods\Z DCS Mods OMM Library' -- This is where to put all mod packages. The prefix 'Z ' it to insure the folder is last in the folders list, which makes it easier to find. EG: 'DCS FA-18C Cockpit - HOTAS\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua' -- My keybinds mod for the Hornet This gets zipped with the folder tree to 'DCS FA-18C Cockpit - HOTAS.zip' and copied to 'D:\DCS Info\Mods\DCS Mods\Z DCS Mods OMM Library folder'. Target Backup folder is managed by OMM so it goes to 'D:\DCS Info\Mods\OMM\DCS Mods\Backup'. I don't recall if I had to create this folder first or if OMM did it, but either way, this is where the backups of files you mod are copied. EG: When I implement my Hornet binds, first 'D:\Eagle Dynamics\DCS Worlds OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua' is copied to 'D:\DCS Info\Mods\OMM\DCS Mods\Backup'. Then 'DCS FA-18C Cockpit - HOTAS.zip' is unpacked into 'D:\Eagle Dynamics\DCS Worlds OpenBeta', but starting only with the Mods\ folder. That seems like a lot, but organizing sensibly and sticking to a good organization will make you life a lot easier. !! Attention !! before every DCS update, always de-implement all your mods! I have a batch defined just for this purpose with zero mods implemented. If anything isn't clear, or you have any questions at all, please feel free to ask.

I would kindly guide you to have a look at In-Game Scratchpad Mod Available - Works Great In VR! It works exactly the same in VR as without. In short, you can center the F10 map over a center-dot the app provided and then mouse-click the button to transfer the location coordinates at the dot to an own file in all formats the aircraft you are flying might use. The contents of the file is always available to be read, like having an extra kneeboard. In fact, you can have at least 10 pages like list and they persist from session to session, as the files reside in their own folder under your Saved Games\DCS folder. Of course in doesn't translate any inputs to the cockpit button, or whatever method you are using, but maybe this project can give you an idea to solve your issues.

Yeah, but you never land with brakes on. The stress tires endure simply by touching down at over 100 knts , while the wheels are not rotating, is enormous. At one time they tried making the wheels turn at least closer to landing speed for touchdown (I think it was just for airliners, but larger aircraft anyway), but the weight and cost of motorizing all the wheels was considered to high compared to developing tires that can take the strain, and replacing them often.

It depends on the ABS system. A good ABS will always stop quicker than non-ABS. If you are old enough and grew up in a climate which regularly has snow and ice in winter, you learned to pump you brakes when it's slippery. If you lock your brakes, not only can you no longer steer, if your tires are only skidding on--be it snow, ice, wet pavement, mud, leaves, whatever-- on, they have less stopping power, than if you are pumping them, ie press-release-press-release-press-release. So if ABS only does press-release, but automatically, how can it stop quicker? Because it uses sensors to tell when the wheels are about to lock up, and lessens the brakes power, before asserting them again. It does this many times per second. Not only would it be the rare human who might be able to pump the brakes that quickly, humans do not have sensors telling him/her that the wheels are about to lock-up, to know to let up on them. I'm going to go out on a limb here and conjecture the Navy doesn't buy crappy ABS for the Hornet.

As basis for this experience I flew the P-51D Landing Training mission. Much of this report is from memory, because it's been a very long time since I've flown gates. The "next" gate used to remain large much longer. You used to practically be able to see it shrink while flying into it, almost. Now at about 200 meters distance, it's already small. The "next" gate used to be more highlighted. It was very easy to tell which it was. Now there is very little difference. Upon passing through a gate, if you turned your head, you could see its color snap to grayish. Flown gates used to be grayish, un-flown gates lime green, and the next, enlarged gate was bright green, almost green/yellow. Now from a distance it is difficult to tell the difference in color between the "next" gate and other un-flown gates. In MT the "next" gate does not enlarge at all, but I've reported that in the MT section - just mentioning it here. Documentation in the manual is abysmal - no explanation at all for what the flag number is used for, restrictions and requirements, nor the flag value (all only known through reading other missions) - sad.

Yes, I've seen that entry, but thank you for posting it. It lacks any reference to specifics. Anyone can interpret anything they wish into it. What was changed? From what, to what? Additionally, since it was apparently wrong before--proof positive that ED makes mistakes, just like everyone else--, it is completely erroneous to assume it is now correct, without evidence.

Why? Now I am intrigued. How so? If there is no mission--ie a PP defining which targets belong together*, and you pick and choose as you wish, there is no constraint preventing the pilot from picking one target in Anapa and one in Sinaki and then expecting a IZLAR to be produced from that. How do you know what target is programmed where, when you basically only know Station [2, 3, 7, 8] and , [A, B, C, D, E, F]? You will need a cheet-sheet at all times to pick your targets. Sounds like extra work and a great source for errors. *Of course, if the PP is the mission, while entering the PP you must insure the entered targets are also grouped together, lest they also be illogical and impossible. At some point, someone must take the responsibility and insure the targets are valid and grouped viably together for JDAM usage. The difference with what my interpretation is, is that once done correctly, there can never be an error, because the grouping is programmed into the PP. Just select a PP and do your work. What??? No matter what, you can program targets completely illogically, all over the place. QTY nor anything else will prevent you from doing that. I am not proposing that QTY share any targets across stations!! QTY is only a filter. It restricts to which stations you can program targets, and from which stations you can drop bombs. Only those stations are viable for either action when selected in QTY*. *The only exception is that when nothing is selected in QTY, everything is allowed. Why? Who knows. They could have masked JDAM DISPLAY unless at least 1 station is selected, but they didn't.

I have pointed to the statement of an official spokesperson of ED stating that the PP is a mission. That has been countered by claims that that was changed by ED, and I asked for documentation to that, and NOBODY has provided it. It sounds to me like people simply discovered they way it currently works by trail and error until they figured it out, and now CLAIM that it was an official change, but can give NO EVICENCE of that. IF it is a case of a lack of documentation, there is even LESS reason to not making the system work logically, reasonably, and usefully. There have been numerous occasion in which a system was changed, because ED either discovered themselves that they had been doing it wrong for months or years, or were shown that what they were doing it was wrong. Saying that if ED does it a certain way, it is PROOF that is how it works, and ED is infallible is simply ridiculous and a point EVERY one should know is not true. I do not expect ED to be perfect. While in my apprenticeship my boss had a saying, "if you work, you make mistakes, if you don't work, you can't even manage that". If you want to see evidence that ED works, look at the list of fixes in the patch notes. ED is working hard, and I'm thankful for it. I hope neither you, nor anyone else thinks I should ignore what I see as being an error, or at the minimum, room for improvement, in order to get on the band-wagon that ED is infallible, when everyone knows--including ED themselves--that that is not even possible.

Also what was said in every case before it was changed.

You mean, to a feature introduce 4 years ago, because that was the event spurring Wags to make his videos. Changes to HMD alignment was documented, also by Wags, right? The rescinding the status of 'planet' from Pluto, was well founded in scientific reasoning, and highly publicized throughout the world. I am following the statements of an official spokesperson for ED. You do not get to simply wave your hand and claim his statements are null and void because you think they are too old. If you have documentation showing a change in the way JDAMs are programmed after mid-2019, please present it. I would be very glad to see something official of which I am not aware. I have provided official statements on JDAM programming. If YOU have anything which contradicts that, please present it.

QTY works as a filter. Set QTY to Sta8 & Sta2 and you cannot program Sta3 or 7. The idea that anyone in their right mind is going to program 4 stations with each 6 different targets, and then somewhere in the air, start picking and choosing which up to four targets from 24 he's going to hit on a given bomb run, boarders on insanity, or at the very least, a total break with reality. The idea is I find childish. The proximity of targets to one another will naturally allow them to be grouped into a single mission ie PP. I conjecture this will be the case nearly always. Being able to select this PP, and by that I mean select each target to be attack on a single pass, is only logical. That there may be exceptions to this rule on the rarest of occasion I can accept. The idea that because of these scarce occurrences every target must always be selected individually is a highly radical idea, unless you would like to suggest, the engineers at McDonnell Douglas are highly incompetent. ED has countlessly made changes to paradigms during the development of aircraft. This would be just one more, nothing radical nor unusual.

Hi Bignewy, Please speak with Mat Wagner, because he is teaching that PP are missions, and what he says makes a world of sense, although NO ONE--not Mat, not Chuck's guides, no one--takes multiple weapons per pylon into account. The jumping from PP2 to PP1 while programming and stepping thru the second set of JDAMs can only be a bug. There is no logical reason to without warning jump to a station and PP1 which are already programmed. After over 35 years in IT--several of which were as a programmer--I recognize halve-baked, un-thought-thru coding when I see it. There's a saying in IT, computers don't make mistakes, and to 99.9995%, with regard to the hardware, that is correct. But damn, you should have a look at the programmers.

Thanks for replying, Phantomo711. I am aware of how it "works". I am saying that the way it "works" is bugged, not only in STEPping from station to station in some cases, but in how the PPx work, and I have declared my sources of information and the logic behind my conclusions. If you do not believe the PP is a mission, please take it up with Mat Wagner, because that is what he teaches, and I have yet to see anything declaring a change to that, other than statements within this thread.

On the kneeboard page with JDAM data for station 8, both LAT & LON are wrong. They differ from the tutorial texts. On the F10 map the Marks can be found and the LAT / LON for both targets correspond to the tutorial texts. Kneeboard for JDAM Station 8 should be N 43 40 35.13 E 39 36 54.20 ELEV FEET 351 HDG UNDF ANG 45 VEL 700 (default) Also, the narration, while saying the LON says "four five" instead of "five four" Station 2 on the JDAM kneeboard is correct. ---- JSOW STP2 entry. The text giving for the STP2 LAT entry is wrong. The text giving is actually the LAT of the target, not the STP2. The Kneeboard is correct, as confirmed by the flag found on the F10 map at the kneeboard coordinates. The tutorial does not mention that the STP MUST be entered for each stations.

Please show where this is documented. I have shown where official publication presents that the PP is a mission and includes the stations programmed into the PP. I will need an equally official publication demonstrating a change to the logic presented by ED in Wag's video. QTY is only a filter. It determines which stations can be selected while programming a mission. If boxing a PPx does not select ALL stations programmed into that PP, it has absolutely no meaning. You are otherwise forced to select every single station you wish to use for an attack, and the selected PP has no meaning. This is demonstrated in the track file I provided. NO! PP are meaningless unless they select the programmed stations.

I've been watching Wag's Youtube videos on the F/A-18 and JDAMs, specifically Hornet Update: Introduction to JDAM, LTWS and More from 24 March 2019, and DCS: F/A-18C Hornet - Multi-Target Mission Attacks (JDAM / JSOW) from 15 June 2019. In both he refers to PPx as missions. He used both synonymously. Ergo, if PP1 is a mission, selecting PP1 MUST select all stations programmed to it, without any other garbage in-between. This would also explain exactly what additional PPx are; they are slots for assigning additional missions designated PP1 thru PP6. Therefore, as stated in my first post, while programming PP2, when pressing STEP and the box jumps from PP2 to PP1, it's a BUG. When two or more missions are programmed, selecting the mission slot (PP1 thru PP6) MUST select all stations programmed into that mission without any other steps. This is not the behavior I have documented and is therefore also a BUG.

Many thanks for your detailed analysis, Tholozor. I needed to find the time to follow your points, but yes I believe you have picked out all the facts. What I am really questioning, is whether this is working correctly. If I could get my hands on the NATOPS I'd look up the procedures myself, but I cannot find a copy online. I think I've covered all the points, which make me skeptical as to how Pre-Planning works in Reality™, or at least why I'm skeptical to it working the way it works in DCS.

Thanks for the reply razo+r. And this makes the PPx buttons absolutely useless and an over complication of everything. Firstly, it's not a plan AT ALL. It is just the designation of which of the two positions on the pylon is selected. Secondly, what are PP3, PP4, and PP5 for? the GBU-38 can only be 1 or 2 to a pylon, so any button above PP2 is useless. What are they for? Thirdly, how do I easily drop just two bombs? I have three target areas. In the first I want to hit two targets. In the second area I want to hit 4 targets, and in the third area I again want to hit just two targets. I've programmed all the bombs--I better keep my target sheet handy, because now I will need it to keep track of which bomb is programmed for which target, because, you know the pre-plan is not a plan, just a pylon position. So pylon position 1 on Sta8 & 2 are for target area 1, targets #1 & #2. Return to the J82 main page -> QTY -> box Sta2 & Sta8, unbox the rest ->JDAM DISP -> MSN -> STEP to Sta8 -> PP1 -> STEP to Sta2 -> PP1. Now I'm ready to drop Warheads-On-Foreheads™, and it only took me 30 to 45 seconds with my nose glued to the UFS and DDI the entire time, when if the targeting system weren't programmed with someone with learning disabilities, I could have simply pressed PP1. For target area 2 the same thing - back out, QTY selection, back in go to all station, select the correct position (better cross reference with my list to be sure the right positions on the pylons are selected, because with all this jumping about and selecting this station, and that position for this target, over and over again, it's bound to wear you down mentally,) is there anyone with their head outside the cockpit insuring we aren't about do die from some enemy who could sail in without a worry, if he knew I was too busy to look up. I cannot help thinking, someone read the manual wrong. And I'd still like to know what PP3, PP4, and PP5 are for!

So I have to select each station individually and select the PPx on each, instead of simply selecting the PPx?

Thanks for replying, Tholozor. I should hope so. But that doesn't explain why, when I select PP1 it is dropping on PP2.