Jump to content

colasmulo

Members
  • Posts

    8
  • Joined

  • Last visited

About colasmulo

  • Birthday August 13

Personal Information

  • Flight Simulators
    DCS World, Microsoft Flight Simulator

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I cannot remember from when I remember this, but I remember a feature not working correctly once before with a unit already placed in a mission file created before the update. The testing I've done and the infos gathered on this post lead me to believe this is what is happening here. When playing a mission already existing before the update with ACLS, the carrier/hornet does bot behave as expected. When flying a mission created after the update, it works as intended. I was able to replicate this multiple times during my testing. What I need to finally test is if a new carrier is placed in an older mision, if it fixes it or not. If anyone wants to try the same with their old vs new mission to confirm or not my thnking don't hesitate to share results ! Edit : Can confirm placing a new carrier and setting it up in an already existing mission will make the ACLS work as expected (Wag's video for reference), while a CV already placed before the update , but configured the same way will not work as intended (no mode 1 on ACLS display and no proper autopilot.
  2. Many thanks for the answers, I had no idea these levers existed. With that information it could make sense that they are turned all the way down by default at night so the pilot has to adjust them to whatever the lightning conditions are when he starts the plane.
  3. Hello fellow pilots. I noticed that when starting a mission at an hour considered as night, the AR Status/NWS Indicator lights in the F-16C cockpit do not seem to be working at all. Using two mission files on Syria and Persian Gulf maps I was able to reproduce the problem, when starting the mission around 5:30am, and the problem was not reproduced when starting the mission around 5pm. In the attached track file I start an F-16 at night and start taxiing, activating and desactivating the NWS and air refueling switches. They both work as seen by the plane being able to turn and the AR valve opening, but the indicator lights do not turn on in the cockpit. The track is from a multiplayer flight but I was able to reproduce the problem in single player. I'm running the game on Openbeta 2.7.0.4625, my specs are i9-9600k, RTX2070S, 32Gb DDR4 RAM, game installed on an SSD. server-20210416-231449.trk
  4. I noticed the same, a friendly tanker went from diamond to normal and switched a few times as I tried to unlock and re lock it. I could be doing something wrong too though.
  5. I did some testing this morning, 2 flights without loadout, and I flew 300nm without a problem. At the end of the second flight, I landed, got a loadout of fuel tanks and missiles, took off, and game crashed after 5 minutes. I used waypoints and tacan everytime so that shouldn't be the problem. I restarted a flight with ths same loadout, and game crashed after 10 minutes. Edit: the problem seems to be caused by fuel tanks, flying with missiles and no fuel tanks doesn't crash the game, flying with 3 fuel tanks crashes every time.
  6. I'm having the same issue, so I'll post what I can in hope to give more info to solve this problem. I've had this freeze that requires to kill DCS in the task manager on different servers in multiplayer and in solo on different missions, every time with the same loadout of 3 fuel tanks 4 Aim7M and 2 Aim9M, and I use waypoints and TACAN to navigate. I ran multiple tests and every time the game freeze to death after about the same time, roughly 20 minutes. As for the others, nothing in the log file to exploit, the last entry is from 10 minutes before the freeze, I attached log files and a track file of a flight that ended up in a freeze. Somehow, I tried the hot start instant action mission and wasn't able to reproduce the freeze after 40 minutes of flying the same way, with waypoints and a Tacan, but this time no loadout. I tried a cleanup of DCS and a repair, deleting the metashaders folders, and no change, it keeps freezing in the hornet. My specs are the following: Win10 Home 64bit, Intel I5-4690K, GeForce 1060 6GB, 500GB SSD, 16GB DDR4 RAM, Edtracker, Logitech X56, Logitech Rudder pedals. Logs.zip Patrouilleur_du_FAIL_v89_experimental-20180602-005817.trk
  7. You're probably downloading 2.5.1 like myself and the others who forced the update. Sorry to disapoint you.
  8. Will there be huge waves during bad weather like on the Normandy map ? This could add a lot of fun to carrier operations, in addition to night operations !
×
×
  • Create New...