Leaderboard

While waiting for Tacview 1.0, here Tacview 0.95a! Full Flaming Cliffs 2 support Black Shark and Flaming Cliffs 2 flight recordings have been optimized and are now 3 times smaller in average You can now choose where to record your flights! + Many fixes and improvements Enjoy! http://tacview.strasoftware.com Flights are now recorded by default into [\My Documents\Tacview\]

Hey guys. I had some time to kill and wanted to try something out. Here's the small test i did: Why make it? Well, to see what works really. What to look for here (for those who cares :P ): - Color toning. Darker contrast, less saturated. - Lens flares (tried not to totally over-do them) - Overall glow to the whole scene. -Camera angle, with the intended goal of having the A-10 pass by close to the camera, and then head off to the left and fire 2 missiles. - Tried to simulate a more "Natural feel" to the shot, by constantly moving the camera. And of course, sounds from the real deal, more or less. Also tried simulating sound delay. Cheers movie-fans (and a-10 fans alike ;) )

After I saw this post I thought it would be useful if we created a complete list of lua files which are automatically exported from server to clients. This is important for servers to be able to include various custom settings, especially since RvE is going to set up an Fc2 server quite soon on a 100/100 connection. Currently I know very little of which files are automatically exported, but here is what I know so far. Automatically exported files: Scripts/Database/db_sensors.lua Scripts/AI/Detection.lua Config/View/server.lua Lua files that can be included in mission file: config/export/config.lua (<51>Case) config/view/server.lua (<51>Case) config/view/view.lua (<51>Case) So if anyone wants to pitch in and help me and others figure out which are the other files, it would be great! If you make a post saying you know one more, i will add it to the list!

In other words, be cool, don't be cool_t.

Thanks :)

со мной перепутали

This patch adds multiplayer compatibility between the Black Shark and Flaming Cliffs 2. As such, either game can host a multiplayer mission that both products can fly in. Several additions and a few bugfixes have also been included in this patch. For a more complete list of changes and improvements, please refer to the readme1.0.2_en file. You may download the patch from the 1.0.2 EN page, http://www.digitalcombatsimulator.com/en/downloads/patches/dcs_bs_patch_1.0.2_en/ Please note that the most correct way of 1.0.2 install is: 1. Install clean 1.0 release version and activate (or have activated and not deactivated 1.0 or 1.0.1). 2. Install 1.0.2 patch. Please check the path of 1.0.2 patch install to avoid questions and problems. For those who have "BS installation not found, patch installation interrupted" message (it may appear in case your Operating System was reinstalled): You may install release version again, it will not ask you for activation, and 1.0.2 installer will found it. Or you may like to add registry stings with a path to 1.0 version yourself: HKEY_LOCAL_MACHINE, 'Software\Eagle Dynamics\BlackShark', 'Path', BSPath or something like HKEY_LOCAL_MACHINE, 'Software\\Wow6432Node\Eagle Dynamics\BlackShark', 'Path', BSPath for 64-bit Win-7 OS. 1.0.2 patch or new install of 1.0.2 version do not require new activation if your version wass activated already.

Bug description: The sound of the left engine disappears when starting the right engine. Steps to reproduce / Conditions of occurence Start a mission from park. Engines stopped. Start APU using standard procedure. Start left engine using standard procedure. Check how the left engine sound increases until nominal. Start the right engine using standard procedure. Check how the previous sound from left engine suddenly mutes. Check how the right engine sound increases until nominal. Shut off the APU. Shut down the right engine using the cut-off valve. Check how the engine sound decreases until zero. Check there is no right engine sound although left engine is on. PC Configuration N/A Attachments N/A

Technically there is no difference for detection, at least AFAIK. The only caveat is if you have a fighter flying below your altitude then the ground clutter and doppler notch will no longer protect you and thus you are detectable.

Миссия интересная для совместного прохождения. Но с производительностью надо что-то делать. У меня комп как-бы не самый слабый (C2D 4,5Ггц, 8800Ultra разогнанная, 4Гб оперативки), но 12-15 фпс я там часто видел, а это неиграбельно. Убирал указанные группы юнитов, убивал еще 20-25 единиц наземки - кардинально ничего не решает. Ни к в коем случае не хочу охаять задумку и саму миссию, просто она действительно малоиграбельна. У тебя самого сколько фпс? :noexpression:

