Jump to content

Vibora

3rd Party Developers
  • Posts

    8016
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Vibora

  1. If you don't get any answer from ED in the forum I suggest you open a ticket in the web page. When I asked ED they told me they would look at it.
  2. Fixed all. If someone needs the files, let me know.
  3. At San Javier AFB. At about 250-300 ft, start turn to crosswind, acceleranting towards optimum climb speed and keep that speed until you are at 1500 ft, which will happen most likely once you reach downwind, then accelerate to 250 kts. You shall keep max thrust untill starting the first turn to crosswind after take off, then reduce to MCT during the turn to crosswind or to be set at around 1000 ft. Once on downwinds and at 250 kts reduce power as needed to keep 250 kts. Reduce to 200 kts well in advance, as it's the max speed for gear extension. In a short runway maybe you'll need to keep just 200 kts during downwind.
  4. Fixed IFR Flight mission. EN version here. ES version here. If someone wants CN version please ask.
  5. Fixed Basic Visual Flight mission for now. Here you have it in EN version. Or here in ES version.
  6. Will correct it. Txs for the report.
  7. TOUCH AND GO 1-Throttle - MAX. 2-Airbrake – RETRACT AS THROTTLE IS ADVANCED. 3-With positive rate and altimeter: Gear – UP (Minimum 120 Kts) Flaps – UP ( Minimum 125 Kts) Spotlights – UP 4-Check correct indications for: Gear. Flap. Airbrake. Engine instruments. Hydraulic. Electric and fuel. Visual traffic pattern of the airport in question. Traffic pattern at San Javier Air Base is at 1500’ Speed 150 kts. On downwind, flaps takeoff and gear down. When turning to final, flaps down, make a descending turn to final. Reduce to final approach speed.
  8. We have reported it to ED.
  9. Sorry for my late answer. We will work on it later on. We are currently busy with other stuff.
  10. Gracias Paco :)
  11. We will next work on multicrew and only after that, weapons.
  12. We will next work on multicrew and only after that, weapons.
  13. Vibora

    Mirage F1

    Incredible cockpit! Congratulations to this guy. Could be interesting to get in contact with him.
  14. Did you read my message above? ED has to study it. That takes some time.
  15. You are right. We have been changing lighting but it seems it needs some more adjusting. We'll look at it. Thanks.
  16. We got no reaction time. The first time I saw a Syria map in DCS was two weeks ago. Will make a few missions.
  17. NS-430 itself is available in Steam, but not for specific modules like C-101, L-39 or Mi-8. ED will study that possibility.
  18. It is how it works IRL. I don't see why AOA indication could be a distraction. To me it's a very welcome flight parameter.
  19. Fixed, txs.
  20. Multicrew is much WIP, we will work on it soon.
  21. This refers to personal mappings in saved games, not to default mapping that comes with the module.
  22. Hi all. After Open Beta update 2.5.6.52196 users lost their C-101 input mapping, due to internal changes made in the module. Here you have a tool to recover old C-101 input mapping. Take into account that it only works correctly with mappings saved previously to Open Beta update 2.5.6.52196. How to use it: input_profiles_repairer.exe "X:\fullpath\Keyboard.diff.lua" Same for joystick profiles. Just add " before and after the path and file name. The file generated should be renamed back to a normal name. That is, the trailing ".fixed" should be removed. The new file will be saved in the same folder where diff file is. input_profiles_repairer.rar
  23. Once multicrew is finished the module will be pretty much complete. Just pending some bugs, features and improvements.
  24. There are several fixes to do in weapons.
  25. Thank you. Mainly will be failures repair. For example, you will be able to set an engine fire in the ME and repair it afterwards once in the mission, as you know, landing in a friendly airport, shutting down the engine and requesting repair to the mechanic. There will be a large list of failures that were not working previously, including failures that occur during the mission and are not set in the ME. Another example of this type of damages, in this case a very tiny one, is the wire of the Emergency Gear Retraction Button ("Crash Button"). Once you press it (for two seconds to break the wire), you will have the option to repair the wire. And this applies to any other damages and failures that can happen in the mission or that can be set in the ME. As I said there will be a large list, these are just a couple of examples. In current version, many failures can be repaired but some others can't, after this update everything will work, unless we missed something. There will be other updates of course, but we won't have time for more since the version for Third Parties gets locked some time before the OB is released, to fix any possible issues. Next to fix will be remaining multicrew issues.
×
×
  • Create New...