Hunden Ynk

As a big fan of both Richardo/Devrim's Black HD cockpit and Richardo's Blue cockpit, I've never been able to choose one and always found myself switching between the two. The thought of having them both installed at the same time and picked according to livery did occur, but I never pursued the idea. Until I bought the Huey, which has that feature. So, a quick look at the files of the Huey, revealed that adopting it for the Shark, would be an easy task. Note! All credit goes to Devrim, Richardo, Belsimtek (for showing how it's done) and Eagle Dynamics of course! If interest exists I could upload the whole ready-to-use package, textures included (I know Devrim thinks it OK, just waiting for confirmation on Richardo as well) In the meantime, this is how it's done: What you'll need: Basic computer skills, copy, rename, working with archives, etc. But don't worry, it's super simple - if anything seems strange, it's just my inability to explain clearly. Just ask and I'll try to better myself. Cockpit textures Note, this procedure work with any BS2 textures, and you could have more than two, this is just my preference and what is used for the example. Ricardo/Devrim's Black Cockpit - http://forums.eagle.ru/showthread.php?t=94081 Ricardo's Blue Cockpit - http://forums.eagle.ru/showthread.php?t=99751 (download available in this post: http://forums.eagle.ru/showpost.php?p=1825818&postcount=153) Software A text editor. I use Notepad++, but just Notepad is fine. A program for (de-)compressing ZIP archives. I'll use the free 7zip, but WinZip, WinRar, Windows-built-in etc. is fine, but you will have to modify some step as per your programs mode of operation. Steps Copy both texture-packs to a temp folder, I'll call it [TEMP] from now on and extract them like shown below, you'll get two new folders with the same name as the archives. We'll use the Blue packs folder (the one named [TEMP]\Cockpit-Ka-50 Textures) as our work directory. Open that folder, the many files here are the different textures that makes up the cockpit. The neat thing is that most of the textures are the same for both the black and the blue version, so we only have to work on a few. Append _blue to the name of the following files: Ka-50 dash-board Ka-50 devices Ka-50 interior Ka-50 interior2 Ka-50 Panel L Ka-50 Panel R Ka-50 RightTopPan Ka-50_recockpit_1 For example: Rename Ka-50 dash-board to Ka-50 dash-board_blue Navigate to [TEMP]\Devrim_DCSWBS2_UpgradedHDPit_v1.1\Mods\aircrafts\Ka-50\Cockpit\Resources\Model\Textures\Cockpit-Ka-50 Textures.zip. Select all files within the archive and copy and paste them to our work-dir (the folder where we renamed the files remember). When asked about replacing, choose no. Your work-dir should now look like this, green marks whats different from stock: Re-compress the cockpit textures like shown below: Copy (and replace) your new zip to [DCS World]\Mods\aircrafts\Ka-50\Cockpit\Resources\Model\Textures (I'll use [DCS World] to indicate your DCS World installation path) Copy [TEMP]\Devrim_DCSWBS2_UpgradedHDPit_v1.1\Mods\aircrafts\Ka-50\Liveries\Cockpit_Ka-50\english.description.lua to the corresponding location in your DCS install Now we need to bind the different textures to the corresponding livery. I'll use the Russian Worn Black for this example. Open the file [DCS World]\Bazar\Liveries\ka-50\Russia Worn Black\description.lua and add this after line nr 19: {"dash-board", 0, "Ka-50 dash-board_blue", true}, {"devka 50", 0, "Ka-50 devices_blue", true}, {"interior", 0, "Ka-50 interior_blue", true}, {"interior 2", 0, "Ka-50 interior2_blue", true}, {"panel ka 50 left", 0, "Ka-50 Panel L_blue", true}, {"panel r", 0, "Ka-50 Panel R_blue", true}, {"right top panel", 0, "Ka-50 RightTopPan_blue", true}, {"Ka-50_recockpit_1", 0, "Ka-50_recockpit_1_blue", true}, Final step: Open [DCS World]\Mods\aircrafts\Ka-50\entry.lua and add this after line 75: mount_vfs_texture_path(current_mod_path .. "/Cockpit/Resources/Model/Textures/Cockpit-Ka-50 Textures") Try it! Now repeat step 7 for any livery that you want in blue colors. Knowing which one is supposed to be blue is of course the real challenge here. I'd love some help on that. So far I've only found three cockpit-livery pairs when searching the net. (With one being a grey pit. :noexpression:) I'm sure the truth is out there! (Wish I knew Russian. :()

I've not seen this (MSFFB2 user), but something sure seems iffy about FF in late versions. Troubleshooting semi-random stuff like this can't be easy. Toby23: When using simFFB you'll need DCS FF to be on, otherwise you'll get the traditional need-to-center-stick-mode of trim if I'm not mistaken.

One thing that has bothered me (a teensy bit) when using this savior of a mod. Is that when the trimmer is released while the rudder being off-center, the rudder will jump a small distance in the direction of deflection before going back to the old position. Enough to slightly offset the aircraft, for example, when going fast and straight, with right rudder applied to counter side-slip. I don't know if I'm doing something wrong (configs, input-setup, etc.) to suffer from this. But tonight I thought about reducing it. I remembered that old dreaded stick-center time, and thought tinkering with that variable could help. And behold, setting HelicopterTrimmerTauInverse in DCS World\Mods\aircrafts\Ka-50\FM\FMOptions.lua to 0.0, fixed my problem. Since I'm a FFB user with non-centering pedals, I don't even need the mod after that change. For non-FFB users this change would of course not work, since the value is shared by both cyclic and rudder, and this mod would be required instead. Does doing this have any know side-effects that I'm not aware of - everything seems OK during my brief testing.