I did some CAP for the Ka-50s on 104th server last two days. The worse threats were russian aircraft, that preyed upon the Sharks with the EOS, hugging the ground to not appear on AWACS and running to their friendly SAMs and ships area when threatened. Once the bandits are in the sharks playground, I had to use full radar mechanization to find the aggressors, paying attention to elevation and PRF, and also flying an optimal altitude for scanning (not too high and not being able to scan the full terrain below, but not too low and having too much drag and low speed - too many times doing a tail chase engagement). (Sidenote - I have seen many fighter pilots coming to the server and not knowing how to employ radar elevation and PRF, and then complaining why nothing appears on radar :)) Once we determined and patrolled their ingress route however, it was easy to defend. Oh and I may be wrong and it needs confirmation, but I think the russian EOS, when locking a Shark up close, triggers the LWR. One Shark pilot reported it being triggered when I flew past him with EOS on VSCAN mode and locked him briefly. He was at near a friendly airbase, no threats around, so.

Там же, но в файлике view.lua нужно сделать UseDefaultSnapViews = false, иначе он будет использовать дефолтные значения и плевать на твой исправленный файлик.

I'm not trying to argue with your point of view because I know first hand what you mean. My post wasn't a poke at your server either I just used it as an example of a mission that has Objectives so far away from one another and spread out. This thread though, is about what players expect out of the 2 sims being utilized together and quite frankly that is what I expect. If you don't want to work as a team or hop in Teamspeak with people then why are you playing multiplayer? It's an honest question. Lets face it this isn't a game with 20-30 maps with the objective being to totally go 30 and 0 and pwnzor teh noobs. If you play it like that it gets boring quick. The longevity comes from Playing it as a sim, and working together. Getting shot down is annoying as shit, but take a step back and ask yourself why it happened. It's Really funny when you hop in a server and see 8 people on one side in Ka-50's or A-10's or Su-25's and 8 on the other side in fighters and mud movers and then hear them complain that they got shot down. Obviously they aren't going to toss green lollipops at you. What it has come down to is a mario kart race for ground targets. PEW PEW my vikhr's,mav's,etc... 20 minutes later I'm done rinse repeat. Same thing in the air. There is no objective other than to shoot. Like I said, My 2 cents. *edit* Sorry this post might have come off a little vehement. Bit tired and cranky :doh: I know that not everyone wants to play it like a sim and its cool. Just gets boring the same old over and over.

anyone can tell me what time the german version will be released ?

One of the biggest air shows in North America happened this past weekend at Andrews AFB in southern Maryland the 2010 Joint Service Open House (www.jsoh.org) and yours truly was there to snap some pics which are posted for your viewing pleasure over at our squadron's forum: http://forum.51st.org/viewtopic.php?f=3&t=1512 Hope you enjoy them, and perhaps if anyone else went, share yours as well!

Less techy talk - more myths & stories please :D

Thank you guys !

Sorry mate, my schedule is full, so you'll have to find someone else to worship. Good luck :smilewink: Happy flying mate.:joystick:

Короче понятно! Одну ошибку исправят сто других сделают. И ведь ни один из разработчиков не ответил а оч жаль. Наверное просто ответа нет. Хоть бы сказали "Да косяк. Исправим."

It was prepared for a different sim by me some time ago. Here's one for black shark If one is a beginner: Use the Frazer's Tweak Guide and don't spare eye candy. It is easier to tune from high performance towards quality than opposite. Especially the lowest water setting and the recommended visibility settings. . Now based on my miniguide: set every option like all of the green settings. I hope I won't have to repeat that gray settings are to be ignored after working so hard on such a nice graphic :) Only two main 3D graphics driver settings two fiddle around left - AA settings group and Vsync. Tune the rest using game settings. . Make a decision - enable Vsync or not? Enabling Vsync is highly recommended for the reasons I explained in numerous posts and two main topics. Look it up. The minimum requirement for Vsync is that your system is capable of rendering not less than 20 FPS in absolutely critical conditions (lots of units and fighting). It is highly recommended again to use such game settings and AA settings (at least 2x is desirable) combination that will allow to meet minimum requirement for Vsync mentioned above. . After dealing with the most important settings mentioned above fine tune the performance using AA settings group and game settings. I've changed in-game settings to game settings to include all the settings one is able to change for DCS. Do you still have any questions, kobac?

