BiBa

No wonder it was not findable! Thanks for the good tip - IOU1 :thumbup:

I was modifying some mission like "Rebel Base.miz" but lost the path to some *.ogg sound-file. The weird thing is when for eg the sound "01-bbq_b.ogg" is set in search, it's like as if it doesn't exist on my computer. I even browsed in all DCS sound files and Mod/Aircraft/etc, but couldn't find a trace! Does anybody knows where to find the path to the UH-1H missions sound file, and specifically to the "Rebel Base.miz"?

After having a look on PeterP's thread: ED Forums » English » Sim Topics » Mods and Apps » DCS Mods » Reworked Cockpit Views with proper Neck and having read this: It's also not possible to 'only' smaller the HUD - it has a fixed size bound to a certain FOV it is covering and the HUD is carefully calibrated to the whole cockpit-frame/fuselage. And there is only a small narrow band in which the HUD projection can be fully seen. Changing a parameter of it will de-calibrate it and make your aiming reticles useless and way-points will not be placed where they are. You will have to move your head towards the HUD to 'smaller' it. It took me a few minutes reading in this Link to be aware of how naive I was to think the Hud could be also easily adjusted, especially with the good knowledge I have on Perspective. I thought it was enough to center the AI nose line and forgot how many things in an AI are also dependable of the Head position and distance to the Hud; I didn't think further than my nose! Any FOV with objects further than one mile will keep consistently all its properties' measurements and symbologies uniformly to the eye of the beholder, let alone any type of head movement in a 100cm radius. Thus the movement of the Head in any direction has no volume impact on them, however only on the Hud framed content that is not further than an arm length. This Hud is like a 2cm hole on a DIN A3 paper sheet holding it in front of your face and trying to watch a movie on a 10m screen in the cinema! To move the sheet away to just the length of your hand will make a huge difference of how much left is visualized from that big screen! So I was curious to see how many A-10C instruments are dependable of this phenomena and I picked as much as possible (I'm sure there is more) to list them here for you: 01. Flight Path Ladder 02. Total Velocity Vector (TVV) 03. Depressible Pipper. 04. Target Designation Cue (TDC). 05. Gun Bore Line (GBL) Cross. 06. CCIP Gun Reticle. 07. Bullets at Target Altitude (BATA) Circle. 08. CCIP Bomb Reticle. 09. Rocket CCIP Reticle 10. Maverick Reticle 11. Firing Evaluation Display System (FEDS). 12. Air Mass Impact Line (AMIL). 13. Funnel Gunsight. 14. AIM-9 Seeker Reticle But then this weird question just popped up in my head, on why didn't ever occur to the screen architects to split the Hud in two categories: the active symbology listed above in a center screen and the static symbologies cited in the following list, that could be dealt with in a 2 cm frame on the edge as an extra undependable Hud: 01. Heading Tape / Scratchpad 02. Desired Magnetic Heading 03. Airspeed. 04. Barometric Altitude. 05. Flight Path Angle. 06. G-Meter. 07. Pave-Penny Cue Index. 08. Anchor Point Display 09. Destination Index (Tadpole). 10. Radar Altitude. 11. Steerpoint Number and ID. 12. Time to Go (TTG) and Time on Target Delta (TOT). 13. Current Time / HACK. 14. Required Airspeed. 15. DTSAS Mode and FOM Message. Remains of course a programming of this extra screen for a stereo visualisation for both eyes, compatible with the eye focused on the distance objects on the center Hud-screen.

It took me a few minutes reading in your Link to be aware of how naive I was to think the Hud could be also easily adjusted, especially with the good knowledge I have on Perspective. I thought it was enough to center the AI nose line and forgot how many things in an AI are also dependable of the Head position and distance to the Hud; I didn't think further than my nose! Any FOV with objects further than one mile will keep consistently all its properties' measurements and symbologies uniformly to the eye of the beholder, let alone any type of head movement in a 100cm radius. Thus the movement of the Head in any direction has no volume impact on them, however only on the Hud framed content that is not further than an arm length. This Hud is like a 2cm hole on a DIN A3 paper sheet holding it in front of your face and trying to watch a movie on a 10m screen in the cinema! To move the sheet away to just the length of your hand will make a huge difference of how much left is visualized from that big screen! So I was curious to see how many A-10C instruments are dependable of this phenomena and I picked as much as possible (I'm sure there is more) to list them here for you: 01. Flight Path Ladder 02. Total Velocity Vector (TVV) 03. Depressible Pipper. 04. Target Designation Cue (TDC). 05. Gun Bore Line (GBL) Cross. 06. CCIP Gun Reticle. 07. Bullets at Target Altitude (BATA) Circle. 08. CCIP Bomb Reticle. 09. Rocket CCIP Reticle 10. Maverick Reticle 11. Firing Evaluation Display System (FEDS). 12. Air Mass Impact Line (AMIL). 13. Funnel Gunsight. 14. AIM-9 Seeker Reticle But then this weird question just popped up in my head, on why didn't ever occur to the screen architects to split the Hud in two categories: the active symbology listed above in a center screen and the static symbologies cited in the following list, that could be dealt with in a 2 cm frame on the edge as an extra undependable Hud: 01. Heading Tape / Scratchpad 02. Desired Magnetic Heading 03. Airspeed. 04. Barometric Altitude. 05. Flight Path Angle. 06. G-Meter. 07. Pave-Penny Cue Index. 08. Anchor Point Display 09. Destination Index (Tadpole). 10. Radar Altitude. 11. Steerpoint Number and ID. 12. Time to Go (TTG) and Time on Target Delta (TOT). 13. Current Time / HACK. 14. Required Airspeed. 15. DTSAS Mode and FOM Message. Remains of course a programming of this extra screen for a stereo visualisation for both eyes, compatible with the eye focused on the distance objects on the center Hud-screen. Peter, I know you are a good programmer, maybe you can work on the design of a prototype with its programming and register it as patent. I'm sure "die Bundeswehr" will pay you well for it. I'll be happy with a 20% interest for this idea :thumbup:

Grüß Dich Peter, This great thread of yours has become so enlarged to the extent of a jungle where I got lost... May be the answer to my following question lies somewhere here in between, so excuse me if I ask for the following: I've solved the Pilot's head positioning in the Cockpit only. I like my head positioning totally sticking back as if it's under the acceleration of 5G, and off course, and a little bit to the top. So I think you know to which extent the Hud would be enlarged out of it's frame. What I'm looking for is the A-10C lua File & path with its formula that deals only with the Hud's size (width & length) . I assume with that head position, the Hud's size must be reduced to 30%. Mit vielem Dank im Voraus MfG

I think this formula is for the Pilot's head positioning in the Cockpit only. I've solved that... What I'm looking for is the lua File with its formula that deals only with the Hud's size (width & length) and its positioning (x,y,z). Looks like I have to make a hike to PeterP Thread anyhow, But thanks a lot anyway

It's good to know there's still somebody out there on the other side of the Atlantic with multicultural understanding :) But again for the last time for all the others: it's Ok to make the audio setting of RED Player in Russian. In that case DCS should offer for Users who buy the BS2 English version a Mission package with BLUE PLAYER, where the audio communications is in English! Second: if I knew DCS will reverse the language back to Russian again, I would have had exchanged the PLAYER to BLUE in all Ka-50 missions from the beginning, where I invested weeks of lost work in Mission Editor. So I do have a damn good reason here to get angry as compensation for the lost mod time in ME! OK now I've exchanged the sound files, but if my Russian friend want to fly on my computer, I must re-exchange those files again! This DCS back and forth policy was the main reason for my frustration. So for the DCS Admin, the Tenet written on the tombstone of this thread: Juggle decisions have consequences that the consumer must pay for. DCS Bad Policies - RIP

The Link looks very promising as it's also linked to other threads. Needs a thorough study. :book: Thanks a lot for the tip!

So maybe the system is automatically adjusted. But here in DCS you've clearly a Hud problem when you pull your position backwards. Try it yourself and have a look at the Hud again. The way how to modify your Cockpit position: 1. Go into DCS World/Options/Misc./Check "Enable User Snap-View Saving" 2. Load a mission. 3. Disable/pause your TrackIR 4. Hit once [NumEnter] Default FOV aka Zoom and [Num5] Cockpit Camera Move Center 5. Fine adjust it with: [RCtrl - RShift - Num8] Cockpit Camera Move Up [RCtrl - RShift - Num2] Cockpit Camera Move Down [RCtrl - RShift - Num*] Cockpit Camera Move Forward [RCtrl - RShift - Num/] Cockpit Camera Move Backward [RCtrl - RShift - Num6] Cockpit Camera Move Right [RCtrl - RShift - Num4] Cockpit Camera Move Left Povhat or: [Num8] Turn Cockpit Camera Up [Num2] Turn Cockpit Camera Down [Num/] FOV- aka Zoom-in [Num*] FOV+ aka Zoom-out 6.Once you are satisfied - hit [RAlt+Num0] to Save current Cockpit view as default for this vehicle.

I have finally managed to adjust my head position in the cockpit for a comfortable TrackIR head movement when looking down side ways to the left or right Consoles without having to crack my neck while doing so. With the Cockpit Camera control commands and finally with RAlt+Num0" I was able to save my current Cockpit view as default for A-10C, which is way backwards. But the disadvantage of this perfect cockpit setting is that the Hud was automatically enlarged to a point that up to 40% of it was out of sight on its frame border! I've tried the Mini-Hud setting, but went worse. So I've searched in OPTIONS/CONTROLS for any clue to adjust it, but didn't find any. I don't know in a real A-10 how the Pilot adjusts the Hud when he adjusts his seat, but I badly need a hint for Hud adjustment here by zooming it in and out. (in this case zooming out) If there is no Key-Command yet for it, maybe a formula to rewrite its lua-file!? (and its directory path) Many Thanks in advance

To end further grinding discussions, I've exchanged the folder: C:\Program Files\Eagle Dynamics\DCS World\Sounds\Speech\Sound\RUS with: C:\Program Files\Eagle Dynamics\DCS World\Sounds\Speech\Sound\ENG so for all Russian Fans; no need anymore to start WWIII :smartass:

What it was important that in the whole package I've purchased from BS2 mission, the player is red coalition. If all communications with the wingmen now are taking place in Russian, then it is just like the previous version of BS1. If the programmer in this case do not at least offer us a new mission package, where the player is in the blue coalition and thus can communicate with wingmen in English, what for have we paid then the extra money for BS2? BS1 would have been sufficient. Above that if I knew they will reset it to Russian, I wouldn't have had invested weeks of time in modifying the Ka missions to a higher level. Now all the work is down the drain, because it doesn't make sense anymore flying mission with wingmen that reply in Russian!

...And Spanish coalition speaking Spanish German speaking etc, papalapapp... The MAIN problem lies in the Ka-50 mission package you get when you purchase BS2, it's all packed with missions where the Player is RED coalition. If they want to set it back to RED Ka speaking russian, then at least I want a new Ka mission package modified where player is Blue coalition, so that I can fly DCS missions with wingmen and communicate in English!

YES exactly, I'm flying a BS2 on the RED coalition, and other BS2 Wingmen are speaking/replying in Russian. (it's not about labels or cockpit Info/language) All Radio DCS missions where Player and his wingmen are RED were communicating in English (with foreign accent) sofar until the last update. I bought the BS2 because they told me the Radio COM with Wingmen is in English, compared to the prior BS1 version. So if you've reset the RED coalition Radio communication with wingmen back to Russian now and didn't at least modify the Ka-50 missions from RED to BLUE coalition, what for did we pay the extra money? BS2 in only Russian is now exactly like the BS1 version!

