Leaderboard

Hello guys, After flying with BS2 and completing a few missions, something has struck me. They have adopted a new Point of View as to where the pilot eyes are in the cockpit, and as a result all objects rendered in the Shkval are shrunk to about 60-70% of their actual apparent size. There is also another little problem with the new POV. A little more than 5% of the Shkval TV screen is obscured by the black frame on the top of the monitor and it simply can't be seen anymore. Since the BS is ubberly dependable on its optical sensor, and it has no other effective way of detecting and/or engaging targets, I find these changes (Bugs? Features?) majorly disturbing. ID'ing targets at a distance has become a painstakingly difficult task now, since MBT's become a slice of what their silhouette once was. For me, this an enormous disappointment in the paid-upgrade, for it hampers our ability to ID and engage targets. I took a few screenshots from the same Airfield with the targets positioned at the same distance; roughly 3km) The first image illustrates the perfect apparent size as it was with BS 1.02 from a T-80 @3km with the Shkval at its maximum zoom. The second picture shows the same tank as it is depicted in the BS2 Shkval from the same tank on the same airfield, same distance and same zoom level as before. Another picture illustrating the first case-scenario, but now with the Shkval gate on top of the tank to better illustrate the lack of shrinkage in its apparent size. The last picture further illustrates the shrinking in the apparent size of the target @3km and demonstrating how distorted it becomes: One can also note that the frame on top of the Shkval obscures a good 5% of the top view, which did not occur in the first installment of Black Shark. So, is there something that can be done about this? I believe this to be a major drawback in the paid-upgrade. Sure having all the niftiness of grass, HDR and the such is a nice addition, but obscuring a considerable part of the only targeting visor we have and shrinking the entire world around us does not sound too reasonable. :thumbup: :pilotfly:

Exactly the same monitor set-up. Exactly the same Monitor options.lua I have tried full screen, windowed, every possible resolution from 1920 x 1200 to 2944 x 2280. I cannot get the ABRIS or Shkval to appear anywhere outside of their places on the cockpit. Suggestions? Hmmm, have to run windowed to export? Yea, it works. Frame rates are nothing to write home about in windowed mode.

Hi, folks. Reinstalled BS after quite some time (got excited by BS2). As I was reconfiguring my controls I seem to be having a problem with the collective. In the Options screen, under Axis Tune, everything seems fine. The graph matches the motion of the slider/throttle on the joystick (Saitek Cyborg 3D Gold). Looks good. In the cockpit, however, the response is completely different. I can move the throttle/collective halfway up before the on-screen collective begins moving. If I max the collective all the way up (engines off, of course) and then lower it, the lowering on-screen collective matches the position of the throttle/collective on the joystick. Just the upwards motion of the collective is out of sync. Even if I lower it half way and then try to raise it again, the on-screen doesn't move. Again, the graph under Axis Tune is fine, all motion matches. I don't seem to be having a problem in TKOH so I am pretty sure the joystick is okay. Thoughts? Mick

Is it possible to tell my wingmen to engage freely but stay in formation? (Relatively) I want to be able to control their positions very carefully because even with the "Hold" command they move too much. I often can find a spot where with a little flares or even "duck down/pop up" maneuvering can keep us safe from SAM/AA fire. But then they won't engage. If I want them to engage, even with a hold order, I have to accept that they're going to move around and they will die. They always always die as soon as they leave formation. :) :cry:

Viper, those are two different radar systems.

Not wanting to insult your intelligence, but you are assigning the Collective aren't you? Not the Throttle? It was a mistake I made when I very first installed BS1, and I know other people made the same mistake who were new to BS. Also, just read in another thread that people are finding they have to move the relevant axis in both directions to be fully recognised and accepted in BS2. Try deleting the assignment, then re-assign and move the axis in both directions the full range several times.

just curious if you are using the bs2 default unmodified keymaps or did you copy some from your bs1 install? I initially copied some stuff from BS1 and had a similar issue to you, looked fine in the options but the mappings would not work in the game

Спасибо! Обновил драйвер, все проблемы исчезли.

Вряд ли из-за этого будут какие-то конфликты. Да, синхронизация фпс игрушки с частотой вертикальной развёртки моника. Обрежет она не до 60, а до частоты конкретного монитора. У всех же моники разные, кто-то играет на старых элт с развёрткой 75-85 гц, кто-то на плазмах в 3д со 120 гц.

Вот замечательный мод, к сожалению автора не помню... cloud.rar

Try a different browser - I was also unable to make a tansaction wit Firefox. I used MS Internet Explorer than without errors.

UUMickey, When in the Axis tune window check to see if the axis you are using is set as a "Slider" (tick box ticked). If not, try setting it that way and test it out. Also try checking in the software that comes with the Saitek stick ... see how it is treating the axis ... typically the collective uses the "Z" axis. Just a couple of suggestions ... good luck and good hunting.

Well 8*MSAA is an FPS killer. ;) I'd suggest trying 4x. The difference is miniscule.

Sorry to say this, but what am I looking at? I don't see any difference worth noting?

I found this to be annoying to but for me it is not a problem, you can edit the pilots head position in the .lua files but that is not what I did, since I always fly with the Shkval "projected on the bottom 1/3 of the screen with the camera export files. It improves situational awareness no end! Screen shot(the only one I have of it at work, its not a very good example): It is sort of realistic as if you were in the chopper you could use your peripheral vision to see the screen out of the comer of your eye.

Да поставил, а как же без неё. Это она так сильно поребляет ресурсы или она и должна синхронизировать с регенерацией экрана? ....щас перезагуржусь и попробую. Смех!...но бывает, что слабое железо создаёт меньше проблем с настройкаи:) ZMEY-HS ты совершенно прав! Благодарю! Вот интересно, а стоит ли в файле графики тоже снизить ограничение ФПС чтобы не было конфликта там какого-нибудь? И к чему привязывает синхронизация к 60Гц обновления монитора? И вот тоже вопрос по поводу- а зачем тогда ограничение на 120 поставили, если вертикальная синхронизация обрежет до 60?

in the install files of the complete bs version (not the patch) there is no more shkval and abris lines but LEFT_MFCD = and RIGHT_MFCD = lines... didn't tested it personnaly as I still haven't activated neither bought.

Here is my setup works great windowed mode required This is a over/ under setup total res 1920x2160 Helios works in single player. No luck in multi player yet. Probably going to have to wait for Gadroc to figure it out. _ = function(p) return p; end; name = _('Airdogs Pit'); Description = 'AirdogsPit' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77777777777778; } } Shkval = { x = 575; y = 1152; width = 930; height = 345; } ABRIS = { x = 1675; y = 1461; width = 754; height = 495; } UIMainView = Viewports.Center

Быстрая миссия Су-25 В быстрой миссии ведомый бот Су-25 получил повреждение 1двигателя, пошёл домой на Кутаиси. Сел, снизил скорость до 60 а дальше нос не опустил и скорость не снижал до незначительной возвышенности, после взрыв. Причем это второй раз. В первый аналогично но на основных шасси не было резины и переднего колеса как здесь http://forums.eagle.ru/showpost.php?p=865812&postcount=103