Captain Orso

Thanks for the Library list-view... scroll..... position..... thingy..... works great!! and it's not even Christmas And thanks in general for all your work

Is it? Haven't I seen screenshots of people reaching ultra-high altitudes in Mig-29s, up to about 80k feet+, in which you can clearly see the roundness of the earth? Anyway, even if that were something DCS does only at extremely high altitudes and closer to the ground the geometry of the earth is a flat plain, you can still have the weather at least appear to touch the horizon at what would be the geographical the horizon, so that there are no ugly, silly looking, bright-sky stripes on the horizon at all times, even when the weather is set to overcast 8 with rain.

Over a year and no change. Running through startup at night, until the APU is off the flashlight is not dimmable. Doing startup and trying to maintain at least a little night vision is very difficult when the flashlight only works at full brightness until the half the startup is finished.

I know all is still WIP, and a lovely work it is, but I'd just like to request that the end product actually has the weather setup in a mission extend all the way to below the horizon. If it's very overcast and the horizon in all directions is a bright stripe of sky it just looks silly.

Oil cooler flaps switch is locked in the open position. IDK, but isn't it normally an (On)-Off-(On) switch, the positions in parenthesis are temporary ei when you release the switch they fall back to the middle automatically. The first we can see of the temp gages oil pressure is green and temp too. Then temp drops to a bit below green before starting to move quickly to gage-max. When the needle hits gage-max the oil pressure starts to drop rapidly and is at zero within about 10 seconds as if the oil pump had failed. I have no idea what is simulated and I'm certainly no engine mechanic/engineer. If the oil pressure had dropped off first, I'd have said "of course, oil pump dead, engine soon to die", but the other way around...? I'd also expect if an oil line (like the return from the cooler) sudden became clogged that pressure would go way up, but see the caveat about all I don't know.

LOL true. Actual pilots used a trick, I was told. Switch every 10 minutes. Times starting with odd 10-minute digits (eg 11:10 am, 11:20 am, 11:30 pm, 4:40 pm - actually 1110, 1120, 2330, and 1640 in mil-time) use the left tank. Times with even 10-minute digits use the right tank. Even if you forget to switch, just look at your clock and you know which tank you should be using. Same goes for drop tanks of course.

Controls with desync if you make any adjustments to any controls while in-mission. It has been this way for as long as I fly DCS. EG: You are flying straight and level. <Esc> and go into control settings, change anything, even if you immediately change it back, save. Now try to lower your gear through flipping the switch on your HOTAS configured for gear-up/gear-down to the gear-down position. Nothing happens. Flip back to the up position, and nothing happens, which is expected, because the gear are already up. Flip the switch to the gear-down position again and the gear go down. After that it works normally. Works the same with every switch on the HOTAS.

IMHO trim is not annoying. What is annoying is if I have to let go of the stick for a second and the aircraft goes *VVVVEEEEERRRRRRRROOOOOWWWWW" and suddenly I'm 30° nose up and flipping over - THAT's annoying. Trimming is easy. On take off I always use the 5-6° right rudder, because it simply makes controlling the aircraft on takeoff easier IMHO. Once you're up, gears up, and you've reached above a couple hundred feet agl and over about 175 kts start to ease off the rudder trim while adjusting your rudder pedals appropriately and observing your slip indicator (the "ball"). At first you can use some heavier handed adjustments, easing off the closer to stable you get. Then just taps on the trim hat (I'm of course assuming you are using a trim hat on a HOTAS, but translate to whatever HW setup you use). Then do the same with pitch trim until with hands off the stick your climb indicator remains centered and stable, and that's it. You are stable for that altitude, speed, and direction of flight. After that simply maintain with tiny adjustments and enjoy an relaxing flight. Do this regularly and it will become second nature and you basically don't think about it anymore; you just do it automatically.

I have a Thrustmaster Warthog HOTAS. I can mod the '..\Input\Joystick\default.lua' to be able to assign the undercarriage up and down to an On-Off switch, because there are separate iCommandPlaneGear commands for up and down. However it appears that separate iCommands are missing for the Launchbar, arresting Hook, MasterArm, really, almost everything. Is there anyway to get around this issue to be able to use On-Off switches?

Not to worry. I had absolutely no idea what the issue was at all. I only came up with the idea to try to discover the issue again after having gotten my hands on a cockpit customization for the A-10C II that is fairly simple, so I thought I'd use that as the basis for getting my default.lua in order and the folder names and structure. But until I tried it on the TF-51D and saw that it works on that, I thought I still had a problem with my default.lua file. I still have no idea why the kneeboard and mirror entries are required, because I'm not doing anything with those anyway, but without them it doesn't work so that's just the way it is. LUA is still a mystery to me and DCS a foggy mystery. Thanks for your offer. I've already posted the issue in the P-51D Bugs subforum I guess it's kind of a bad time to have posted a new bug, what with 2.7 having just come out and the bugs it's brought with it. Already there are a number of them just in the P-51D alone that weren't an issue at all before. I'm just glad to have found out where the issue lies and that it's not because of my default.lua file, because it's already been bugging me for years.

