Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/22/09 in all areas

  1. I know there are several other quality checklists out there, but I've been working on mine for a while and thought I'd throw it out here to see if anyone else finds it useful. This document is a work in progress, but the start-up checklists should be pretty solid. Below is a list of items I'm still working on. Performance data/reference Autopilot operation reference Additional Emergency cards (in-flight fire, etc.) Weapons Employment reference (Vikhr, etc.) Mission briefing template I know folks on this forum aren't very open about their opinions:megalol: but your feedback would be very much appreciated, positive and especially negative. Feel free to post them here or PM me with your suggestions and criticism. FM-Ka50-CL-H5.pdf
    6 points
  2. Attached is my somewhat generic solution for export/import to SIOC / OpenCockpits cards. Some knowledge of programming is needed to make the scripts work. General idea has been to keep most of the complicated stuff out of Export.lua and into a bunch of support functions + definition files to make it easier for myself and other to connect the appropriate switches, LED's etc to their simulated counterparts. This version supports: Inputs with specific function calls for each SIOC parameter. Comes with ready made functions for "two position switches" and "rotaries". Simple on/off indicator output, cockpit LEDs, warning lamps etc. Usage: Install by unpacking and overwrite into the Export directory of DSC:BS. Note: Make a backup. Configure you SIOC server host ip and port in siocConfig.lua Configure your inputs/outputs in the appropriate files in the SIOCConfig directory. Configure the options in the USER SETUP SECTION of Export.lua This section needs to match the files etc in the SIOCCONFIG directory. Future work: Add support for rotary encoders. Add support for instruments (altimeter etc) Add support for selected weapon. Add support for Nav system display Enjoy:thumbup: Thanks to PanelBuilder for the help. /Oakes Update: I've created a Google Project to keep tabs on the code for the scripts. Future releases will be posted there. http://code.google.com/p/dcsbsexport/ If you want access to the code you can 1. use http://tortoisesvn.tigris.org/ for simple export to your computer 2. you can download complete releases from http://code.google.com/p/dcsbsexport/downloads/list 3. You can download individual files from the repository via the source code browser http://code.google.com/p/dcsbsexport/source/browse/ (click on the file and then right click on the "View raw" link). /Oakes Export_0_90_beta.zip
    2 points
  3. шиворот на выворот ручки катапульты
    1 point
  4. ............Pirates of the Crimean........... ...............................................................
    1 point
  5. We're back for real this time.... I'll cross my fingers anyway--here is to more than 48hrs.... :D I'm sure Viper will come up with a neat new picture! :P IP: 64.87.10.166:10308 Intel E6400 @ 2.13 2 Gig's RAM Windows Vista Business x86 10Mbit up/down
    1 point
  6. Yeah, in BS, as far as I know SF only checks if your activation is valid when you start it, and then it functions normally - there is no disk check and therefore no drivers. I would say this is a lot - if you have BS crash logs, please upload them to the forum. They should be in the temp folder in the DCS folder. Yeah. I heard is has something to do with DX actually being sufficiently multi-threaded to deal with this - so the DX might split some threads off to the other core - I could be wrong, I don't remember well. But DCS was not specifically made multi-threaded. This will come in the (probably distant) future. My PC is very similar. Buy another hard drive and install win7 on it. :) You'll slowly migrate :)
    1 point
  7. That is if they are going against Su-35. The ground crews push that button, and it activates a system that jettisons wheels after take-off, instead of retracting them (since they won't be needed any more) :)
    1 point
  8. use flags. For each vehicle/group to reach the "goal" zone, set a specific individual flag. Set up a constant trigger to look for "Flag is true" for each vehicle combination..ie "if flag 5 is true and flag 6 is true and if flag 7 is true" then "mission = success". It will require quite a few trigger's to be set, but basic logic can be set up in this way. To cut down on combinations, I would use 4 or 5 groups of vehicles, and assign a Flag to the success of each group. If you assume 4 groups, then that is 16 possible combinations in total, of which 5 = a 75% success rate (1111, 0111, 1011, 1101,1110) and since "1111" is covered in the other 4, thats ony 4 constant triggers to test for ie: if (flag1 AND flag2 AND flag3) = mission success if (flag2 AND flag3 AND flag4) = mission success if (flag1 AND flag3 and flag4) = ..... and so on not perfect , as of course "Group in Zone" will be true whether it is 1 vehicle from the group, or all vehicles in the group, but still...extrapolate using bit logic (which is all flag values are used for), and go from there. and good luck! (it would be nice to have some more basic logic setup in the ME to test for! )
    1 point
  9. I'm sorry, but it's not that easy. Copy protections usually are made and sold by separate companies and bought to protect a game. In normal development the software is applied to the game just before it is going gold/being published. As ED/TFC probably doesn't even have full access to the copy-protection code, there is no way this protection is the same. Yes and no. 1. These settings are dangerous, but if you have programs which benefit from it, that's your own business. 2. I never said that your /3GB-switch is the cause of your crashes in BS. Infact I stated that from the very beginning. I just posted what it does and what risks come with it. Not more, not less. The opposite is the fact. Apparently during testing it was found that one campaign that came with the game ran slower on Vista, hence the recommendation. Once the game was released, though, it was pretty clear that there was a mistake in the games settings that made DCS run on one core only. Of course XP had the advantage as it is the lighter OS. After setting it manually to use 2 or more cores, though, Vista is tremendously faster since XP does not natively support multicore/multiprocessor-systems and barely benefits from running a program on more than one core. With the Patch 1.0.1 the limitation to one core has been corrected. You'll find dozens of threads here that performance boost going from XP to Vista/Win7 is between 70 and 120% (no matter wether it is 32bit Vista or 64bit, btw)
    1 point
  10. When A-10 comes along I wont look at the KA-50. Infact it has been a while since I touched it.
    1 point
  11. смотри сорри ВНЕШЭКОНОМБАНК
    1 point
  12. http://www.vtb.ru/rus/web.html?l=1 Баннер вверху или логотип самой странички, к примеру...
    1 point
  13. Name this plane. Picture from Google Maps. For topol-m:
    1 point
  14. Well if you boys are going to go hunting you might as well look good. May I suggest the Simmod A-10 model with the Live to Fly Fly to Kill skin pack you may enjoy it. http://www.lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=245&lid=1145&title=A-10A%20SIMMOD%20model#dldetails
    1 point
  15. Finally! :D Lol .. grats on a great "We're back" poster! ;)
    1 point
  • Recently Browsing   0 members

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