S77th-ReOrdain

Cool. A great community for sure. Many have done the same for me and others. Glad to help.

OK. Finally have it sorted. With TrackIR running and starting in cockpit (doesn't matter whether you're paused or not): 1. Hit Ctrl-KP0(Ins) to activate cockpit snapviews. 2. Hit the KP# of choice to be programmed (this obviously will not be your final view, but will serve as your reference to confirm success). 3. Hit Ctrl-KP0(Ins) to get out of snapviews - I have a suspicion that this also preps the button by resetting/clearing any previous view setting. Seems redundant, but skipping these first 3 steps produced unwanted results similar to your previous description. 4. Hit the KP# you want to program (again). 5. Set your 6DOF view preference, including your zoom level, height and vertical position in cockpit. (Very important not to attempt to freeze your view by hitting any other KP# at this point. However, you can use default keys KP/ and * to zoom in and out). 6. Hit Alt-KP0(Ins) to initiate program. 7. Immediately, while also trying to hold your head still, hit the same KP# you hit in step 4 to confirm program and finalize. 8. Test for success by hitting Ctrl-KP0(Ins)/KP#. To prevent un(re)programming what you just did (if successful), make sure you follow all the steps again. I kept overwriting my previous button programs when failing to follow steps (1-3). If for whatever reason your default cockpit view gets thrown off again, you can correct it by programming KP0 with the above procedure, or with the re-center head shift trick (didn't know about that one). Please let us know if this gets you where you want to go.

Wow, sorry about your troubles. I'll nail down the exact procedure and report back. I know the frustration with this (been there), which is why I warned of the tricky nature. Rest assured, it works and you'll get the help you need until its all sorted.

My pleasure dude. After reading the other thread, the procedure I listed may be out of sequence. You may have to hit the keypad# you want to save first and then hit alt-keypad0(ins). I eventually lucked up and ended up with what I wanted. Guess that's why I found it so tricky. ;)

Try editing your snapviews.lua and/or view.lua file located in the ../Ka-50/Config/Views directory. You can accomplish what you're trying to do by editing the values. Take the necessary precautions by backing up those two files and only edit using Notepad++. The easiest way I've found to accomplish this is by using the Right Control-kpd0(ins), as Boulund suggested, to lock snap views and then using the keypad button of choice. If you have a programmable HOTAS, the view switch can be made instantaneous by combining the keypress combinations. I use (control-kpd0 / kpd2) to snap a full screen view of the IT-23. That's where editing the snapviews.lua file comes in. You can specify what the keypad buttons actually snap to. *Important to note that these files carry over from Lock On and control views of pits that are not actually flyable in Blackshark at the moment. Snap[1][2] = combination controls keypad button 1 of the Su-27 (second number value is off by 1). You want to manipulate Snap[9][1-13] for the Blackshark. The plane index section in the view.lua show which values control which aircraft.* The other way is to save the zoom view of choice by using the alt-kpd0(ins) method. This is a little trickier and may require some trial and error to get it the way you want, but what you end up with is the exact view. This method saves your view to the SnapViews.lua file mentioned above. Make sure that line 26 (DisableSnapViewsSaving) and line 27 (UseDefaultSnapViews) are set to false in the View.lua file to insure that your view is saved and written to the SnapViews.lua file. To get it to work: (1) set your view (2) hit alt-kpd0 (3) hit the keypad number you want to save the snapview to. A quick search revealed this thread for more help - http://forums.eagle.ru/showthread.php?t=35163&highlight=snapviews You can try using my custom Snapviews values if you'd like. Good luck. Snapviews.lua.txt

Try opening the VLC media player window by going directly to the VLC.exe in the Plugin folder. Select tools, then preferences. In the interface settings tab I believe there is an option to start as systray icon. You can see if checking that box makes a difference. I also turned off the activate update notifier (less running in background). I'm not sure if this will work but it's worth trying.

That was the one Repeat! It works perfectly. What a great addon.

Hi repeat, Thanks again for this awesome addition. I tried adding the additional code to the export.lua file with the following results: Radio will still start playing in either AM or FM when selecting the designated frequency. Radio will continue to play if switching from AM to FM. Radio will pause if switching from FM to AM and will only play again if another frequency is selected. I've attached a text version of the export.lua file to review. It's very possible I did something wrong. Export.lua.txt

Excellent addition. Highly recommended. 1. Download file (I downloaded the IRadio.zip file as I didn't have previous version) 2. Backup existing export.lua - ( . . \Ka-50\Config\Export\export.lua). You can also backup your existing config.lua file (same directory). Replacing config.lua is not necessary as it replaces the old file with a copied (russion version) of the same file. This enables exporting. 3. Extract all files into Ka-50 game directory. This will install the nifty VLC program into a new Plugin directory created by the extraction. **WARNING - changing skins in VLC caused a problem. Recommend you use the default skin as the program struggles to locate the default skin if it has been changed. I had to install full VLC program to correct this.** 4. Open the ifreq.lua file - (. . \Ka-50\Plugin\ifreq.lua) 5. Modify the tuning frequencies and radio stations to your liking. 6. I used Windweapon's suggestion and "right clicked" the tune in button on stations that I liked on Shoutcast. Just select properties and copy the URL location (http:\\ . . .) and paste it over the existing stations in the ifreq.lua file. Mind the "" quotes. HINT - if using shoutcast stations, select the "I want to use my own player" option. Using the shoutcast media player to extract the station address will also include the media player in the address which is not desirable. 7. Save your new ifreq.lua file. That's it. Go fly and try your radio. Be sure to tune the correct frequencies. Switching AM/FM has no effect, although it would be nice if it only worked in one (preferably FM). My skills don't go that far. Now you can fly and listen to the stations of your choosing with ease. If I really want to be distracted, on long flights I can even watch inet TV. 10 radio stations and 5 TV stations, too cool. Thanks to Repeat.

This sounds like a good endeavor. Best of luck with your efforts. A really helpful feature would be the ability to select multiple units by some method and then copy/paste them within the current mission and/or other missions. This method would need to go beyond the template creation function so that units of varying types can be selected together.

Just tested this properly. It doesn't work in multiplayer. Apparently, it is only effective locally - client maintains control of external view distance. Would be nice if view distance could be enforced on the server.

There is a compromise to this situation: Go to the server.lua file located .../Ka-50/Config/View/server.lua Back up the file - Original_server.lua, or whatever Open server.lua in Notepad++ Locate line 19 - ExternalObjectsLockDistance = 10000.0 Alter the lock distance to your preference - (I use 100.0) Save the file Now you and all clients joining the server are limited to the altered view distance. You can inspect your own helo, or check wingman (if he/she is is within 100 meters), and still enjoy external views with full zoom. This makes its difficult to exploit the combat view cheats, but will allow the moderate consumption of eye candy.:)

