Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/11/09 in Posts

  1. DOWNLOAD This skin is based on Slovakia's digital camouflage paint scheme implemented on their Mig-29's. It's my first real skin for BS, so forgive me for any hickups. File is ready to be installed with Modman, headache free. Instructions are in the readme. Background These images of a real Slovak Mig-29 with the digital camo paint job were my reference/inspiration. More: http://img512.imageshack.us/img512/9941/mig29gooddigikf2.jpg http://www.hyperstealth.com/Mig29/index.html http://www.defenseindustrydaily.com/Digital-Thunder-Camo-for-Slovakias-MiG-29s-04814/ Screenshots Where's waldo? (alright its not that good :P ) *Final version features small black tail numbers instead of large side numbering.
    3 points
  2. Hello ladies and gents, I have added all default keyboard shortcuts to the cockpit tooltips. The file can be found here. Since a lot of people might skip the readme file in there, I am posting it here too. Enjoy! WARNING: This was only tested with the English release of DCS: BS, version 1.0, with the option COCKPIT LANGUAGE set to English. I cannot guarantee it will work with the Russian release, or that it will work with the English release with COCKPIT LANGUAGE set to Russian. OVERVIEW ------------------------------------------------------------------- This readme is organized in the following fashion: - INTRODUCTION - HOW TO MODIFY TOOLTIPS YOURSELF - EXISTING ISSUES - INSTALLATION INSTRUCTIONS - CONTACT INTRODUCTION ------------------------------------------------------------------- Hello and welcome to the world of tooltips! The files in this download were created to add the default keyboard shortcuts to the in-cockpit tooltips that DCS: Black Shark is capable of showing. The reason I decided to do this was simple. I do not own a HOTAS setup (or at least, not yet), and am therefore forced to either use the mouse to click through the cockpit, which I like quite a bit, or to use keyboard shortcuts. For the vast majority of the time I spend in the cockpit, I use my mouse pointer to click on things, but I find that sometimes, especially in the heat of battle, I do not have the time to look around for a switch, never mind move the pointer over it and click it. For these moments, I wanted to learn some of the existing keyboard commands. In reading through the DCS: Black Shark forums (http://forums.eagle.ru/forumdisplay.php?f=72) I bumped onto a message where someone suggested it would be great if keyboard shortcuts were added to tooltips, so i set out to see if it was possible, and the rest is, as they say, history. Here we are. When I polled the members at that forum to see if anyone else would be interested, I got some very positive feedback, and so decided to make this public. At the same time, though, some people brought up really good points and ideas. One of the good points was basically "Well, if the tooltip only shows when your mouse button is over a switch or knob, then what good would this be? Just click on it already!". That's very very true. The intention of this package is not to move your cursor over a switch, read the keyboard shortcut, then use that. It is to help memorize what that shortcut is, so that after several usages of the same switch, by seeing the key combo repeatedly, you will recall it from memory. So, I guess you could see this as a study guide. HOW TO MODIFY TOOLTIPS YOURSELF ------------------------------------------------------------------- I do not intend for this to be a closed effort, and welcome help and questions at any time. I am also showing everyone how they can customize their own tooltips for the benefit of the community. Black Shark itself has a very open architecture, and so in that same spirit, here's how to do this editing. All cockpit tooltips live in a file called clickabledata.lua. This is a text file, written in the lua scripting language (http://www.lua.org). If you are not familiar with editing lua files you should proceed with caution. Information and tips on editing lua files can be found on the above referenced forum in threads such as this: http://forums.eagle.ru/showthread.php?t=35627&highlight=editing+lua First things first: Make a backup of your original file. Copy it to anywhere in your computer you will remember, or keep it in the same directory under a different name. Either way, you need a backup copy because it is not hard to change things by accident and break some or all functionality of DCS: Black Shark. I use Notepad++ to edit them, as the default Windows Notepad will corrupt such files when saving them. Using a proper text editor program, open up clickabledata.lua, which is located at ....\Eagle Dynamics\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit. The first 13 lines or so are default information. The data we are interested in starts at around line 15. In my file, lines 14 and 15 are: -------------------------------------------------------------------------------- -- CPT MECH This is a section header used to organize this lua file into chunks. Each tooltip is on a line of its own. Look right after these two lines, on line 16, and you'll find our first tooltip, in the following format: elements["GEAR-PTR"] = {class = {class_type.TUMB,class_type.TUMB}, hint = LOCALIZE("Gear lever (G)"), device = devices.CPT_MECH, action = {device_commands.Button_1,device_commands.Button_1}, arg = {65,65}, arg_value = {direction*1.0,-direction*1.0}, arg_lim = {{0.0, 1.0},{0.0, 1.0}}, updatable = true, use_OBB = true} As you can tell, this file does more than identify tooltips, but we're not interested in the extra info, all we are looking for is the text inside the quotes, right after the "LOCALIZE" tag. In the above case, it is the following: "Gear lever (G)" The text within these quotes, also referred to as a string, is what will show in the tooltips in the simulation. You can write pretty much anything you want, although some characters are treated differently by lua. For example, if you wanted to print a percent sign, %, you cannot simply add that sign, as lua will recognize it as an operator. What you have to do here is to "escape" that character. This is a programming technique that consists of simply prefixing the special character with an "escape" command. In lua, that escape command is the backslash, \, so in our previous example, if you wanted to add a percent sign to the tooltip right after the word "Gear" you'd simply write it like this: "Gear \% lever (G)" lua has a list of special characters that would need this escaping technique when used in a string. Here they are: " ' [ ] % \ You may be thinking "Wait a second, one of those special characters is the backslash itself!". Yep, that's right. Why? Well, easy enough, what if you wanted to print a backslash into a string? Simple. Like all other special characters above, just preface it with a blackslash. So, if we wanted to add a backslash in between the words "Gear" and "lever", we'd do the following: "Gear \\ lever (G)" If all of this is not making sense, take a look at the lua website I mentioned above, and read around in the forum. Let's continue. If you are looking for a specific tooltip, you can search this lua file with your editor's search function for some keywords, or scroll down through it looking for the proper section. Once you have located it, change the text inside the quotes right after LOCALIZE, save the file, and you're ready to go. EXISTING ISSUES ------------------------------------------------------------------- I ran into a couple of decisions during this effort, as well as some limitations. They are/were as follows: 1 - To avoid confusion I did not use "-" or "=" in between key presses, such as "LShift + G", since sometimes keyboard commands involve the signs "+" or "-". Key presses are simply separated by a space, so the previous example would be "LShift G". 2 - Brackets (either [ or ]) seem to be a problem. In lua, you can "escape" a bracket inside a string or, in other words, tell lua the bracket is not part of opening or closing an array, and is just to be printed as text, by prefixing it with a backslash (see HOW TO MODIFY TOOLTIPS YOURSELF above). I have tried this and still get what looks to be just the upper part of a bracket once in the tooltip. It could be due to my resolution, video card, video drivers, BS itself, or all of the above. If you can resolve this issue, or if you don't have issues at all, please let me know. In my testing, it seems that prefacing a bracket with a backslash did not make any difference, they printed the same way on screen with or without backslashes. Just in case, every bracket I used in tooltips has been prefixed by a backslash. 3 - I could not find keyboard shortcuts for the following, some due to the fact they are "No Function" switches and probably do not have shortcuts. If you know them, please contact me. WALL PANEL - Radio equipment datalink SA-TLF power switch - 1st fire warning sensors group BIT - 2nd fire warning sensors group BIT - 3rd fire warning sensors group BIT - Reducing gear box oil pressure indication selector - Sling load Auto/Manual - Latitude selection rotaty (it is misspelled as "rotaty") - North/South latitude selection FORWARD PANEL - SHKVAL Optics adjustment AUXILIARY PANEL - ATGM Temperature selector - Unguided rocket and gun pods ballistics data settings selector - Systems BIT selector - Control computers BIT switch - Self test system push-button - Emergency INU alignment switch - Stabilisation and indication of hanger cable switch - Video Tape Recorder switch OVERHEAD PANEL - Windshield washer fluid switch - Brightness 4 - For rotating knobs that had two different keyboard shortcuts, one to rotate clockwise, the other to rotate counterclockwise, yet only one tooltip, I added both commands to the same tooltip. I prefaced the clockwise rotation shortcut with the letters "CW", and the counterclockwise one with the letters "CCW", or "DECR" and "INCR" for knobs that decreased or increased settings such as brightness, or "DOWN" and "UP" for rotaries with such motion. 5 - I did not have time to test all keyboard shortcuts. If you find any mistakes, please contact me. INSTALLATION INSTRUCTIONS ------------------------------------------------------------------- 1 - Backup (or move to another directory) your original clickabledata.lua, located at ....\Eagle Dynamics\Ka-50\Scripts\Aircrafts\Ka-50\Cockpit 2 - Replace it with the clickabledata.lua file from this package 3 - Make sure that in DCS: Black Shark, under OPTIONS | GAMEPLAY you have TOOL TIPS checked on CONTACT ------------------------------------------------------------------- You can contact me at fabiomiguez@gmail.com Enjoy learning these keyboard shorcuts! Best regards, Fabio Miguez
    2 points
  3. You can have rep just for your Tornado quest, keep it up. And don't let the boo boys put you down.
    2 points
  4. Два года игра работала нормально, но вот купил новый компьютер с лицензионной Windows Vista, и игра теперь не устанавливается - при запуске установки немедленно требует Диск №2, вставляю диск №2 - всё равно тупо его требует (при этом даже к приводу компакт-дисков не обращается!). Скопировал содержимое обоих дисков во временную папку на другом разделе, первый диск оставил в приводе, запустил установку с винчестера. Вроде бы встала, но после перезагрузки Vista сообщила, что ей не нравится Star Force. Ну я подумал, что без патча 1.12b тут не обойтись, и установил его. Перезагрузился. Windows cнова ругается, ей и этот драйвер не подошёл. В общем, потренировавшись ещё некоторое время, я проблему решил. Просто поставил и на новый комп Windows XP, и всё снова работает. Однако, я не думаю, что такой вариант всем подходит. Разработчики, я вас вспоминал. Нехорошо о вас думал, очень нехорошо. Всё у нас пишется вот так - то левой рукой, то левой ногой. Потому так и живём.
    2 points
  5. I knew that in DCS: Black Shark Version 1.0 trees would be fly/drive/shoot-through and see-through for AI units and sensors. I knew it because ED were so kind to announce it beforehand and I thought: ok, no big deal, if they have their reasons and they feel they can release without tree collision model and sensor blocking then I can live with it as well. I was wrong. I´ve got BS on my harddrive for less than 2 weeks and already after only around 25 hours in pit I have to admit: I´ve got (tree) issues. The :doh:-thought occurrs to me in each and every mission I flew so far: - My Shkval shouldn´t be able to continue tracking that BTR disappearing into the woods. - That BTR shouldn´t be able to continue straight ahead at 50 km/h through the dense forrest. - My Vikhr shouldn´t be able to reach it, nor my designating laser. - The AA units in the middle of the forrest he was racing towards shouldn´t be able to see, sense, lock, track and shoot upon me with neither shell nor missile at a near horizontal angle through +200 m thick woods. - A multiplayer opponent shouldn´t be able to hide from my view inside a tree or race literally through vegetation. Helicopter combat is about hide and seek; the skilled pilot who is able to sneak up on his target by hopping from clearing to clearing, by sideslipping into a new position for a well-timed pop-up, he should be rewarded. In the current release of BS it is even worse than if there were no trees at all: everybody sees you while you cannot see them. With this I have found a huge dent in my perception of this in many other ways awesome piece of software. Huge enough that I have to vent it here in public and that I feel the quality of the simulation would more than double with this single issue fixed. I am not seeking nor expecting any explanations from anyone. I can imagine myself a huge number of reasons why things are as they are and I don´t want to start a time-wasting speculation. I also don´t ask for any information about future proceedings on this issue. I guess I´m not telling anything new to those in charge, nevertheless, please still regard this posting as constructive criticism. Forgive my rant, I just felt the urge to voice my opinion, to make sure nobody felt the current state was "ok"... Kind regards, Woody
    1 point
  6. Speaking of the patch 1.13, I finally figured out what's wrong with the missile performance in FC and found the source that ED's programmers used to design the guidance systems: http://www.crc-mindreader.de/FC/MSL_Guidance.wav
    1 point
  7. Excellent idea, making a seperate mission. One thing to keep in mind: If you use the in-game malfunctions, it actually causes an engine fire, and does not simply shut down the engine. The first fire bottle will fire automatically and put out your first engine, and you can keep flying. When the second engine fails, the second fire bottle will have to be fired manually. So after the first failure, once you get things under control (i.e. fire out, which should be automatic, shut off the failed engine fuel cutoff lever, increase throttles to EMERGENCY, and make sure you don't crash in the process), you should switch your fire bottle switch over to your alternate fire bottle, and when the second engine fails, you will have to click the failed engines fire button to put it ou, plus cut off the fuel lever, plus drop your collective and begin your autorotation. (You could probably skip the fuel lever, but in real life that absolutely needs to happen so you are not feeding fuel to a hot engine that was just on fire.)
    1 point
  8. Hi geogob, A better way to practice would be to create your own mission with both engines set to fail in between 5 and 10 minutes, for example. that would give you enough time to get in the air, start moving somewhere, but not know exactly when the engines would fail. It creates a little more realism for this scenario.
    1 point
  9. Хотелось бы иметь возможность отмены соединения к серверу:music_whistling:
    1 point
  10. Некоторые "побочные" результаты экспериментов с шейдером НВ: Все таки просто так в симах ничего не дается, при использовании увеличенной яркости ОВН пропадает возможность регулировать яркость в игре :)
    1 point
  11. Can anyone confirm that the Modman version works with no issues?
    1 point
  12. Thanks for making my Russian speech understandable. ))
    1 point
  13. The laser rangefinder operation is limited to five series of uses, with 30 minute intervals between them. Each series gives you 16 lasings of up to 10 seconds, with 5 second intervals between lasings. If you use the LRF more than this, you will damage it.
    1 point
  14. I wish I had seen your comments before I repped you. As a PROUD veteran of the Uniform of the United States- An opportunity to beat the snot out of you face to face is lacking- But I can fix the "rep" mistake. :mad:
    1 point
  15. If your game directoy includes any space characters, like in your case "program files" and "eagle dynamics" it doesnt work. I had the same problem and tried to rename the folders, but it wouldnt let me. So i copied the whole game to a new directory without any space characters and now it works.
    1 point
  16. Just switching your radio to "ground crew" doesn't allow you to talk to them in real life until they plug into the aircraft. The game simulates this by assuming that when that switch is in the ground crew position, the ground crew have their headsets plugged into the aircraft. They are yelling at you because to get them to unplug, you need to switch the radio back away from ground crew, which is the game's way of simulating them unplugging and moving away. At least that's my take on it. ;)
    1 point
  17. Hope they get rid of them bulluts before they bring the Tornado as a flyable on the scene! :P Mind you ... it calls into question how high fidelity DCS BS really is! As I hear it among my military contacts, info about bulluts is still highly classified ... so ED, where are you getting your modeling data, hey!? :D Cheers!
    1 point
  18. Ok. Though some issues are present with laser rangefinder, I may also say that: laser rangefinder has limitations: 5 series with intervals of 30 minutes; 16 cycles of 10 seconds with intervals of 5 seconds in each serie. You may be not following these rules in your flights (and make more range counts than it is possible) and this will result in not working rangefinder. Not a bug but a feature.
    1 point
  19. Товарищи. Вы совсем того. Был ЛОГС - все орали:"Ночи светлые слишком! Сделайте темнее!" Сделали темнее, появилась ЧА: "Ночи слишком темные, сделайте светлее!" Напоминает мне один всем известный форум и фанатов игры, в названии которой есть цифра 2.
    1 point
  20. Ну у мну была схожая, по ситуации, проблема, 2 года назад. Не со звуковухой - с довольно древним модемом (2002 года выпуска) (убер китаец - типа люцент :)). Тож писиайный, тож после переустановки ситемы перестал работать. Исследованиям причин помогло то что данный девайс использует мелкосовтовские дрова - так что несовместимость дров отпала сразу, плюс обширная мелкософтовская база знаний. Дык собака порыта в распределении ресурсов ( прерываний и окон памяти). Гыг знаменитая плуг-анд-плай (плуг-анд -прей-шоб заработало). Оказалось что в икспях ресурсы выделяются дважды - первый раз, собственно вне икспей - биосом, второй раз уже икспями при загрузке. Дык у мелкософта довольно путано написано - но в одном месте указано что икспи хотя и читают то что распределил биос - пересраспределяют по-новой. Собственно у мну так и происходило - модем перебрасывался икспей на верхние прерывания причем попадал в расшарку (совместное использование прерывания) с USB контроллером. Дык если в усби ни чего не было воткнуто, то модем просто не работал, стоило воткнуть джой - срузу получал "синий экран смерти". Глубинные эксперементы показали что первое, биосовское, распределение ресурсов в модеме занимало длительное время (скорее всего так и не завершались полностью) к моменту начала распределения ресурсов икспей. Мозги модема косило. Выход был найден просто элементарный - задержка запуска ОС - 30 секунд хватило - наверное в первое распределение заканчивалось по таймауту (граница была где-то 25-27). Так что мой свет посмотреть в устройствах что чему распределено и постараться (отключением ненужных устройств в биосе/виндах) высвободить прерывание звуковухи на отдельное прерывание. Еще один способ воздействия сменить прерывание - разные слоты писиайа могут давать разные прерывания - хотя конечно биос может тупо всегда сажать звуковуху на 10е (в расшарку с сетевухой). Обычно в документации к мамаше указывают кокому слоту какое прерывание будет выделено. Здесь важен другой аспект икспя изменит порядок обхода при выделении ресурсов. У мну тоже такой финт работал но не стабильно - раз на раз не приходилось. Ну и кординальный подход - использовать MyJoy16 как переходник (те присабачить гейм порт а из него вывести оси и кнопки). Собственно счас данный девайс встанет рублей в 500 на все про все, но естественно надоть уметь работать паяльником, правда, достаточно лишь легкого знакомства с данным инструментом. Достаточно вразумительно-полная инструкция http://www.joysticks.ru/joysticks/samodel/25.shtml Неск замечаний. 1- для печати рисунка платы лудше использовать рисунок-исходник в векторном формате. Пиксельный не гаранитирует полной идентичности. Так что я испльзовал референсную разводку из MJoy16_v1.pdf - просто распечатал страницу из файла (предварительно выствавив/проверив в настройках печати акробата отсутствие масштабирования). Мини варианты из статьи - у мну не пошли - они пиксельные. Хотя конечно можно их перерисовать в векторный формат - например в MS Visio. 2- перенос рисунка - впринципе все правильно. Ток конкретнее - порошки лазерников разные - соответственно и температура плавления может быть разная. Толщина бумаги тож (глянцевые жруналы самое то). У моего принтера/порошка надо 3 деления на утеге и довольно сильно вжаривать. Еще варианты оживления старичков через уэсби http://www.obdev.at/products/avrusb/prjhid.html
    1 point
  21. Мде... Камрады, а с каких пор отменили светомаскировку в военное время?
    1 point
  22. "and of course be able to run DCS:BS quite decent." I currently building a new machine & discovering that for just a little more monitary output you can get a lot more without breaking the bank. Trying to save money on your initial build almost always costs a lot more. Especially when you get your new puter running & find yourself turning everything down to lowest settings, which was probably not the point of spending all that money. 1: E8500 is a great processor @ 3.16 Ghz & cheap at the moment. Read other posts & you will soon realize BS is CPU (Ghz) dependant. You can go cheaper & OC if you are confident with that sort of thing. I am not sure about AMD stuff, just get the fastest (Ghz) you can afford in Dual core. 2: min 2 GB 800 3: as far as I am aware the 9600 series are not really meant for gaming, they are a low budget card for low performance applications. Most people here seem to use the 8800 series quite happily and these are at a reasonable price as well. 4: your choice, some have mentioned a FPS improvement with vista using multiple cores. 5: Re-read post by okolovos I am not sure if your prices are from retail shop or internet, but shop around, especially Ebay. It is easier $$ (psychologically harder) to get the parts slowly as you can afford them, & you end up with a higher quality build that WILL run BS & other games "Quite Decent". Spend some time doing the research, It costs nothing & will save you wasting money. You also learn a lot about the all different components & how they go together which is great for getting value for money & a few extra FPS while you are at it. My friends of the 169th_Panthers have a few good articles here: http://169thpanthers.com.au/forum/viewforum.php?f=22&sid=eb718a122d1e5151c2d8150965322c6c Cheers, Rastus.
    1 point
  23. thanks for the help guys, the ones who actually tried to help.to the others,apparently I have to scan a manual constantly for one obscure reference which isnt in the manuals index.If I could have found it in the manual I wouldnt have posted here. Duh. Thanks for that advice ., Never thought of reading the manual. And I cant ask for help in more than one place. That would be awful. hope someone can be as helpful for you in the future.
    1 point
  24. To get a sense out of that kind of cockpit is good. It is one of this types of the screen shots that is good with this sim and it’s exiting in it’s own way.
    1 point
  25. You know, I ran into it by mistake while looking for more info on the HDR mod that I use with Black Shark....Well it turns out that some games have the same problem with clouds.... specifically I believe it was GTA3 or GTA 4.
    1 point
  26. Another crosspost. I hate it. http://simhq.com/forum/ubbthreads.php/topics/2650175/do_wiper_blades_on_the_Shkval_.html#Post2650175 Especially when the question was already answered.
    1 point
  27. OK, I've updated my last post to include the results at 3.96 GHz with Windows 7! I can upload the track I used if you would like to compare to my data. Keep in mind this is just how *I* benchmarked - anyone else's data is from something different. To compare to my data, use FRAPS (etc) to generate benchmark data between the instant the switch is flipped to turn on the helmet mounted sight, and then stop capturing 8:00 minutes later. All settings were posted back in Post 24 for driver level settings and in game settings unless specified changed for an individual run. Here is the trackfile I used: http://www.megaupload.com/?d=VRED889L
    1 point
  28. I'll stick a couple of links on then, i'm the sort of person who reads it all thoroughly though, you might want to find something a bit less mindnumbing that doesn't waffle on lol http://www.tomshardware.co.uk/forum/240001-11-howto-overclock-quads-duals-guide http://www.clunk.org.uk/forums/overclocking/2-c2d-overclocking-guide-beginners-p5k-add.html I use CPU-z, Real Temp, and HWMonitor (sounds the same as Speedfan). I by no means mean to patronise anyone, I just never found a decent explanation of what overclocking actually was. All the stuff about RAM ratio's etc. got me thinking it was really complex (which it can be), but it in theory can be very simple. Here's an explanation of what Overclocking is: THIS IS NOT A GUIDE, lol - You can kill almost everything on your mobo if you don't know what you're doing. The aim is basically to make your FSB as large as possible whilst keeping your temperatures under 65C. The Front Side Bus can be any number you want to enter in the BIOS, and each CPU uses a 'Multi' (Multiplier). Mine and SunDogs' E8500's have a multiplayer of 9.5x. This means that if my FSB is set to 333, the CPU will output 333x9.5 which equals.. 3163.5 That number is the speed the processor is running - FSB is measured in MHz, so.. 3163.5MHz = 3.16GHz - the stock speed of our e8500! To overclock it, it's easy. Just find the FSB box in the BIOS and stick a new number in. If I enter 400[MHz], it will give me a speed of 3.800GHz - simple! This extra processing needs extra power (Volts), and this is where it gets interesting[..ish]. To make the processor stable you will need to increase the Voltage to it. This is also done in the BIOS by simply entering the desired number into the CPU Voltage box. Stock Voltage for my e8500 was 1.2500v. To run at 3.8GHz stable, I needed to raise this to 1.2700v. Simple as that! Now this extra Voltage will create extra heat (hence SunDog getting a big fancy cooler!). Another thing is that there are other voltages (exaple: for the NorthBridge). Same principle here too, the voltage will need to be raised in order for it keep up and run with stability. Exactly as with the CPU, more volts will make the component hotter, so you may need to buy a new Heatsink, same as SunDog did for the CPU. Now the system has been overclocked and the voltages have been raised. However.. Increasing that FSB changed your RAM speed. RAM has a maximum speed at which it can run. SunDog has 800MHz RAM. This means that he needs to make sure that he keeps his FSB under 400. This is the 'Dual Data Rate' part of the ram - 400MHz FSB x 2[it's dual] = 800MHz! If SunDog went over 800MHz he would then be overclocking his RAM. So now we've got my e8500 to 3.8GHz, running stable, with my CPU using 1.2700v, and my NorthBridge using 1.300V. This is creating more heat, which is handled by my new heatsinks and fans. The only job now is to get the voltages as low as possible, so that the system will run as cool as it can! Finished, we're overclocked and [very importantly] stable! Like I said, wish someone had written that BEFORE I took 5 pages of notes! THATS NOT A GUIDE > it's an explanation! Hope that helped someone who wasn't entirely sure what overclocking is all about. Most of the numbers used are off the top of my head and won't be correct, and i'm certainly no expert, so I may be wrong! But anyway, hopefully might help someone understand the overclocking guides better. mike
    1 point
  29. See my second half of response above ... .
    1 point
  30. Как и предупреждали ребята ..чуть что "пишите свои миссии".. ,это связанно с какими-то техническими трудностями ? Может времени не хватает ? Тяжело или элементарно не хочется ? Без обид
    1 point
  31. :megalol: MSFS, LO, Il2, Ka-50 - это по Вашему не современные и не интересные авиасимуляторы? :thumbup: Вот ведь, и джойстики тоже не популярны :D Так значит джойстики пылятся на складах, у производителей кризис сбыта? Только Comanche 3 при всей великолепности игрушки был кнопочной аркадой и джойстик там был необязателен. Кстати NovaLogic выпустил нечто аля Comanche 3 - Comanche 4 уже вышел. Лет восемь назад. :) То есть не аркада, а симулятор? А ЧА под это определение не подходит? Именно для MS Flight Simulator был создан MS Sidewinder и никакого отношения к аркадам он не имеет. Те, кто играет в аркады не станет покупать дорогой девайс. А чаще всего и дешевый не станет. Нет нужды. Какие либо требования к игровым устройствам предъявляют как раз злостные симеры. И именно для них появляются такие устройства как Hotas Cougar например. Хорошие рули, такие как МОМО, или Г25 появляются для таких симуляторов как GTR, r-factor. RBR изначально не имеет поддержки FF. А мегапопулярные аркады типа Grid или Dirt руля не то что не требуют, он там противопоказан...
    1 point
  32. Actually I see quite a bit of potential for professionally done 3rd party flyables (payable). Not necessary combat planes, but relatively simple combat support or transport aircraft. For example the OV-10 A-FAC is not too complex and would fit nicely in the DCS world.
    1 point
  33. ну я так и понял, но все равно стрелку героя надо дать:D вот еще забавный вид из кокпита он же с наружи)
    1 point
  34. http://forums.eagle.ru/showthread.php?t=36605
    1 point
  35. Windows 7 preliminary testing Windows 7 Preliminary testing in BlackShark has some very interesting results! Remember the run I posted above for 3.06 GHz? Well, no need to go look up there for it. . .here it is: Windows XP E8400 @ 3.06 GHz (speedstep enabled) DX9.0c 2x1Gigs of PC8000 RAM at 850Mhz, 8800GTS (G92) at stock clocks 178.24 drivers Frames: 16232 - Time: 480193ms - Avg: 33.803 - Min: 5 - Max: 61 The following is the same run, but in Windows 7 (64 bit), with DirectX11, all other settings the same ( more than 2 gigs of RAM doesn't appear to make a difference in BS): Windows7 core 0 E8400 @ 3.06 GHz (speedstep enable) D11 2x2gigs PC8500 at 850Mhz, 8800GTS (G92) at stock clocks 178.24 drivers Frames: 13802 - Time: 480225ms - Avg: 28.740 - Min: 7 - Max: 60 So that's not so great. . .at this point it's not looking very good for Windows 7. . .but it's supposed to run like a better version of Vista, which supposedly is strong in Black Shark. . .so what gives? Ahhh, the CPU affinity trick you say?? Well, lets see if that makes up the lost performance! For this run, settings are the same, only I enable both CPU cores in the taskmanager: Windows7 core 0+1 core E8400 @ 3.06 GHz (speedstep enabled) DX11 2x2gigs PC8500 at 850Mhz, 8800GTS (G92) at stock clocks 178.24 drivers Frames: 21729 - Time: 480340ms - Avg: 45.236 - Min: 23 - Max: 62 So umm. . . can you say AWESOME?!??!!!?! Not only did I get the lost performance back, but I set something of a record for this benchmark on my machine! If you take a look at my previously posted Windows XP run at the same settings the best I managed was - Avg: 42.185 - Min: 10 - Max: 62 and that was overclocked to 3.9 GHz!!!!!! Even my runs at 3.960GHz with 2x2Gigs of PC8500 RAM at 1100MHz, only averaged: 44.439fps in XP. . .so simply running Windows 7, and using both CPU cores gave me .8 avg fps better performance at a stock 3.06 Ghz than at nearly 4.0 GHz in 32 bit Windows XP!! I can't wait to see what it does at 3.96 GHz!!! Well, yeah I can, I need to sleep now that it's 6:30 am!!!! :music_whistling: [Edit to add the results from the 3.96 GHz runs] Windows XP 32 E8400 @ 3.960GHz 2x2Gigs of PC8500 RAM at 1100MHz, 8800GTS (G92) at stock clocks vSynch and triple buff on on 178.24 drivers Frames: 21281 - Time: 480107ms - Avg: 44.439 - Min: 10 - Max: 63 Windows7 (64) core 0+1 E8400 @ 3.960GHz 2x2Gigs of PC8500 RAM at 1100MHz, 8800GTS (G92) at stock clocks 178.24 drivers vSynch ON Frames: 26647 - Time: 480074ms - Avg: 55.506 - Min: 27 - Max: 62 Windows7 (64) core 0+1 E8400 @ 3.960GHz 2x2Gigs of PC8500 RAM at 1100MHz, 8800GTS (G92) at stock clocks 178.24 drivers vSynch OFF Frames: 28235 - Time: 479994ms - Avg: 58.823 - Min: 32 - Max: 93 Impressive results no? Under the same conditions I had an increase of 11.1 frames per second better on average when overclocked to 3.96 1100MHz DDR2, and 14.4 frames per second better when vSynch and triple buffering are forced off in the driver control panel (the normal way in which benchmarks are run). Perhaps most impressive is the minimum fps. . .they are almost as good as the average fps at stock clocks!!!! My track really killed the fps in a flew places on XP, but with 7, and both CPU cores, that's gone!!!!! Also, I am using drivers that are not technically compatible with WIndows 7 in the interest of running the same driver as I'd used previously. Next I'll try the driver MS suggests, and perhaps the 185 series beta that shows big gains in many titles.
    1 point
  36. Memory speed and latency hardly effect performance in any app or game. You only need memory that is fast enough to support your FSB. So if you have a CPU with a 1333 FSB rating, you get 333FSB or DDR2-1333 memory. But if you want to overclock that CPU to 400FSB, you need DDR2-1600. FSB x 4 = DDR2 rating and CPU 'FSB' for the S775 systems. Not sure about AMD. The Core i7 is x8. Its about the CPU not the memory. So conversely if the Mobo supports 1333, its supports a CPU that has a default FSB of 1333 like E8400. If you only get MoBo that supports DDR2-800 memory, Then you can only use a CPU such as teh E4600 or the C2D Celerons. It has been proven time and again. Only benchers need 'fast' memory. Its may help a few seconds in some hour long coding/encoding/ripping.
    1 point
  37. I dont know where else to do this so Ill say here. I would like to ask my governments military to please contribute a charity contribution to the flight sim community of ONE MILLION DOLLARS TO EAGLE DYNAMICS. This money shall be used to further the develoment of LOMAC...ONLY. Allowing ED to concentrate on their future. This is not a waste of money. However it is not for many. It is for the few and the proud ED supporters and admirers. We love you all!! Respectfully, a US citizen.
    1 point
  38. Yes ... I noticed this too! I got a few bad reps once ... and I know beyond a shadow of a doubt that there was nothing but PURE LOVE in them thar hearts :D. Cheers!
    1 point
  39. 1.AMD 64x2 5600 2.2 gig ram (later is easy to upgrade to more if need. 3.none of these cards i used ever so dunno. 4.vista premium 5.Psu you should pick carefully with good name behind it. dont go cheap on this one regardless of wattage ( go for brand name even if more expensive with less W) And motherboard???? You don't need one?
    1 point
  40. Убрать ботам сорбции, всех делов )
    1 point
  41. nicely done !!! like it a lot - music is cool too thanks for posting rep inbound ! cheers mate
    1 point
  42. yeah grey indicates they have not yet accumulated any rep value themselves to pass on. Here Prophet- I'll see if I can offset some of the mistakes.. :) EDIT.. whoops I can't.. Seems I gave you some recently..
    1 point
  43. Red is bad. Black is null point i think.
    1 point
  44. Interesting. I hadn't even looked at the load across the cores. I'll play around and see what I get with different delays.
    1 point
  45. Надо сказать и о минусах. Главный минус, самый весомый минус – это цена. Стоят они примерно как Thrustmaster HOTAS Cougar. Что бы еще придумать, попридираться для приличия? Шнур USB коротковат и белый. Я хочу черный. Правда, он съемный – можно заменить. Нет блестящего корпуса :lol: . Не очень удобно пользоваться конфигуратором. Отсутствует инструкция. Однако разработчики обещали в будущем сделать программный интерфейс для конфигуратора. А инструкция уже готова. Отсутствие корпуса как такового скорее плюс, чем минус. Педали можно легко смонтировать на своем основании, что оценят кокпитостроители. Все.
    1 point
  46. IMHO, 'Collidable' trees in BS are a bit like missiles that obey physics in FC ... pretty fundamental! Watching TOW missiles fly through forrests and hit a BMP ... just looks silly. There are dozens of videos showing attack helicopters skirting along tree lined roads/rivers etc ... NOE is again fundamental. Afg/Irq are not conventional environments and I'm sure what is considered convention attack helicopter is different there. Against a mech army with lots of AAA/SAMs you'd have to either neutalise (SEAD/ECM) it or go low into the trees. I guess we await the new engine ...
    1 point
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...