Now I'm really confused, because as I've already mentioned in OPTION/GAMEPLAY/COCKPIT LANGUAGE, ENGLISH is already checked. So to avoid any misunderstanding, are you saying if you fly with that setting a Mission where PLAYER AI is RED, your cockpit is in English? Because in that case it is a bug problem that I only have. Can you try a DCS mission with a RED Player and confirm if that's the case with you? Thanks

Your DCS ID is a little bit confusing. Are you a member in the DCS staff team for programming or just a member?

1... I already speak four languages and I'm too old now to learn a fifth... 2... A Simulation is supposed to be real and depend on Radio communications, not a fiction text to be read on the forehead... 3... Hearing a foreign language in a real combat is a distracting torment for the pilot and should be dealt with as intrusive psycho weapon in warfare... 4... "Copying etc" is not a cool solution. Prefer to keep the original... 5: Update to the way it was. If I choose ENGLISH in the COCKPIT LANGUAGE, this must go for all AI nationalities! You want RUSSIAN as COCKPIT LANGUAGE, go to OPTIONS/GAMEPLAY and choose that. My frustration is big, because I've invested a lot of work in Mission Editor modifying a lot of DCS missions, where PLAYER is RED, and it was working fine up to now in English, so why now the stupid change? Only if you're working in the NSA and have the tools for an eavesdropping attack and have Russian speaking specialists, then write a new role in DCS for it - I'm not interested My matter of concern is, the first time I bought Ka-50 I on Steam, I was angry because the missions were still in Russian. They told me you need Ka-50 II to fly those missions in English. So I bought that. That means I also bought the right for the missions in English, and therefore have the right to claim for missions in English, not only in text, but also in spoken English! Otherwise it is the obligation of DCS to mod all DCS game missions and change all AI PLAYER from RED to BLUE to get it to work "properly", because I've invested weeks of work in modifying in ME the DCS missions, where PLAYER is RED, and now it takes the piss out of all that wasted work, when RED Player's COCKPIT turns Russian...

