Jump to content

BIGNEWY

ED Team
  • Posts

    41508
  • Joined

  • Last visited

  • Days Won

    613

Everything posted by BIGNEWY

  1. As soon as we can confirm a date for steam we will let you all know. thank you
  2. Hi, we are reading the comments, I have even replied in the thread, I pass on the feedback directly to the team. I understand the frustration with slow development, however that is how it is, early access does take time, it has to be this way so we can get peoples feedback and reports, and allow us the time we need to develop. If a finished product is what you are after for your initial experience it may be best to wait for the early access to finish before considering a purchase. Threads like this do not help with speeding things up, the team is already working as fast as they can. Thank you for your purchases and supporting our work, but please understand that this work can not be rushed, and it will take time to complete.
  3. Hi, Some animations and functions are still W.I.P, please stay tuned for future updates. thank you
  4. Hi axis for zoom is working here, are you sure you are in the axis section? as for the jettison it is reported. thank you
  5. Yeah 10fps with your system seems odd for sure, if you have a track replay that isnt to big, attach it so we can test it also. Just bear in mind some servers run many scripts and external databases which dont play well with track replays. thank you
  6. Hi, please run a slow repair try moving the input folder for the aircraft to the desktop, create new bindings and test. Attach your dcs log so we can look for clues. thank you
  7. Hi, currently we do not have any plans for VR in combined arms. In the future we may consider combined arms 2 or something like that. Adding VR support would take considerable effort and resources.
  8. Hi, this has been reported to the the team. thank you
  9. Hi, thank you for your report. We have asked the team to look at this.
  10. GPS-Era / STRD HDG Alignment First, let’s start with the most common form of alignment in DCS, GPS-era using a STRD HDG alignment. This is the simplest, fastest, and most common for single- and multi-player. With power to the avionics systems, set the INS switch to STRD HDG and then set the GPS switch to ON. It’s important that the MIDS switch remains in the OFF position. After about 12 seconds, you’ll see an ALIGN indication on the HUD. You’ll then verify the STRD HDG alignment by going to the DED INS page and check the latitude, longitude, and altitude against your location on the F10 map view. After about 60 seconds, you should be aligned and confirm this by the ADI flags being retracted; HSI showing correct magnetic heading, DME, bearing pointer and CDI deflection; roll and pitch correct on the HUD; and RDY should be flashing on the INS alignment DED page after less than 2 minutes. We can now switch the INS switch from STRD HDG to NAV. On the DED INS alignment page, confirm that GPS TIME is displayed one minute after the GPS switch is set to ON. Note that this may take longer if the aircraft is under cover like a hardened aircraft bunker. As such, it is best to align out of cover. With good GPS TIME, set the MIDS switch from OFF to ON. After alignment with GPS correction, you can expect no more than 40 meters of INS drift. Further, if you zeroize the GPS or are flying a REDFOR Viper, you can expect an INS drift of 100 meters or more. GPS-Era / Normal Alignment A normal alignment is much like the STRD HDG Alignment, but we’ll need to manually enter the aircraft starting location because we’re not using a known, STRD HDG location. To start though, we’ll in the INS switch to NORM and not STRD HDG this time. Then set GPS to ON, verify MIDS to OFF, and wait for ALIGN on the HUD after about 12 seconds. The big difference is now going to the DED INS alignment page and entering the aircraft’s latitude, longitude, and altitude as shown on the F10 map. Once done, we’ll verify ADI, HSI, and HUD as before and wait for the flashing RDY indication on the DED INS alignment page after about 8 minutes. Once flashing, set the INS switch from NORM to NAV and verify GPS TIME indication. With that, set the MIDS switch from OFF to ON. These will be the most common alignment scenarios when performing a cold start. However, you may come across a mission or campaign with a date prior to the GPS era. In that case, we’ll only align based on INS with no GPS correction. Non-GPS Era / STRD HDG Alignment Like the GPS-era, set the INS switch from OFF to STRD HDG and wait for the ALIGN indication on the HUD. Then, verify the DED INS alignment page latitude, longitude, and altitude to the F10 map data and verify ADI, HSI HUD, and wait for the flashing RDY indication. We can now move the INS switch to NAV. Once airborne, you’ll then want to conduct alignment FIX procedures using Overfly, targeting pod, HUD, or FCR to remove accumulated INS drift. Please see the earlier videos on fix taking. Non-GPS Era / Normal HDG Alignment The last weight-on-wheels we’ll look at is doing a normal alignment at a mission date prior to GPS. Set the INS switch from OFF to NORM and wait for the ALIGN indication on the HUD. From the DED INS alignment page, enter the aircraft’s latitude, longitude, and elevation using the F-10 map. Next, verify the DED INS alignment page latitude, longitude, and altitude to the F10 map data and verify ADI, HSI HUD, and wait for the flashing RDY indication after about eight minutes. We can now set the INS switch to NAV. Once airborne, you’ll then want to conduct alignment FIX procedures using Overfly, targeting pod, HUD, or FCR to remove accumulated INS drift. Please see the earlier videos on fix taking. So far, we’ve only been talking about weight-on-wheels alignment procedures. We’ll now shift gears and discuss in-flight alignment. We’ll start with the more common GPS-era procedure. GPS-Era / In-Flight Alignment First, set the INS switch to FLT ALIGN and flight straight and level until the ADI flag is retracted. You’ll see INS FLT ALIGN on the DED and STBY on the HUD. Maintain straight and level flight and enter your compass magnetic heading within 20 seconds on the DED and verify that the pitch ladder is displayed on the HUD. Continue to fly straight and level until the ALIGN is replaced with the maximum G value on the HUD and then return the INS switch to the NAV position. Non-GPS-Era / In-Flight Alignment Last, for an in-flight alignment with no GPS, set the INS switch to FLT ALIGN and fly straight and level until the ADI OFF flag is removed. INS FLT ALIGN should appear on the DED and STBY on the HUD. Fly straight and level and enter your magnetic heading on the DED within 20 seconds while ALIGN appears on the HUD, replacing the maximum G indication. We’ll now perform an OFLY FIX within the next 30 seconds. It is required we perform a second OFLY FIX within two minutes to correctly perform velocity calculations. Keep flying straight and level, and once the maximum G field replaces the ALIGN indication, you are done. For best INS alignment, you may wish to perform an OFLY, HUD, FCR, or TGP alignment every 15 minutes for best possible navigation and acceptable weapon accuracy. Manual Alignment as Backup The manual alignment is a backup alignment designed to provide get-home capability only.
  11. Try setting your pagefile to auto. You have 64gb ram it is more than enough, and setting it to auto will be easier on your disk space. Multiplayer will always be more demanding on the machine, there is way more going on, and usually MP missions have 1000's of units.
  12. Hi, you can save a track replay when you exit the mission during the debrief screen
  13. Hi, the ATP has been added to DCS now, and although we currently still have the AN/AAQ-28 LITENING in game to support older missions loadouts the ATP supersedes it. I will discuss it with the team again however. Thank you
  14. Hi, we have tested our public builds and flaps are working as expected with controller and keybinds. Please double check for any strange keybind issues, if you still have problems include a short track replay thank you
  15. Hi, we do have a report for this, it is lower priority however. thank you
  16. Hi, please ensure you are setting the laser code correctly on the bombs. If you still feel there is an issue please include a track replay example. thank you
  17. Hi, please include a short track replay showing the issue, if you can do it on the Caucasus terrain that would be optimal. thank you
  18. thanks for letting me know
  19. Hi I will ask the QA team to check in a MP session. thank you
  20. Please if you have actual evidence from the block and year we have modelled DM me directly thank you
  21. Hi, do you have any key assigned to the flaps on his HOTAS/Joystick? If so, can you actuate the flaps via these key binds? thank you
  22. Please include a track replay and a video if possible so we can see what you are seeing. At the moment we can not reproduce Please also see here thank you
×
×
  • Create New...