Leaderboard

By Dimitrije Ostojić:

:clap_2::clap_2::clap_2::clap_2::clap_2::clap_2::clap_2::clap_2::clap_2: Great video! Excelents cams! Excelent music! ¡AWESOME, JOB! Waiting the Campaign! :thumbup:

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

Спасибо!

MJoy16 http://www.samoletiki.com/MJoy16c1.html схема элементарная. Можно 64 кнопки, 16 тумблеров и много чего другого повесить

If you dont like scratches on your Canopy, remove it with this atached mod. Work for all planes. Maybe on some "old" machines give + few FPS. ;) Install with Modman. NoCanopyScratch FC2_0.rar

Ahh.. maybe that was it!

On that mission the combat air patrol (CAP) is between wp 2 &3 I believe. Just fly between them,(2 then 3, then back to 2, etc, etc). Don't worry. You will soon have more to worry about than waypoints!

little teaser video guys for you to drool over, turn your speakers up. http://www.youtube.com/watch?v=BiSF79tTzis

Jim, I have been experiencing a very similar problem in Black Shark that I believe is the same issue (correct me if you're seeing something different, Moose!): when I try to playback tracks recorded from a multiplayer session, they "go bad" after a few minutes. By "go bad" I mean that playback shows events differently than they actually occurred. For example, in one particular session, I took off from a FARP, headed into enemy territory, took out two enemy AI COBRAs with Vikhrs, took out another one with the cannon, but took a beating from a 4th and had to limp home, making a miraculous emergency landing at base. When reviewing the replay, everything seems normal up to the point where I intercept the Cobras: then, according to the replay, I lazily hover while the Cobras proceed to nail me from my flank, destroying my poor Shark while I don't react at all. This most certainly didn't happen in the online session! It *appears* as if the AI Cobras are behaving/reacting differently in the replay than they did in real-time, and, since the track is just playing back my recorded inputs, the mis-match destroys the accuracy of the playback, leading to the frustration that Moose expresses above. This happens whether I'm hosting or joining another server. The only tracks I've checked have been very large, and I've always used time compression to get from the start of the track to the juicy bits and wonder if something's getting out-of-whack during the speeded up bits? I'm playing Black Shark 1.0.2, patched over 1.0, no mods whatsoever. Panzertard has a good description of the problem (and what seems like a reasonable suggestion for a fix) here: http://forums.eagle.ru/showthread.php?t=42571

What I've noticed is that you get the prompt if you have a situation like this: Two planes (whether in the same group or not) are using the same payload, let's call it "Super Great Payload". On one of the planes, you decide it needs more Mavs or something, so you alter "Super Great Payload". That all looks fine. Then later you access the payload screen for the other plane. It's still set to use the same payload name ("Super Great Payload"), but its actual payload is still the original version. That's when it prompts you to save the payload, because it's not finding a match in the configured payloads for what that aircraft actually has. What I normally do is hit cancel on the save payload dialog, and then click on the "Super Great Payload" name to reset it to the new version of that payload.

Lol, perfect time to slap down my new image. The left switch toggles L/R/L+R dispensers and the right switch toggles between program and quantity display. Give yourself a program with a flare density balanced between being effective and dropping them all too fast. Average of 1.0 per second is middle of the road. Total program duration should match how long you expect to be safe after being in trouble.

The real HUD does look like these. Yes, it's beveled. But you still see the upper surface because of the light refractions. See this diagram. I changed the texture names and types to isolate the shared files and/or add the alpha channel. I masked out the part of the rail over the indicator to reveal it. Here is the complete list of changes. This is described in the mod readme, too. A-10-ALT-PLASHKA.bmp > F-15-ALT-PLASHKA.bmp A-10-ALT-PLASHKA-N.bmp > F-15-ALT-PLASHKA-N.bmp A-10-ALT-PLASHKA-TEN.bmp > F-15-ALT-PLASHKA-TEN.bmp A-10-ALT-PLASHKA-TEN-N.bmp > F-15-ALT-PLASHKA-TEN-N.bmp A-10-RUCHKA.tga > F-15-EMG-OPEN.tga F-15-CDU.bmp > F-15-CDU.tga F-15-FUEL.bmp > F-15-FUEL.tga F-15-HUD-CONTR.bmp > F-15-HUD-CONTR.tga F-15-INSTR-11.bmp > F-15-BKUP-GYRO.bmp F-15-INSTR-11N.bmp > F-15-BKUP-GYRO-N.bmp F-15-KNOPKI.tga > F-15-HSI-RING.tga F-15-KNOPKI-N.tga > F-15-HSI-RING-N.tga F-15-MPCD-DISPL.bmp > F-15-MPCD-DISPL.tga F-15-PRIBORY-2.bmp > F-15-PRIBORY-2.tga F-15-PRIBORY-8.bmp > F-15-HUD-FRAME.tga F-15-GLASS.tga > F-15-HUD-EDGE.tga F-15-PEREPLET.bmp > F-15-PEREPLET.tga F-15-RADAR.bmp > F-15-RADAR.tga F-15-SPEED.bmp > F-15-SPEED.tga F-15-TEWS.bmp > F-15-TEWS.tga ILS-REFLECTION.tga > F-15-HUD-GLASS.tga KOMPAS-PLASHKA-MIG.bmp > F-15-COMPASS.bmp KOMPAS-PLASHKA-MIG-N.bmp > F-15-COMPASS-N.bmp ZERRKALA-BLIK.tga > F-15-MIRROR.tga

The Lock Altitude command is a not-best-translated Radar Altitude setting. The unit will adjust altitude to follow the contours of the terrain.

Thanks for that sample mission Einstein. I found my problem. I think the main problem was that I had the Task set to 'Pinpoint Strike'. I changed it to 'Ground Attack' and then it started working. I was able to put payloads on both wings and also in the bombbay. And I also put an OSA SA-8 at the target, and it still dropped it's bombs just fine. I had the waypoints set to about 6000 meters, but in the game it said the flight was at about 16,000 feet, so I think the actual flight was lower than 6000 for some reason. When I told it to 'Lock Altitude' at the first waypoint, it would dive down a little at the second waypoint, so it must want to be lower to bomb. So, I reset the waypoint to just 'Turning Point' and let it start at the altitude it wanted. Thanks for all your help!

Once you have made a payload and added it to some aircrafts you should not edit it. If you need a different payload make a copy of it and then make changes to the new one. Then you apply that payload to all the aircrafts. (HJ)