Chip dude, this is not about realism and your personal feelings/preferences, it's about sounds that were made so we can hear them, while they are currently inaudible or muffed by horrific engine wav files. I dont care you like as it is, and that you think its cool, I just want to hear what was supposed to be audible.

This is what the other side of this engagement looked like from my point of view (F-15). Please note that I am a very new pilot that is still learning how to play. 3 of us took off out of Mineral. An SU27 and 2 F15s. We made our way to the ground pounders with the intention to get some of them to switch into fighters. The turkey hunt was on. We started low until about the last 60 miles and made a slow climb to FL250. We picked up 4 contacts on radar. 3 of them showing alt of 0 on the TWS. Our 27 pilot got contact on what he thought was the blue AWACS. He decided to go for it. The other 15 and myself leveled at FL20 and each fired AIM120s on the Ka50s 20NM out. They show up on radar very well. I dropped down to FL050 the other 15 stayed high. I had my radar slewed to about a low as I could. Narrow Focus, 10nm, and only searching the 0-5k feet. I had lock on a Ka50 at "Tank Hill" 5 miles out I let a 120 go on it. It went ballistic on its last mile. I never lost radar lock but I was probably to close when I launched and too fast. I don't really know, I am still new at this. I then switch to guns manual and dove on the ka50. I didnt have enough room to make the get a good angle so I pulled out and headed to the "river by tank hill". Our Su27 Reported that he shot down the Tanker. He then decieced that he was going to head back to us to assist with hunting KA50s. I then saw what looked to be Flares. (I guess it was an AIM9) Then at my 11o clock, an A10 in a steep right hand turn and I am on its 5 o' clock. I am still not very good with switching weapons in flight so I went full AB and charged in gave a guess and fired some cannon rounds a mile in front of him. Not even close. I shot by his tail and made a hard left and tried to regain a visual. I had my cannon radar on this pass and found an A10 flying in a straight line level. In about the exact spot I made my 1st pass. I took my time and gunned him down. Thinking that the A10 was destroyed, I went back to "tank hill" to reengage the blackshark. I switched to AIM9 and had radar on to help guide me into it when I saw an a10 over tank hill in a steep left hand turn. From my point of view I thought the A10 was trying to get a lock with an AIM9. I turned my radar off and fired. The Aim 9 hit him moments before he was able to complete his turn on me. Richard III ? My kingdom for a horse? (kingdom for a gun radar to calculate lead) I don't understand this. I was then fired on from behind. Missle warning going off I dove low over tank hill and made for the coast. It missed, (I dont know how) I turned back into the bandit. With help from the other 15. I turned the radar on and pointed it to FL15 and had a lock at 15ish miles. I fired my last 120c from the deck and turned back inland to a neutral airport. ( 800 Pounds fuel) On my way in I got lock with my remaining Aim 9 and downed a KA50. A little further on I saw a second KA 50 with its lights on and made a fast attempt to gun it down. I didnt have enough time and my shots all went over it. I buzzed it with less then 20 feet between us at 500 knots. The Blackshark managed a few hits with its cannon after my flyby. I was impressed but he didn't damage anything. I made a landing at the local airport and that was it. I can agree with this 100%. I had a f15 doing support at 20k feet. I wasn't looking for fighters. He was. 50s are harder to hit then I was expecting. (They are still the easiest target I have shot on yet.) But in order to get a clear lock you have to join them are there level. You are extremely vulnerable to enemy fighters yourself then. One fighter is enough to hold up a group of attackers. Advice to Blacksharks from my run. Most of the KA50s I saw hit had one major thing in common. They all had there lights on. 150+ meters is easy to spot on radar. Stay under 400 agl Hide in a city. If you cannot be found, you cannot be killed. Brown hayfield do not hide your profile from above. If you want to hide, Look for something dark below you to hide above. I makes you much harder to spot. Any level of support will increase your chances of not being shot down. To the post about how buildings have no effect on Radar. This is true, However if the missile cannot pass threw the building to get to the ka50 on the other side. It works better then chaff. Okay, sorry for the wall of battle I posted here. Again, I am new at this. So all of my information can be taking with a grain of salt.

