Jump to content

CarlosNO2

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by CarlosNO2

  1. I'm assuming this wasn't fixed in the hotfix? I tried it on Wednesday and no comms as soon as a human RIO loaded in.
  2. Has there been any update on this issue? I just tried last night and couldn't get the TPOD Flir adjusted in any way, the gain level doesn't do anything at all and the bezel rockers don't adjust gain or contrast either.
  3. Ok well I got the time to try and reproduce the issue to no avail. I set up the main components and relative geometry of the situation I first encountered it in, and changed a few things between three runs. The DDD and RDR worked as expected, with the contact (a beaming coalt F-5E) appearing faintly at around 50ish nm, and at around 47nm it would stay faint in Pulse Search, but became a stronger contact in the HCU RDR supersearch, and allowed me to lock it. I guess I chalk up the earlier issue to a possible combination of Pilot/RIO/Plane desync + multiplayer BS. If I run into it again I will post again in this thread.
  4. Hi, thanks for the reply. Yes, I did use one bar scan, and used the vernier and coarse elevation adjustment both in the Pulse search and the HCU commanded super search, the contact was nowhere to be found. I was referencing the RDR elevation indicator to the left of the DDD as usual and manually scanned around the entire area the contact was seen in Pulse search. I even tried having my bars set to every different setting to have the superscan help me elevation wise just in case. Judging by your response, it is unintended behavior so I will try to reproduce it tonight and perhaps record something.
  5. Hello all, when I was brushing up on my RIO skills last night I had some weird things that seemed to happen on the DDD. The behavior of the radar returns seemed a bit off. A main issue I ran into was during my use of pulse search, I was receiving returns on some contacts between 50-100 miles away, but when I did half action on HCU in RDR mode, and placed the cursor in the exact distance, azimuth, and elevation as I was getting the return it would not appear at all. I attempted to troubleshoot by adjusting the Pulse gain and the Erase knobs, and using 1 bar scan to ensure no elevation issues, and even turned the MLC off and on to no avail. I also confirmed there actually was a contact there with RWS and the F10 map. After getting much closer, it seemed to work as usual. There were a few more oddities but none as obvious as this. I am unaware if there is some actual reason this could happen, and it could be intended behavior I am not sure. But to me it makes no sense that I would get a strong and full radar return in a 1 bar scan in pulse search, but then have that return be completely gone when I am commanding the radar in HCU RDR mode, effectively its doing the exact same thing electrically and mechanically unless there is some additional system or functionality in the AWG-9 I am unaware of. If this is not intended behavior, I can go back and try to collect more data on what happens in order to help HeatBlur debug it, I just didn't want to invest the time into it first before confirming it isn't intended behavior.
  6. Hey man, are you sure its not the maneuvering flaps? They get put down automatically, and if you have your DLC axis not centered, that could also manually command them either in or out. Your flap lever trick is probably overriding the maneuver flap logic and that's why it fixes it. Try using the DLC axis to force them in and out, and if that is your issue, you typically leave the axis in the center and allow the flight computer itself regulate maneuver flap usage.
  7. Hopefully you were PM'd the needed information @BIGNEWY, but just in case here is a clip of Mover trying to reset the max G indication in the way described in a video of his: (its timestamped)
  8. Is that a bug? I just thought the Viper has plane equivalent of hemophilia IRL. I thought it was odd for a A2G and SEAD capable aircraft.
  9. Oh you are correct, I do see it in your tacview! So the issue is likely related to some FM calculation that breaks past a certain AoA and allows all the crazy stuff, very interesting. The funny thing is the plane feels extremely convincing otherwise until you take it to that limit.
  10. That... is one of the coolest DCS videos I've ever seen! Nice work figuring that out. I wonder if its related, but I have had the Mirage F1 push through its drag (it feels like) when applying full forward stick for a long time. If done at less than about 350 knots (so the pilot doesn't die) the plane will eventually begin to GAIN energy while at a high negative AoA and the engine eventually dies due to the negative G. I could sometimes keep it going past engine death. Have you noticed anything similar in the F1 yourself? If I remember tomorrow I'll attempt it again in instant action to get a short track to post.
  11. Good luck getting planes not that old, between ITAR this and ITAR that, they should probably focus on finishing all the modules on their plate before biting off something like an F-15C, especially with Razbam basically having an F-15E ready to begin showing off. (video showing INS, Toss bombing, and A/A engagement came out today) Most of the available modules have significant bugs one way or the other, I mean they literally have an uncorrected bug since launch for THE SABRE, and in the forum someone literally did all the research, provided ALL the documentation, and even provided examples on how to fix ED's code handed to them on a silver platter, and still as usual "Reported", Thread Locked, radio silence, rinse and repeat. I cannot understand the people who look at the current DCS environment and think asking for an even more modern module is a reasonable thing to do with how everything seems to pan out.
  12. Bumping the thread for more visibility. It's kinda crazy that they broke such a crucial api functionality that many scripts use to create worthwhile missions and training environments, and then haven't fixed it for almost a year. Please get this fixed so the scripting and multiplayer community can continue to prop up your game for you despite the lack of dynamic campaigns or many useful mission making features in the base game.
×
×
  • Create New...