Layman alert! I'm using the SimFFB application and to my understanding it hijacks the DirectInput data from the joystick before sending it to DCS. Could a technique like that work in this case? Edit: What's the point? Beats me - would be more of an hassle than PeterP's mod.

Sorry, I just mentioned it to illustrate that this might be (and most likely is, from my point of view) a matter of deliberate design - not a bugged system.

Cookie for me! :) Have you tried Route-without-task-mode, it works like number 3 on your list. (At least I think, since I'm too lazy to confirm right now.) Now wouldn't it be silly of Kamov to make two modes that function in the same way? And I personally find the operation of number 2 to be more intuitive as a default kind of mode.

It makes sense to me, which I tried to explain in my (mad?) rambling post. I'll try again, like this; if you're moving the cyclic in any direction. (AP channels on, trimmer not held down) The AP must in fact have an effect, since without it, your off-neural cyclic position would continue to alter the angular position of the aircraft, 5° bank becoming 10°, 15°, 25°, etc. But that doesn't happen, meaning the AP must be inputting the reverse of your stick movement. Now press trim, and bam, the AP effect goes away and the aircraft's position jumps. I might be wrong, but my brain says it's OK.

Achievement unlocked: Kamov Test Pilot :thumbup:

Yeah those articles are great, and I would praise the ground EinsteinEP has walked on! :thumbup: Having said that, I don't think they can be seen as reference style docs. Perhaps he just forgot to mention it?

Sorry for lacking the ability to explain what I mean properly, I'm curious about this though: Where is that? I'm finding the manual a bit sparse on the AP documentation. Finally you can try the Route without task mode, meaning Route mode on, but no WP, TP or airfield selected on the PVI-800, if you're dissatisfied with the AP.

I'm not sure I getall you say, but I'll shoot and you can correct me if I misunderstood anything. Also, I'm no expert, so my findings might be a bit naive, and hope I might learn something as well. It seems that the AP out of Route and Hover mode is polite enough to never try to negate the inputs of the pilot. Here's how it behaved under my quick test: From level flight I moved the cyclic slightly to the right, yielding a bank angle of about 5°. Holding that very same cyclic position, and the bank angle kept stable at 5°. (For testing purposes I disabled the heading AP channel, not sure if necessary though.) If I moved the cyclic slight more to the right, I could get to a position where it would hold 10° for example. However, at a certain cyclic position, the AP would no longer be a able to hold a given bank angle, and the angle would continue to increase even as I held the stick steady. That must be past the famed 20%. If I moved the cyclic back to the neutral position, the helicopter would evenly move back to that initial 0° bank. If the same maneuver would be performed with the trimmer held down, FD on, or Bank AP channel off, i.e. no AP. The bank angle would continue to increase as the cyclic was kept in that slight right position, the one that otherwise would hold 5°. To maintain a constant bank, one would have to center the cyclic when preferred angle has been achieved. And to get back to 0°, the cyclic would need to be deflected in the opposite direction. So there's a delay for the AP to kick in, allowing you to perform small changes in attitude without interference of the AP. But the AP will eventually kick in and while it will stabilize the movement at most, it will never actively steer you back as it does in route mode. Meaning, never turn your 5° bank to zero. Unless you move the controls back towards the trimmed position, then it will. You can also experience this if banking nice and steady without holding down the trimmer, and thinking - I want to trim this bank angle. By pressing trim at that moment, you will cancel out the effect the AP was in fact having, and your bank might jump from 30° to 60°. Is that what you describe in your point nr. 2?

Oh, how silly of me to miss that. Sorry. Great work though!

If you're into fixing things. (Obs! You don't have to!) I have thought about this one, the INU update method switch, under the PVI-800 keypad. Why not name one mode, I-251V (Shkval) and the other Fly Over, as stated by the manual. Or does INU-Update makes sense to you guys?

Thanks, just wanted to be sure I didn't break anything by changing that. My first thought of that inverted ocean-land-thingy, GPU meltdown.

Is the coffee example all wrong? I'm thinking pilot induced oscillation is the same (unconscious) behavior of micro correcting, where the pilot ends up correcting the corrections in an escalating loop. Wrong?

To my understanding it's similar to trying to balance a cup of coffee, walking down the corridor. Your continuous corrections will just make the liquid more and more unsettled. Now replace coffee with aircraft controls, and things get more dangerous.

Two posts in a row, very embarrassing. ;) I'm just wondering if there's a particular reason for CameraTerrainRestriction to be set to false on line 17 in server.lua. Under ground is pretty psychedelic...

Has anybody ever done a proper AMD vs Nvidia test with comparable cards, would be interesting for sure...

Thanks a lot! I'm such a pleb that I didn't mind the default settings, but something about this feels right, and I'm not risking to summon Max von Sydow when doing the Ka-50 anymore.

Gotta save something for v2.0 ;)

Amazing work Devrim! No excuse to not buy this bird I guess. If you haven't seen this video posted by ObvilionLost: http://forums.eagle.ru/showpost.php?p=1879013&postcount=13 It contains some nice closeups of an English cockpit, to find that old muse perhaps...

Huh, DCS Humble Bundle is where itz at y'all! :P

I wasn't, just smiling (big SMAC, JA2, X-COM fan here). Though, I'm too tiered right now to imagine how that level (several levels?) above CA could look. A dynamic campaign engine would surly go a long way. :music_whistling:

Next: DCS:Budget Committee ;)

Ok, I don't know how common auto-hover-systems are, my hunch, they're rare. The Huey at least have no auto what so ever. Hopefully some vet will enlighten us...