Terrorvogel

Hi, can someone plz tell me what i have done wrong? I had already installed BS1 DVD-Version and then installed KA-50_full_en_bsupd_1.1.1.1.exe and KA-50_patch_en_bsupd_1.1.1.1.exe Now, when trying to fly, a notification for damn serial pops up!:mad: Where can i check, if BS1 is still properly registered? What else can be the problem? M....f...ing protection crap... Regards Terrorvogel

So all our hopes are with you Gadroc...may the force be with you...:) Regards Terrorvogel

The problem is, that there is no data coming from Lua which can be used of displaying the remaining flares to digits. It has to be calculated manually inside sioc.ini using the UV26´s direct inputs. The remainig flares are depending from numbers of flares and numbers of sequences you have set in UV26-panel. This variables and the multiple count when releasing flares (manually: x-times or automatic: intervall-setting in UV26 in x-time) For example: UV26 is set to: - 3 (flares) - 2 (sequences) 1. Single release should subtract: 6 flares from the total of 128 ones 2. If pressing "Start" in UV26 it depends how intervall-time is set and till pressing "Stop" again. This is the "easiest" way. For perfect solution we also need to notice the sides of flares (each has 64 flares). As you know, is it possible to release flares only for each side too. To count the remaining ones (per side and finally the total ones) there has to be integrated the "Side" position of the UV26 switch too. I hope i´m right so far with my explanation:huh: For someone who is able to programm such things it should be easy to write this. Maybe you can take a look at the code from guillesdrone´s code so far: This the SSI's Part of UV26 is there for 7-segments and light and buttons sequency and choice side // ************************************************** *************************** // * Config_SIOC ver 3.5 - By Manolo Vélez - www.opencockpits.com // ************************************************** *************************** // * FileName : gg.txt // * Date : 04/10/2010 Var 0100, name IniReUv26_LINK, Value 1 // INITIALISATION RETRO ECLAIRAGE { &RetroUV26_LED = &IniReUv26_LINK } Var 0101, name DigitDroitUv26, Value 0 // INIT DIGIT DROIT UV26 { &DisplayDroitFl = &DisplayDroitFl } Var 0102, name DigitMidUv26, Value 1 // INIT DIGIT MILIEU UV26 { &DisplayMidFlar = &DigitMidUv26 } Var 0103, name DigitLeftUv26, Value 1 // INIT DIGIT GAUCHE UV26 { &DisplayLeftFla = &DigitLeftUv26 } Var 0498, name gauchUV26, Link IOCARD_SW, Input 240 // SWITCH UV26 FLARE GAUCHE { IF &gauchUV26 = 1 { &uv26bordLNK = 1 } IF &gauchUV26 = 0 { &uv26bordLNK = 2 } } Var 0499, name DROITUV26, Link IOCARD_SW, Input 239 // SWITCH UV26 BORD DROIT { IF &DROITUV26 = 1 { &uv26bordLNK = 3 } IF &DROITUV26 = 0 { IF &gauchUV26 = 0 { &uv26bordLNK = 2 } } } Var 0500, name uv26bordLNK // SWITCH CHOIX DU LARGAGE FLARES Var 0592, name Uv26QP_SW, Link IOCARD_SW, Input 234 // SWITCH UV26 QUANTITé PROGRAMATION Var 0593, name Uv26Seq_SW, Link IOCARD_SW, Input 238 // SWITCH UV26 SEQUENCE { IF &Uv26Seq_SW = 1 { IF &DisplayLeftFla <= 8 { &DisplayLeftFla = &DisplayLeftFla + 1 } ELSE { &DisplayLeftFla = 0 } } } Var 0594, name Uv26Leurres_SW, Link IOCARD_SW, Input 241 // SWITCH UV26 NBRE LEURRES { IF &Uv26Leurres_SW = 1 { IF &DisplayMidFlar <= 7 { &DisplayMidFlar = &DisplayMidFlar + 1 } ELSE { &DisplayMidFlar = 1 } } } Var 0595, name Uv26Delay_SW, Link IOCARD_SW, Input 235 // SWITCH UV26 DELAY { IF &Uv26Delay_SW = 1 { IF &DisplayDroitFl <= 8 { &DisplayDroitFl = &DisplayDroitFl + 1 } ELSE { &DisplayDroitFl = 0 } } } Var 0596, name Uv26Start_SW, Link IOCARD_SW, Input 237 // SWITCH UV26 START Var 0597, name Uv26Reset_SW, Link IOCARD_SW, Input 243 // SWITCH UV26 RESET { IF &Uv26Reset_SW = 1 { &DisplayDroitFl = 0 &DisplayLeftFla = 1 &DisplayMidFlar = 1 } } Var 0598, name Uv26Stop_SW, Link IOCARD_SW, Input 242 // SWITCH UV26 STOP Var 0700, name UV26_larg_D, Link IOCARD_OUT, Output 31 // voyant UV26 largage droit Var 0705, name UV26_larg_G, Link IOCARD_OUT, Output 32 // UV26 largage gauche Var 0710, name UV26ret1, Link IOCARD_OUT, Output 33 // retro ecl UV26 Var 0715, name UV26_ret2, Link IOCARD_OUT, Output 34 // retro ecl UV26 Var 0720, name UV26_ret3, Link IOCARD_OUT, Output 35 // retro ecl UV26 Var 0725, name UV26_ret4, Link IOCARD_OUT, Output 36 // retro ecl UV26 Var 0730, name UV26_ret5, Link IOCARD_OUT, Output 37 // retro ecl UV26 voyant VERT Var 0735, name UV26_ret6, Link IOCARD_OUT, Output 38 // retro ecl UV26 Voyant ROUGE Var 0930, name fus_on, Link IOCARD_SW, Input 262 // inter de fusées Var 0931, name fus_1, Link IOCARD_SW, Input 252 // inter fusée 1 Var 0932, name fus_2, Link IOCARD_SW, Input 259 // inter fusée 2 Var 0933, name fus_3, Link IOCARD_SW, Input 258 // inter fusée 3 Var 0934, name fus_4, Link IOCARD_SW, Input 257 // inter fusée 4 Var 1030, name uv26power, Link IOCARD_SW, Input 255 // SWITCH UV267POWER ON/OFF Var 1033, name CA5VHF2, Link IOCARD_SW, Input 13 // SELECTOR UV26 CA5VHF2 { IF &CA5VHF2 = 1 { &spuselect_LNK = 1 } } Var 1076, name DisplayDroitFl, Link IOCARD_DISPLAY, Digit 194, Numbers 1 // AFFICHEUR DROIT UV26 Var 1077, name DisplayMidFlar, Link IOCARD_DISPLAY, Digit 193, Numbers 1 // AFFICHEUR MILIEU UV26 Var 1078, name DisplayLeftFla, Link IOCARD_DISPLAY, Digit 192, Numbers 1 // AFFICHEUR GAUCHE UV26