I've checked it up in OPTION/GAMEPLAY/COCKPIT LANGUAGE, where ENGLISH is already checked, but there is no "Turn it off" option, as you advised; either to choose ENGLISH or RUSSIAN. So if I've already have ENGLISH as COCKPIT LANGUAGE, why is it in RUSSIAN, when I fly RED? I've tested it with other Ka-50 Single Mission, where you fly RED (checked in ME) and there it is also COCKPIT-RUSSIAN spoken but with English subtitles! This goes to all other missions where you fly RED. The COCKPIT LANGUAGE turns to ENGLISH in missions where PLAYER flies BLUE. When you choose SPAIN or GERMANY for an AI as PLAYER, the COCKPIT LANGUAGE does not turn to Spanish or German. Is that only the case with Russia? Does that means I have to change in ME all missions where the PLAYER is RED to BLUE? I hope not - so there must be another way to fix this.

... I have already admitted, that I had a false assumption - I was just trying to explain how this left - right Discharger thing could be misperceived, as recently in an online chat other Simmers had it also in the wrong way like I did... The thing is: if the Left Discharger can go to the Right Engine or to the center APU, it's not crucial if the Dischargers were placed one above the other -Up & Down or behind each other- but the only decisive thing to know in case of two intermediate emergencies is, that the first Discharger bottle has been consumed and the second is still operable. Making a comparison with the Ka-50 Fire Extinguisher systems, once a discharger is pressed, there is a button light going on, whereas in the A-10C in a stress situation, there is no optical visualisation to remind you which Discharger you've already used... In that case the Ka-50 system is obviously the Winner!

