Jump to content

WingC3

Members
  • Posts

    49
  • Joined

  • Last visited

Everything posted by WingC3

  1. Thanks. Like you say, it must have something cumulative from all the flights. It would be nice if you could shutdown and have maintenance done rather than having to get a new plane. Especially if you can't spawn a P-47 at the airfield where you've landed. I took it up for another flight and tried to really put it through its paces. I used water injection at low level for 4 minutes, then rested it a bit. Climbed up, used it at high level. Did some dives... All good. Tried to keep the MP and RPMs reasonably high until the plane was slowed down for landing. Engine survived just fine. Thank goodness the piston engine in the PA28 I fly in real life isn't this tempermental. I'm sure students at the club abuse it all the time, and I sure as heck don't want it dying on me!
  2. I'm new to the Jug, and I'm having intermittent engine issues with it. (Unsurprising I'm sure). I'm wondering, do you all tend to keep the same aircraft through many sorties: Landing, rearming and taking off again? Is the 15min of WEP cumulative such that after a couple flights you're basically obligated to get a new plane, or does resting the engine reset things over time as long as you didn't exceed the 15min in any single stretch? Tonight I did 4 flights in the same Jug. Was very careful not to ever let the temperatures overheat. Had two very successful dogfights. After the 3rd kill, I reduced RPM and MP back to max continuous (MP was a bit lower at 40inHg). Crusing along level for about 3 more minutes, and a grinding noise starts. Then, power loss followed by complete seizure. Temperatures were normal right up until the grinding noise, then they skyrocketed right as the engine died. I'm at a complete loss as to what went wrong. I was very careful to not exceed 64inHg for more than a brief instant in any of the fights. Do these engines just die after a few hours of flying?? Also, with the intercoooler shutters at neutral, I did notice that my carb temp was a bit low. Can that kill the engine on its own?
  3. Still experiencing this as of today. Didn't occur until designating at 1.3nm HRM mode.
  4. Still experiencing this on 12 August 2023. Seems to happen at the 1.3nm zoom level of the HRM.
  5. Found two issues related to how the AH-64 displays wind information. Firstly, on the TSD, the wind information displayed is meteorological wind direction, not aviation wind direction (as found in METARS). In other words, it is reporting the direction towards which the wind is blowing rather than where the wind is coming FROM. I don't know if this is how the AH-64 really does it, but no other aviation source that I know of does. Secondly, The PERF screen also has a wind display, and it disagrees with the one on the TSD by about 40 degrees. It would appear as if the TSD report is the correct one, so I'm not sure where this one is coming from. Please see the attached screenshot.
  6. I noticed that if you start the engines with ground power on, the generators also don’t start. Is this expected behavior as well where the reset is needed, or possibly a bug?
  7. I'm sad to report that this is still occuring without Volanta installed or running. dcs.log KaiGir's Georgian Privates 20210417-20210419-213858.trk
  8. Hi, Yeah, will do further testing this evening. Have removed the call to the Volanta lua script, and will see if that solves the issue. If so, it's really a bug for Orbx to solve in Volanta.
  9. This bug has occurred to myself and friend of mine multiple times in the viper. It may have occurred once in the F-18 as well. The crash occurs after landing and re-fuel/re-arm. The re-arm completes succesfully, but upon advancing the throttle to begin moving again, the game instantly crashes to desktop. Loadout of the aircraft was 2 x wing tanks, 5 x Aim-120C5, 1 x AIM-9x on station 3. Unfortunately, due to the CTD, I'm pretty sure the trackfile didn't get saved. I'm attaching one that MIGHT correspond to a session where this occured, but it seems too small. Uploading DCS log as well. Possible hypothesis: Something to do with Volanta's plugin being installed, but volanta not running? Kai's Syrian Privates 1A 20210418-20210418-204437.trk dcs.log
  10. Thanks Czizh! Spartan: DCS has been around for many years before you apparently just discovered it last month. This bug is new, and it clearly is going to have a short life. Perhaps save your sanctimony for something else?
  11. Noticed this on a Persian Gulf Instant Action Cold and Dark Start. After the flight, I pulled into parking and shutdown the viper. However, exhaust continued to spew from the engine. I don't have a track, as it was single player and I forgot to save it, but I do have video evidence.
  12. It was a cold start in the instant action cold and dark. I attached a track a few posts down already. Let me know if the link is not working. I'll give this a try on Caucasus and Nevada and see if it is indeed a PG thing.
  13. Here's a short track Here's a short track. Notice that de-arming and re-arming moves both the horizon line and the gun cross. Only the gun cross should have moved. It does appear to still be *somewhat* tied to the horizon, but there's some correction value that is now wrong it seems. Track here: https://drive.google.com/file/d/1g6LMfJFqjCp7X6aGP5lJxbO3cGTL-pIn/view?usp=sharing
  14. Silly question: Where to tracks from instant action go? I'm used to multiplayer, but this was done in SP.
  15. New issue to the 2.5.6 patch: The HUD horizon line is not slaved/locked to the gyro/INS orientation information (I'm not sure which is the primary input for this IRL). Instead of being fixed to the actual horizon, it is affected by the weight and loading of the aircraft. Unlike the gun cross, which is a static indicator of the aircraft's nose position, the horizon line should be fixed to the actual horizon and corrected by gyro/INS inputs. It should not be affected by the position of the nose or weighting of the aircraft. (And it wasn't before this patch, nor is it affected this way in any other aircraft.) See attached image of the horizon line above the actual horizon. Also see youtube link where horizon position is corrected by adding 2 300 gal tanks. (Tanks are added at 4:22) (This should not affect the horizon position....) Thx
  16. Means the track is corrupted. Happens often with long tracks. It's basically unusable. Of course, that's not helpful when the issue doesn't always occur early in your play session... There must be some way for ED to fix the track system...
  17. Possible additional info: The guys on the 104th seem to have discovered a correlation between F16 and F18s being contributors to Link16 on the same side. They have separated them on their server, and the issue does not appear to occur any longer on that server. I can confirm that I did NOT have the issue on their server since they made that change. They seem to also be of the impression that ED is aware of that discovery. It definitely still occurs 100% of the time of the Through the Inferno servers. It seems that an AWACS must be present as well. On the aerobatics server where there is no global datalink donor, I don't believe I've seen the issue.
  18. Ah cool, that'll be amazing once it is! thanks!
  19. I know the 9x seeker will follow the HMCS when in DGFT mode and BORE selected. Is there a way to get it to do that OUTSIDE of BORE and DGFT modes?
  20. Can I just say how thrilled I am that they spent the post holiday on THIS and not ACM boresight, link16 issues between F16s and F18s, weird main gear compression behaviour, etc.... Don't get me wrong, the viper rocks, and I KNOW they'll get there. Just the prioritisation is really ODD sometimes!
  21. HOTAS button for Slave/BORE In a related area: In DGFT mode, is there a way (other than pressing the MFD OSB) that lets you toggle on the HOTAS between AIM-9X Slave and BORE quickly? (I know I can bind the OSB to my stick, I'm asking if there's an official HOTAS button for it)?
  22. Just in case you guys missed it: Track file link https://drive.google.com/open?id=14zBxIw-K2Jn9aGq1nqO02cb7EXR5MRIo
×
×
  • Create New...