I think alot of the problems that arise from joint operations with the KA-50 and the fast movers is how willing people are to accept the role handed to them. If you're in a fighter do you just wanna fly shoot missiles boom boom pew pew or do you want an objective? same goes for ground attacks. I can sit all day long and toss vikhr's at 8 klicks out, It's not rocket science. To me the fun is in the objective not in the big piece of metal flying at a target. When people start working together on TS thats usually when the fun starts. It's also when those objectives come together. If I get my ass handed to me by a fighter I don't sit there and go OMG easy kill I'm so mad!!! I say GK, Because it was. Either my air cover wasn't there or he was good enough to dispatch them and still come after me. Another reason why ground targets should be in the mix is because people who just hop onto a server to pew pew aren't gonna care about objectives. they are gonna fly to WP2 and pew pew it up. I will use the 104th server as an example. The operation liberty map thats up has the KA-50's at opposite ends of the fighting. If someone wants to attack those KA-50's and also the mud movers, They have to make a concerted effort to do so. By the same token if someone wants to defend said aircraft they have to make a concerted effort to do so. So at least if the air combat is taking place over the ground combat if they happen to shoot someone down guess what, They just protected a Ka-50's butt. Sure it might be easier for a fighter to shoot me down however it also is easier for one to shoot him down and so on. It's also alot more hectic for them to scan 50m off the ground and still watch their asses up high. Anyways just my 2 cents.

Official Server Rules: Rule 1: Be Cool Rule 2: Don't Teamkill Server Changes to be applied soon... Added files to the integrity check 1.) Config/export/export.lua (default file) 2.) Config/ServerGraphics.cfg 3.) Scripts/Database/db_sensors.lua 4.) Sounds/Sound.cfg 5.) Sounds/SoundDescr.lua 6.) Scripts/Aircrafts/_Common/ (except rearm.lua) 7.) Config/Weapons/ Highlighted in green are the new additions to the integrity check. Mission Changes: (applied immediately) Updated Capturing Maykop +Now plays static radio sound when important A2G messages appear +Move Ka-50 spawns closer to the front by about 35 KM or so Note 1: Rearm.lua is allowed primarily for the payload modification mod. However the reason it is allowed is specifically for A2G strike aircraft. That said A2A aircraft may take advantage of the extra payloads with the exception of TWO requirements. 1. Do not add weapons that would not normally (in the game) be allowed. No R-77 on Flankers, ETs only on the proper pylons...etc. 2. Max active missiles = 6 for F-15C and 4 for Mig-29S. Using an all actives payload goes against Rule 1. of the server so don't do it. Note 2: Export.lua has been added to the integrity check for a multitude of reasons. The most notable of which is the proper lack of control over which mods we allow, and which mods we disallow. It was debated to allow ERI and tacview into the server while blocking out LEAVU and other uses of export.lua. Unfortunately the end user experience is better supported by just requiring a default export.lua check, rather than for players to download a custom export.lua. As a result we are forced to block out Tacview and ERI from our server. If a more user friendly or preferably server side capability is developed to allow the inclusion and exclusion of specific modifications to the game, 3Sqn will support and utilize such features to the fullest extent.

With Full back stick then Full elevator trim I see NO stab movement: (Edit with Y SAT set to 100%) So I conclude Trim is limited to no more than Full Stab movement range.

Ничего и не зря - если кулер боксовый, то: 1. Охлаждает по минимуму, и разогнанный проц не сможет охладить; 2. Стоит иногда в несколько раз дороже, чем аналогичный...

Так ты посмотри для чего ты собрался ось добавлять - для свободной камеры? самолет то выбери.

А на такие?:) Пародия на фото с F-14))

Нет. Кодеки из системы больше не используются. З.Ы. 1) Есть скрытая опция Uncomressed AVI - для влючения надо в файле BlackShark/modules/record_avi.lua раскомментировать строку 51. 2) OGV формат поддерживается YouTube, хотя там это и не указано. 3) "Теодор" - это сильно! :)