. . . hmmm someone does appear to be listening.

Nice work LB. Thanks for the update.

Apologies for continuing off topic, I experienced this as well after re-installing Black Shark following a drive failure. Go to your windows control panel and look for keyboard or other software to program the keyboard. Make sure your Left windows, right windows and/or other modifiers haven't been disabled. I also have problems programming the right shift key, but have found workarounds. I'm running Vista, so I don't know the exact interface, but in vista, those keys can be re-enabled by going to keyboard --> then keyboard properties.

Thanks Cap_Z. This works well. Used in combination with ZaltyZ's example of how to set up the "F" key as an advanced command using a delay on the release, the collective brake moves as if one was grasping the collective. Much improved control when establing desired altitude hold. The Z's know something ;).

Yeah, it's those darned twist sticks that got me started off on the wrong foot in the first place. Twist sticks rotate (pivot if you will) in the same manner that an inverted rudder would. I tried flying the correct way and I hate it. Control is gone to hell. Where I once could do laps around the runway and pirouettes around the tower, I now struggle about like a giant drunken hummingbird. This may take more than a week to get used to. For those that struggle to understand how someone could possibly get this wrong, fear not, it's not that big of a deal. If I ever have to take over the plane because the pilot and co-pilot have suddenly become incapacitated, I have confidence I'll get it right (or wait, left). ;)

I think I've been shamed enough into giving the correct way a try for a week, or so. :). Hopefully, I'll get used to it quickly and make the switch permanent.

Yes. Unfortunately, I do this too. I think this feels natural to me because I equate it to the feeling of cornering in a vehicle or pivoting. If I turn left, I lean into the turn. For me (former athlete), pivoting by planting my left foot (if I'm turning left) just seems more natural. Even though this is wrong, I continue to reverse my pedal inputs, because most of the time I'm using them unconsciously. In the heat of battle, I don't have to think about it.

I beg to differ. In game, it works very similarly to targeting points. The closest explanation to it is on page 7-9 of the manual. (Assuming Targeting mode has been reset) 1. Select the Datalinked target of choice (it will flash on ABRIS) 2. Select the "DL/Ingress Button" (next to Send/Mem). Once selected, your target of choice will be marked in a cross on the ABRIS. 3. Uncage the Shkval. At this point, the Shkval should attempt to "snap" to the datalinked target location if it is within the Shkval field of view. Fine tuning may be required. Also, notice that the targeting gate on the ABRIS should be over the datalinked target icon. Keep in mind, as long as your AP functions are engaged, your aircraft will also attempt to orient itself on the targeted axis when approaching to attack. Have to test later, but you may also be required to turn your Automatic Turn on Target button to maintain the targeted axis while attacking. Love to use it for high altitude rocket suppression at long distance. It also saves a lot of time when needing to identify the exact target that has been handed off.

Thanks Acedy. Great effort.

Agreed, that statement was in fact speculation. I've been screwing around with the flags (both true and false) and have yet to establish any consistancy in the MP environment. Nevertheless, the other rules I listed do work as previously stated. Exclude the use of group dead as one of the rule conditions and the sound will play properly for all clients. However, because I haven't tried the player coalition rule, the sound plays and message shows for all clients when the event finally does occur.

Thanks for the explanation nemises. I can already think of a couple of good ways to put those triggers to use. I've been holding off on building new missions until the patch comes out as well. I guess now is a good time to experiment with the current capabilities in existing missions.

I've been experimenting with the sounds and the message triggers. Unit in zone, unit outside of zone, time more, time less, unit dead, unit damaged and flag is true all seem to work without going off at once at the beginning of a MP mission. The culprit is "group dead". It causes the wierdness with clients in MP, but not with the host. Remove group dead as a rule and the problem should go away. An alternative is to set a flag to either true or false when a group dies and use the true or false trigger condition to activate the sound or the message. Now, if someone could please explain an effective use of the front condition and continuous trigggers, it would certainly help those of us that haven't a clue.

This is probably a question for the mission section, but I will attempt to answer. Follow normal procedures to load an ABRIS flight plan as described in the manual - Sec. 3-68. From the ABRIS Menu Screen (you will see "MENU" in upper left hand corner of ABRIS when you are on the correct screen). It is the default screen. Select PLAN (takes you to PLAN Sub-menu), Select SELECT (drop down menu pops up), scroll to LOAD and select it (takes you to a list of mission route plans - if there are plans saved in the mission database), select LOAD after you have scrolled to the appropriate plan, and finally, select ACTIVE (to make the plan the active plan in the ABRIS). This is one of the Ka-50's lesser used features that will hopefully be exploited by mission designers in the future.