Jump to content

discwalker

Members
  • Posts

    1357
  • Joined

  • Last visited

Everything posted by discwalker

  1. - Fresh DCS start - set in game oftions misc random system failures to ON, - in this mission Forced to OFF, DCS dont care about it, after approx 28 min runtime failures came (dont takeoff, just use 60x time compression) OverrideOverriddenTest.miz
  2. 2.5.4.30386 without any script, only 1 AC a client FA18C and unwanted failures came. 28min runtime; caucasus; ME rnd failures forced OFF [4] = { ["failure"] = "Failure_Fuel_Tank4Transfer", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 26934, ["type"] = "failure", }, [5] = { ["failure"] = "Failure_ECS_Valve", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 27319, ["type"] = "failure", }, [6] = { ["failure"] = "Failure_PP_RightAMAD_OilLeak", ["failureDisplayName"] = "", ["initiator"] = "Pilot #001", ["initiatorMissionID"] = "269", ["initiatorPilotName"] = "discwalker", ["t"] = 28005, ["type"] = "failure", }, 2,5,4,30386_WITHOUT_takeoff_failures-RNDfailuresForcedOff3.trk
  3. debriefing log shows the correct exact failures occured by something (indirect scripts?): [16] = { ["failure"] = "Failure_Hyd_HYD1B_Leak", ["failureDisplayName"] = "", ["initiator"] = "Pilot #038", ["initiatorMissionID"] = "114", ["initiatorPilotName"] = "Skimmer", ["t"] = 26432, ["type"] = "failure", }, [17] = { ["failure"] = "Failure_Fuel_Tank4Transfer", ["failureDisplayName"] = "", ["initiator"] = "Pilot #038", ["initiatorMissionID"] = "114", ["initiatorPilotName"] = "Skimmer", ["t"] = 26904, ["type"] = "failure", in the first mission random system failures forced to off, maybe overridden setting
  4. :-) Perhaps nothing was broken or fixed. Please thanks the FA18C failures to the mission designer. replay of your first track: See the 2 coming failures in client AC when random system failures is off (ME forced), preprogrammed failures not available due client slot. 7h20m 7h28m (+tank4 feed, right generator) +in the global settings random system failures was off during replay ++but we know the track settings is over the global settings, they are permanent until DCS restart
  5. As Kang said i'm intrested in a mission part track recording. This way we can produce smaller tracks with the essential what we want to show. For a short error reproduction this way we not always needed to use the mission editor.
  6. I'm tired of using "connect by IP", watch with one eye https://www.digitalcombatsimulator.com/en/personal/server/#allservers for what is the current mission and map. Please send telemetry to ED HQ from "Cant see all MP servers in browser list" long standing problem. Since 2018 february this is problem for some end users, in the 2.5 series. https://forums.eagle.ru/showthread.php?t=201656 https://forums.eagle.ru/showthread.php?t=235620 1.5.8 ended with this fixed in the latest openbeta, but dismissed; the latest 1.5.8 stable left with buggy serverlist. I not force the telemetry, I prefer the fix! Of course telemetry will show datas from enthusiast users only, not from users left the DCS because this kind of things!
  7. Why isn't this a client setting? I want tooltips, and I hate when disabled, especially in MiG-21 with russian cockpit.
  8. Request for new ground crew feature to many years old problem: door open Just go through door? :helpsmilie: 2.5.4.30386 - 104th Phoenix server
  9. Usual workaround ineffective for Tomcats in Anapa In short: 8_Op_Fire_Shield_13-20190512-221610-tomcat3anapa_spectatorBackClosed.trk https://drive.google.com/open?id=1C64g4mxs34Z8TJChmURZoIYTwRXvvpd3 Used only one of the Tomcat slots in anapa for twice, the third, in between go to spectator tried. Without success. In detailed: 8_Op_Fire_Shield_13-20190512-215835-tooManyClosedSheltersTomcat.trk https://drive.google.com/open?id=1Eai2Rpz8RHv1MSilD4WDJe8SbYuS5hP2 Many closed Tomcat spawn, in between F-15C apron (ATC comm not working), then: After a Su-25T shelter slot (ATC comm working... takeoff cleareance got) first Tomcat can spawn in an open shelter, then neighbor Tomcat spawn in closed shelter. Uff. tested and failed: 2.5.4.30386 Please fix it! Finally.
  10. @VWJII, You want to change my mindset?!! First of all please send to me better equipment, not just hotas. I tried enough hard to refuel in my planes, and only succeed the Su-33. Hornet with ATC on has a marginal unrealistic feature missing. Small ATC correnctions is not always possible due, my throttle axis not moving via ATC. Not always moveable the real axis to small corrections to speed. What an idea to neglegt the need for a feaure in a feature request thread.
  11. I flew the Tomcat a very little because of ease to overstress the plane with light stick movement. All the time I not be able to turn with inside concentration to the instruments. Tomcat is ideal for draconus, good to you.
  12. @VWJII, Last of all it is unlimited fuel option, with those fuel management is broken. Unlimited fuel option is not a feature that renders Easy AAR unnecessary. I bet you never used unlimited fuel. Your opinion is hurting.
  13. The possible spawn points for Flankers and Vikings are the same. Altough the big F14B and A10 can start from anywhere in Caucasus. If I maximize Flanker starting in Gelendzhik (3 of 13), Sukhumi (5 of 20) or Beslan (5 of 15) no more place for hot started Vikings without fuel for functioning as mobile TACAN stations. (A/A TACAN on ground) (Flankers can land and taxi back to spots unable to use for start, while Vikings when land just disappear form runway.) in the attached mission: Try to drag Vikings from Novorossiysk to Gelendzik, from Gudauta to Sukhumi, from Mozdok to Beslan. ((no final unit assingnment to TACAN in advanced waypoint actions)) unable_to_add_vikings_to_the_ramp_as_tacan_stations.miz
  14. It's a low hanging fruit. There is a benefit of working on this, because we know the multiplayer variant cause to new players discomfort.
  15. The most annoying black flickering bug forced me to use water at low settings but this happening. 100% reproducible with all planes I fly. When i turn off the mirror or focusing elsewhere normal sea came back.
  16. confirmed in 2.5.4.30038 I hope some day this bug will be acknowledged. I not hope for a fix. steps to reproduce: 0. options cockpit shadows to off or flat 1. FLY with fa18c (not on ground) 2. extend refueling probe 3. look the cockpit instruments 4. make a 360 degree turn 5. watch the plane outside also from front during movements 2,5,4,30038_cockpit_shadows_off_or_flat_fa18c-refuleprobeflickering.trk
  17. Test mission Not working remove zone in MP in 2.5.4.30038. (Destruction zone works.) Even in single player mode buggy in caucasus, airport static vehicles are not removable by ALL or OBJECTS filter. There was a time when they were hideable objects. There was a time they were shown in ME. scenery_remove_mp_test.miz
  18. :-( Not fixed yet in 2.5.4.30038, maybe unseen by ED, maybe not reported My track is accurately replayable in current, same happen if I play my mission from the beginning: https://forums.eagle.ru/showpost.php?p=3637315&postcount=2
  19. confirmed with 2.5.4.30038 as dedicated server client side track, 4th spawn in session Slightly modified mission, free module friendly bug_bluetriggerPartRedInZone-20190429-002624_J11BLUE_as_red-8h3m58s_4thSpawn.trk
  20. I moved DCS 2.5 in non offline mode to SSD, but DCS know it is running form HDD via DIRECTORY JUCTION. thats all.
  21. Confirm. In SP mode fired 2 HARMs to different MOLNIYAS and both hit the same ship.
  22. "JDAM accuracy increased." how? ME and F10 map still display lat-long in DDMMSS. Don't say I need to use converted lat-long decimal from DD MM.SSS.
  23. Not a bad idea, i saw a lot of teamkills by F/A-18.
×
×
  • Create New...