now just FSX work well

Имеется ввиду, что с этой копии можно будет только устанавливать симулятор, а проверка подлинности будет осуществляться посредством активации, лицензионным ключом.

SU-17/22 http://www.vectorsite.net/avsu17_2.html

Верните громкий звук попаданий по вертолету внутри кабины! Я конечно понимаю,что новый движок и все такое,но это уже по-моему перезагиб на месте! Я полагаю тут разработчики скажут мол шлем на голове... ну и что что шлем- в реале кроме всего прочего еще и трясти будет(т.е информацию о попаданиях в реале пилот получит и тактильную и звуковую- а вирпил как?! ),да и звук попаданий я думаю шлем не глушит до такой степени что на него не перестаешь реагировать. В общем за приглушение звуков попаданий,автору звукового движка -двойка! Завтра на работу с родителями!(может помогут исправить)

did you check to see if your in game mode or simulation ?

^^^ No actually PAK-FA is slightly bigger ;) On the diagram the dark aircraft is F-22 so you can see the PAK-FA is a bit longer with larger horizontal stabilizers and bigger wing span

Jeder hier hat ein bißchen Recht, das Wichtigste ist jedoch, dass man openminded bleibt und den eigenen beschränkten Horizont nicht als der Weisheit letzter Schluß ansieht. Ich habe bisher noch nie von einem Flugzeug gehört, bei dem man eine automatische Anlasssequenz beider Triebwerke (natürlich nacheinander) mit einem einzigen Knopfdruck startet. Genauso geht es anscheinend dem Preussen... Die MiG-29 hat allerdings genau so einen Startmodus und gut vorstellen kann ich es mir auch, da der Trend im Cockpit-HMI-Design immer zur Vereinfachung geht. So hat z.B. der Eurofighter in seinen Sidepanels mechanische Hebelkonstruktionen, mit denen man ganze Toggleswitch-Reihen, die vielleicht beim Startup noch einzeln betätigt werden müssen, für einen schnelleren Shutdown im Dutzend mit nur einer Hebelbewegung wieder auf OFF setzen kann. (vgl. Bildchen im Anhang; Quelle: http://typhoon.starstreak.net/Eurofighter/cockpit.html ) Für GreyHead, der nie an was anderem als ner MiG rumgeschraubt hat, ist dieser außergewöhnlich seltene Startmodus das Normalste von der Welt, weil er es nur so kennt. Deshalb redet man hier leider teilweise aneinander vorbei. Wir halten fest: - der echte automatische Startmodus der MiG-29 ist in LockOn nicht simuliert, wäre aber sehr leicht zu programmieren. - in LockOn ist es unrealistischerweise möglich, beide Triebwerke aller Flugzeugmuster gleichzeitig anzulassen, und zwar entweder durch die beiden individuellen Startbefehle der einzelnen Triebwerke, oder aber durch den Doppelanlasser-Tastaturbefehl, der somit einen Easy-Gaming-Cheat darstellt. Wer also Realismus spielen möchte, dem steht für die MiG nur die manuelle Startsequenz im Spiel zur Verfügung. Dann aber bitte auch immer das linke Triebwerk zuerst und dieses vor Start des Rechten schön mindestens 40 Sekunden in Idle laufen lassen... :smartass::music_whistling::thumbup: Again what learned!

А за что Дэдли забанили?

ты либо не понимаешь, либо издеваешься - ED не делало механизм ограничения именно твоих видов. ED сделало универсальный механизм проверки любых файлов игры. список проверяемых файлов указывается на сервере. на том сервере, о котором ты говоришь, хозяева решили включить в проверку файл видов. вот и всё.

Финальный тест "Отряда Вергеева" Продолжаем финальный тест I части кампании "Отряд Вергеева". Публикую таблицу теста. Для того, чтобы было видно, на каком мы свете. Несмотря на то, что каждый из нас отлетал миссию не однажды и не дважды-по трижды - продолжаем отлавливать те или иные "косяки". Это уже не "баги", а мелочёвка - перепутанные даты, ненумерованные ППМ, отсутствующие (случайно прибитые на редакции тригы) и т.д. Дело весьма непростое, доложу я вам.

Джой продан.