Ok i unsterstand that. I´m looking forward to your possibly solution sometime... Regards Terrorvogel

This sounds great Gadroc! I would pay for it! Where can i find the progress of theese things in the future (Link)? At you´re website or here? You´re my biggest hero if this is working sometime:thumbup: Regards Terrorvogel

I think you mean this thread which i already read: http://www.scsimulations.com/showthread.php?1100-BS-UV26-digits-display-moving&highlight=uv26 Yup this is really frustrating because nearly everything can be used by sioc exept this really important thing. To use a USB display for UV26 is the very last thing i´d like to do because of spending money and time into my "touchable" countermeasure unit which looks and feels so much better. Unfortunately my programming skills are too low, to write my own UV26-sioc-code of subtracting the flares. If i could, i would do so. In my opinion ED should fix this too, to finish Black Shark once and for all and to finally satisfy us little group of crazy homepit builders with a perfect simulation. I´m so sad because i know this will not happen... :cry: Regards Terrorvogel

Hi guys, is it possible to display the remaining flares with BS2 and Opencockpits-Displaycard using Sioc? I already inserted gillesdrone´s UV26 code: http://forums.eagle.ru/showthread.php?p=1077469 but this code will not display the subtracted flares, respectively the remainig ones. It always keeps staying at annoying "128". Everything else is displayed fine exept this "little" information. I know, that now, it´s possible, with BS2, to export the UV26-Digits via viewports in monitorsetup.lua but is there no way to put/translate this onto "real" digits? In times of BS1 i built a UV26 with Opencockpits Displaycard and 3-Digit in hope that it will be working sometime (digits are not yet glued inside): It seems we need some programming genius to do this...:smilewink: Regards Terrorvogel

+1

Nope - it´s just a wish:) I have seen Steelbeasts tank simulation and i thought that DCS could do this much better (Exporting things to other displays or integration of TrackIR for example). It would also be nice, if released, to interact with DCS:Black Shark or A-10C in online scenario :joystick: Maybe Eagle Dynamics should think about it...if they haven´t yet... Regards Terrorvogel

When will it be out? Regards Terrorvogel

+1

Really looking forward to a full working UV26 LUA (digits count) support... Greets Terrorvogel

Hi, can someone plz explain in a short way, the steps for customizing the indicators manually? I looked all arround in forums but i really don´t understand it... Downloaded here http://forums.eagle.ru/showpost.php?p=1256947&postcount=144 AN_ALR69V_init.lua and CMSC_init.lua. I placed them into my A-10C´s dedicated folders. What i see now is that the indicators are in wrong size and place. To place them up and down, i have to play around with coordinates in monitor.lua. But how do i change the letter size of the indicators. Are there dependencies with my main resolution of 5040x1050 in some other .lua? What are the next steps to adjust it to my needs? Is there a step by step how-to existing? Hope new Easy Monitor Configurator is on the way:music_whistling: Greets Terrorvogel Now it looks like this:

Thx a lot Nate, you brought me to the right direction:thumbup: I found out that there are some troubles with Asus´s standard drivers for Xonar DX with upmixing stereo stuff. So every one who has troubles with this nice soundcard and Black Shark here is the solution: Download Asus Xonar Unified Driver:http://brainbit.wordpress.com/2010/07/19/asus-xonar-unified-drivers/ Then uninstall old genuine Asus Xonar drivers in Win7 as usual and choose the option to delete drivers completely -->reboot After that, install the downloaded unified driver with the options in my screenshots and do my configuration settings. If having problems with driver signature during install, read at download link. Then it should be no problem with Xonar and additional subwoofer (or Buttkicker) with Black Shark stereo sound. The first screenshot shows the advantages of the unified drivers options (which you have to choose before install). The biggest, in my opinion, is the low latency driver which is also included in C-Media option. This probably can solve some stutter issues in aplications. Just try out... Greets Terrorvogel

When now playing A-10C the sub-out is working fine with buttkicker. Other games too. So it can´t be buttkicker or soundcard issue directly... In Black Shark, normal sound is only comming out of Headset (front-out) and not @ sub-out -->so no buttkick. I reinstalled DX9 June2010 again but the issue still persists. Why do all other games work but BS not? What else can i try? Greets Terrorvogel

Hi, due to lots of problems with my X-Fi, i bought an Asus Xonar DX Pcie-e sound card. But now in Black Shark i can´t get any signal out of the subwoofer output into my Buttkicker Gamer 2. In Xonar Audio Center i activated/deactivated 7.1 Virtual Speaker Shifter. In A-10C (and all other games) everything works fine with sub and Buttkicker. I believe BS does not have surround sound engine but why has the subwoofer-out worked in BS with my old X-fi soundcard? Didn´t made a new install of BS after changing to new soundcard. Maybe someone can tell me in which .lua i can check/change to the right sounddevice. Greets Terrorvogel

Works again. But plz don´t ask why. I have played arround in monitor.lua, graphics.cfg Nvidia ControlPanel. Now i have double fps again :) Can be closed... Greets Terrorvogel

I found out, that with windowed 4800x900 res. i have double framerate (60 fps). Why not at 5040x1050 windowed? The same happens if i´m disabling my additional little TFT´s in Win7 (which are driven by two seperate display cards). Then i also get 60 fps but in 5040x1050 What´s the problem here? P.S. Can someone of Triplehead users plz upload their working monitor.lua and options.lua? Would be great to still eliminate setting issues here... Greets Terrorvogel

The main reason for the low resolution at the MFD´s is that i more like the blurred image so it´s harder to recognize targets. I´ll bet that real TGP view is not as crystal clear as with "1024 every frame" setting. And even not so, i like it more... So i sadly must decide for blurry mirrors too. Nevertheless thank you for this link. It´s very interesting measuring the performance differences between theese settings. Thx for your explanation. It would be sad if this will be never changeable seperately... Greets Terrorvogel

Is there some technical background for this "linking"? Hope there will be a solution to seperate this in future... Greets Terrorvogel

Hi, does someone know in which .lua this is changeable? I don´t want to switch to "1024 every frame" because i like to let the MFD´s at 512 (which looks more real in my opinion and gets best fps ). Hope the MFD´s and mirrors are not linked together which would be stupid... Greets Terrorvogel

Yes, i have FOV problems too with TH2Go. I really hope the upcoming patch will solve some issues... Thx so far Regards Terrorvogel

Hi guys! Since A-10C release i havent´t played Black Shark for a longer time. Now i have the strange issue that BS sticks at 30fps, which seems no problem at first look. But it is stuttering as hell during flying. Before i had installed A-10C the first time, i had lots more fps in BS and not that "sticky" stuttering thing. With A-10C i have absolutely no problems with fps so the culprit can´t be my rig. With 6320x1050 in A-10 have 28-45fps with NO stutters. I´m running Win7-64 with latest patches and Nvidia Driver 280.26 and tried following: - Reinstalled Black Shark with DX9 - Disabled Vsync in Nvidia CP - Set FPS to 60 and to 0 in graphics.cfg and graphic_bs.cfg - Temporary disabled D2DOverrider (with forcing Vsync and Tripplebuffering) - Did a Win7 Systemfiles check Nevertheless it looks like it has something to do with Vsync. I really don´t understand whats going on here an really hope someone help me! BS is unflyable with this sh.. Regards Terrorvogel

AH-64 Longbow

Now it works! Didn´t knew that in A-10 Options the resolution can be inserted manually by double click... Now i´m running at 5040x1530 and erverythings fine. Thx to all so far Regards, Terrorvogel