... As being defined as Left & Right Agent Discharge in the Key Command, I assumed that only the Left Discharger is to be operated with Left Engine fire and so on, so I resumed with the false assumption, the APU must also have one of its own. A small linguistic misunderstanding, because as having two independent Dischargers, it would have been better citing them as no One and Two instead of left and right... So with only two Dischargers it's left to hope not having to deal with three fires at the same time!:pilotfly: Thanks for clearing me up

Left & Right Engines T-Handle Fire Extinguishers have their appropriate Agent Discharge in the Key Command. But shouldn't also the APU T-Handle Fire Extinguisher have one! Where is its Agent Discharge in Option/Controls? (see attachment)

Allies are speaking Russian again! :doh: We had that problem before, and now again - Really frustrating...:mad: I've tried some older missions where I play Red, and all the communications with Flight have turned into Russian, while the Text messages are in English. And YES, I've actualized those missions and resaved them with the Mission Editor, but didn't help. Hope we don't have to wait long until it gets fixed with the next update :P

Good Info - Thanks

Wingman is not responding to the order: Attack with/Air Defenses/..., he says first "roger" and then "rejoin". To the order: Attack/Air Defenses, always "unable"!! He does respond sometimes to the rest. (old problem since four updates)

Yes, beside the Saitek X52, I have the Yoke+Quadrant, which I need to split the throttle in case of Engine fire, and they were working fine all the time. Still though I flew once more with the Yoke unplugged, and the problem persisted. I just found out it was a corrupted lua File in (C:\Users\USER\Saved Games\DCS\Config\Input\A-10C\joystick) and the problem now is fixed. Beside that, are you also having the same problem with the Wingman who always responds to the order: "Attack with/Air Defenses", by saying rejoin instead? If not, can you try my attached Track mission by watching it to the moment where that order is given and when he replies "rejoin", take over control and try it again...