Management Summery The '..\Saved Games\DCS.openbeta\Config\options.lua' file is not being parsed correctly for P-51D-25NA and P-51D-30NA Customized Cockpit selections. EG: '..\Saved Games\DCS.openbeta\Config\options.lua': ["P-51D"] = { ["CPLocalList_P51D25NA"] = "Photo - From Factory To Front Line", ["CPLocalList_P51D30NA"] = "default", ["assistance"] = 0, ["autoRudder"] = false, }, However DCS parses for 'CPLocalList', but not 'CPLocalList_P51D25NA' and 'CPLocalList_P51D30NA'. EG: '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\default\mustang_photo.dds' - file attached. '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\default\description.lua' - file below description.lua: livery = { {"pilot_p51_kneeboard",0,"mfd3",true}; {"p51d-mirror", 0 ,"mirrors",true};--mirrors texture replacement with runtime rendered one {"p51d-cpt_photo", 0, "mustang_photo", false}; } name = "default" Without even selecting the customized cockpit, these settings results in the dashboard photo being displayed However: ..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\Photo - From Factory To Front Line\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\Photo - From Factory To Front Line\description.lua' description.lua: livery = { {"pilot_p51_kneeboard",0,"mfd3",true}; {"p51d-mirror", 0 ,"mirrors",true};--mirrors texture replacement with runtime rendered one {"p51d-cpt_photo", 0, "mustang_photo", false}; } name = "Photo - From Factory To Front Line" .. does not display the photo. Modifying the above for the TF-51D works as expected, without issue. The DDS file is attached for anyone to play around with. mustang_photo.dds

Hi prccowboy, thanks for explaining that. I posted here, because Customized Cockpits belong to liveries. In fact the default.lua file literally says "livery = {", sooo... . Besides it's the only subforum that really talks about actual customized cockpits. I think your explanation should help greatly to report this big. Many thanks again for your help

Many thanks for your answer, prccowboy. I think I understand what you are saying, but I haven't the slightest idea of the CPLocalList, how it works, is generated, or what I can do with it, but I guess from what you have said, it is sufficient for posting it as a bug. I'm not sure how I might add the photo to a plane livery, but I have about 80 custom P-51D liveries, so I think I'll leave that idea alone. Having to copy or rename the folder in Liveries\ to change the photo is a PITA, but I guess I'll live with it for a while longer; especially because I kind of don't thing ED fixing this will have much of any priority at all. Many thanks again anyway.

In the P-51D forum someone at sometime posted that there is a dashboard photo graphic that can modded by replacing the DDS file. This however does not pass the IC control. Then someone presented that the photo mod can be put into the Liveries folder as a Custom Cockpit, which passes IC. EG: '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\default\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\default\description.lua' description.lua: livery = { {"pilot_p51_kneeboard",0,"mfd3",true}; {"p51d-mirror", 0 ,"mirrors",true};--mirrors texture replacement with runtime rendered one {"p51d-cpt_photo", 0, "mustang_photo", false}; } name = "default" The same for Cockpit_P-51D-30-NA and this works as a static change. I want to have a selection of photos that I can change through for example Options -> Special -> P-51D -> Customized Cockpit (25-NA). So, before I continue, because I have tried everything I can think of without success, I tried the same things with the TF-51D, and low and behold, it works perfectly. EG: '..\Saved Games\DCS.openbeta\Liveries\Cockpit_TF-51D\Photo - From Factory To Front Line\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_TF-51D\Photo - From Factory To Front Line\description.lua' description.lua: livery = { {"pilot_p51_kneeboard",0,"mfd3",true}; {"tf51d-mirror", 0 ,"mirrors",true};--mirrors texture replacement with runtime rendered one {"tf51d-cpt_photo", 0, "mustang_photo", false}; } name = "Photo - From Factory To Front Line" AND '..\Saved Games\DCS.openbeta\Liveries\Cockpit_TF-51D\Photo - Mustang Sally\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_TF-51D\Photo - Mustang Sally\description.lua' description.lua: livery = { {"pilot_p51_kneeboard",0,"mfd3",true}; {"tf51d-mirror", 0 ,"mirrors",true};--mirrors texture replacement with runtime rendered one {"tf51d-cpt_photo", 0, "mustang_photo", false}; } name = "Photo - Mustang Sally" AND THIS WORKS for the TF-51D!! BUT... Doing the same thing with the P-51D's by replacing the 'default' folder in the above example (the folder name only has the effect of determining the sort order) with 'Photo - From Factory To Front Line' and 'Photo - Mustang Sally' doesn't work. EG: '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\Photo - From Factory To Front Line\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-25-NA\Photo - From Factory To Front Line\description.lua' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-30-NA\Photo - Mustang Sally\mustang_photo.dds' '..\Saved Games\DCS.openbeta\Liveries\Cockpit_P-51D-30-NA\Photo - Mustang Sally\description.lua' In Options -> Special -> P-51D -> Customized Cockpit (25-NA) and Options -> Special -> P-51D -> Customized Cockpit (30-NA) the entries are listed and selectable, but the photos never appear. The only way i can get a photo to appear is by using 'Liveries\Cockpit_P-51D-25-NA\default' as the folder name, and it can be present to activate the photo or deleted to have the default blank dashboard, but the normal DCS mechanisms -- as demonstrated with the TF-51D -- are not working. Does anyone have an idea of why this isn't working, or what to do to make it work?

Is there a secret/hidden/unknown/special key assignment to put the cam in the newly populated bridge? <LCtrl><F9> puts the cam on the LSO <RAlt><F9> puts the cam on Cat1 and further presses cycles thru the other Cats and back to Cat1 etc. When cam on a Cat, <RCtrl><RAlt><F9> cycles cam from one launch team member to the next for the selected Cat. Cam on bridge?

I have a Thrustmaster Warthog Throttle and Stick, and I've had flaps assigned to the slider/dial on the far right of the throttle-box. It has always worked perfectly, except that instead of it using the 5% steps, it was exactly analog to the setting of the slider; eg if I move the slider just a few degrees, the flaps only moved a few degrees, once up to 5% and the lever would move into the correct position and so on in 5% steps. Now the hand-lever doesn't move at all. If I now move the hand-lever per mouse-click, it moves the lever in 5% steps, but the flaps themselves don't move until the hand lever "catches up" with the analog slider position. But even then, it doesn't seem to change the flaps setting synchronized with the lever perfectly (visual confirmation looking outside the cockpit), Previously the Ram-Air sliding lever and the Carb. Heat sliding lever, actually slid when you activated them with an assigned switch. Now they jump from front to back and back to front, which looks really crappy. Pretty please, to fix these

If you use the default profile, the KB is positioned as for all DCS users. Now, if you open the KB and the point and <Left-Click-Hold> on the upper left hand corner of the KB window, you can drag it to wherever you wish. However, if you start to drag it to the right, you will notice that the right hand side of the KB window starts to disappear; the further you move to the right, the more disappears. Drag it back to its original position to view the entire KB window again. That is the limitation of the KB in DCS. The same thing happens to the left, top and bottom. DCS seems to have a pseudo-window defined, within which overlays may be viewed -- the KB is an overlay, just like the chat window, the SRS window, and various other mods with display windows. I have yet to see anyone modify the size and/or position of the pseudo-window.

I don't have a list of differences, but I do have this A-10C_2 HOTAS Charts by Capt Orso.pdf,A-10C_2 HOTAS Charts Night by Capt Orso.pdf. Concept is from spectator257, not sure what his actual name (search doesn't find him) is or who he is, but I used his download as a basis: https://www.digitalcombatsimulator.com/en/files/3312541/ So you might want to look at that as well. The only thing I really know that changed is the Coolie Hat down, long does not swap the DDI's from left to right and right to left, since the HMCS was added, because Coolie Hat down, short now makes HMCS SOI. I'm not aware that anything else changed, but I'm no expert, sooo....

I can hear the gunner going, "BLYAT!!"

Came here for this. Especially with new maps like Syria there are spawn points which are not on perfectly level ground. In general I'm okay with this. In fact I love that the ground is not simply flat as a pancake. But because of this ALL aircraft need wheel chocks!!!!!! like in the Real-World™. Common guys, it's only freakin' wheel chocks. They're blocks of wood. They can't be that difficult to simulate.

News reel: Chinese anti-tank missile test Chinese anti-tank missile - boing.mp4 DCS virtual pilots: "Thanks ED!! You guys can't make anything right!! "

Maybe it's a personal thing, but I don't notice any great effect of having 3* AGM-65D on one wing and none on the other. Having the TGP on one side and the Mavs on the other will balance things out too; but honestly, I stopped paying any attention to it. I've got other things to occupy my mind than this. I think if it made such a great difference in the flight stability of the A-10, Fairchild and Raytheon would not have developed Quick Drawing, because rifling off 3 Mavs, one right after the other, but then crashing into the ground because you can't control your airframe anymore, kind of makes the system useless.

I was wondering about this too. My first attack aircraft was the Harrier, and having an asymmetrical load in the Harrier is not good at all. So when loading up the Hawg with 6* AGM-65D's on two LAU-88's, when I noticed that the Mavs were rifling off the same LAU, I was kind of worried. I've learned since then that on the A-10 an asymmetrical load doesn't make that much difference. So much so, that Fairchild set up the Mavericks to use first one LAU-88 before moving to the other, and that the next selected Maverick will automatically look exactly where the previous Maverick was aiming. This they called "Quick Drawing", so as soon as the first Maverick is away, you can slew the next one onto the next target and launch it, and then move on to the third Maverick. So don't worry about the asymmetrical load and let the Hawg do its thing and let the Mavericks rip in Quick Draw fashion.

Thank you!

Does Liberation really have a Discord server? The links I've found don't work, and I can find it searching in Discord Where do you actually want to have questions and reports posted? Some posts say, 'in Discord', but you seem to want to keep Discord a secret - see above. Very frustrating, these things, which should be simple and straightforward.