Jump to content

Triggerjo23

Members
  • Posts

    74
  • Joined

  • Last visited

Everything posted by Triggerjo23

  1. Sauadron Name: Task Force Trident Aircraft Selection: All Pilot Roster: TBD Time zone: International
  2. Hi, I can confirm this happens. It quite possibly is just in multiplayer as I don't play single player so have no reference for that. Basically the HMD when in bore sight can hover over a target without locking. Fixing requires switching through multiple radar modes. Sometimes you have to cycle many times before you get a lock. Verticle scan seems to work better but bore sight even when using sensor select long finds it very dificult to lock often. The radar also loses lock when in a turn fight, it always seems to conveniently be when you pull lead and are about to pull the trigger too.
  3. I am not asking you to disregard proven information at all as you have no information you are willing to accept on the missile. Vice versa, you are asking me to accept something you have no evidence for as all the evidence points in the opposite direction. I am not arguing over the way the 54a works, I am trying to clarify on the way the 54c works based of official nomenclature used in all descriptions of it's functions. They are not just similarly named as that would defeat the purpose of it being a nomenclature, they do not just casually name these systems. Nomenclature "The body or system of names used in a particular specialist field". It is a much bigger leap of faith to assume that a missile made decades apart from it's predecessor is just as obsolete especialy once given the the expressed updates which are stated to be present on another known and contemporary missile. It's clear that there is a phylisophical devide between us here so I am just going to leave it at that. Perhaps your lead will take us somewhere but I doubt it as you will most likely just get the same level of info depending on the source. If it is a freedom of information act request then it will probably get rejected due to ITAR and if it is someone just telling you then they are at risk of breaching ITAR restrictions if it comes from ITAR controlled documents. I left my part on a good note with Iron Mike and am now right back to debating with yourself so it's best just to agree to disagree I think, but good luck with your lead.
  4. I totally get it and am hopeful for the best and am thankful for your hard work and passion. All I mean by moving away from the module for now is in regards to the DCS competitive scene just wanted to say that. Regarding the main topic of the thread before we went off tangent, we have seen the exact same scenarios. Firing a missile on a target cranking at 20-30 degrees can see the missile reach them at only a few hundred knots or sometimes even just fly off the rail in a straight line even though the TID shows no lost track. This has been happening consistently. Even PAL with ACM cover up once the missile is active will see very wide misses. Nearer the start of the year this kind of shot worked really well at around 10-15nm with ACM cover up and 10k feet higher than the bandit, now though all BVR launched missiles are missing and almost all PAL shot's are missing. The notch on all of the other DCS Fox 3's seems to be much larger now too and perhaps something which changed that is having an effect on the present Phoenix? May I make a suggestion? How about you guy's start up a discored server. I feel comunication that way will be better for off topic conversations and perhaps the nice, fun daily messages could help prevent anyone from feeling like there is hostility in the air as that is not my intention at all. Wanted you guys to make a discord for a long while now. Just some food for thought.
  5. Again, I wasn't trying to be rude and I had no intention of being so nor do I think I was, merely trying to help out. On the matter of documentation, you will most likely not acquire it as it is ITAR controlled but I hope you can. Also, as I said earlier, given the real evidence regarding the AIM-54C you are making a larger leap in guesswork than anyone else as far as I can see. I really hope one day you can fix this and I assure you seeing every patch worsen or leave the Tomcat in the same place it is right now feels a lot like groundhog day too. I have had patience with it for a long time and maybe one day I will be able to return to it but for now I won't be able to which is unfortunate. Good luck and I wish you and Heatblur the best.
  6. Explicit, "stated clearly and in detail, leaving no room for confusion or doubt" or a "literal explanation", "in accordance with it's original meaning". To say that Coomand-Inertail is not prove that it goes active on it's own is somewhat nonsensical to be painfully honest. Guidence laws include, Command Guidance: "The missile tracker is on the launching platform (The AWG-9/WCS). These missiles are totally controlled by the launching platform that sends all control orders to the missile". In other words, during the Command stage of the missiles flight it is guided by the F14 that fired it, slaved to the F14 to an extent and relying on it's updates. Inertial Guidance: This can only be used in an autominous system. A missile fired with this capability as you already know is updated on it's starting position based off the inertial navigation of the firing ship. The inertail stage does not come until the missile is autominous (pitbull) and is how the missile guides itself to a last known position of a target, you know this ofcourse. Further more, "Strapdown systems Lightweight digital computers permit the system to eliminate the gimbals, creating strapdown systems, so called because their sensors are simply strapped to the vehicle. This reduces the cost, eliminates gimbal lock, removes the need for some calibrations and increases the reliability by eliminating some of the moving parts. Angular rate sensors called rate gyros measure the angular velocity of the vehicle. A strapdown system needs a dynamic measurement range several hundred times that required by a gimballed system. That is, it must integrate the vehicle's attitude changes in pitch, roll and yaw, as well as gross movements. Gimballed systems could usually do well with update rates of 50–60 Hz. However, strapdown systems normally update about 2000 Hz. The higher rate is needed to let the navigation system integrate the angular rate into an attitude accurately. The data updating algorithms (direction cosines or quaternions) involved are too complex to be accurately performed except by digital electronics. However, digital computers are now so inexpensive and fast that rate gyro systems can now be practically used and mass-produced. The Apollo lunar module used a strapdown system in its backup Abort Guidance System (AGS). Strapdown systems are nowadays commonly used in commercial and military applications (aircraft, ships, ROVs, missiles, etc.). State-of-the-art strapdown systems are based upon Ring Laser Gyroscopes, Fibre Optic Gyrocopes or Hemispherical Resonator Gyroscopes. They are using digital electronics and advanced digital filtering techniques such as Kalman filter." To elaborate on this further, Strap-Down Inertial is explained to be on the 54C, this is becuase it has a solid state seeker head and is a none gimballed system. This becomes a part of the Command-Inertial function and means several things. 1. The missile is not only getting updates from the F14 but is also constantly extrapolating the targets position after each update. 2, The missile seeker is already active whilst still in the command phase which is clearly stated on ducumentation about the 54c. 3, if the missile no longer recieves updates from the firing F14 then it is already active and already extrapolating the track to try and place the target within it's seekers detection cone. To conclude, the AIM-54C is infact the same as a big AMRAAM. This capability would not be implimented on to the missile if it was not allowed to be autominous without the F14 giving it the signal to be so. Perhaps this is all just due to a launguage barrier? As I understand English might not be your first launguage and the concept nomenclature might not be quite understood. I mean no offense by that by the way, I was speaking to someone in person just a few days ago who was speaking very good english but certain concepts or meaning were escaping him. I just had to explain these things in a respectful manner to allow him to reach the same page as me, so to speak. Put quite simply, if the missile did not behave the way all of the publicaly avialble documentation states it does then they would never have used these terms to explain the updated model. So again, you have all the proof you need to model the missile to the best standard, you are just ignoring it and that is why I am disapointed with it as with many others. I truly would love to sit here and congratulate you on a well modeled module and I hope one day I will be able to do that. With this level of missconception though, how can I be sure that future modules won't recieve the same treatment and results the Tomcat has now? You are not achieving high standards right now, you are guessing more than the people who are asking for a better AIM-54C. Again, I say this with the greatest of respect. Edited for some spelling mistakes.
  7. Others already have. The evidence posted by others is not a simple belief. Many documents supplied have implicit information as well as explicit. The combination of both the implicit and the explicit indicates only one thing, that if you claim to want to create the most realistic interpretation of the Phoenix and the Tomcat then this effort will fail. It will fail because you don't want to accept the information given. Now, I fully understand not wanting to model something you don't know how to model or don't have enough information on. That is reasonable even if I do not agree with it because of the different way we seem interpret information. I do however think that it can never be reasonably claimed that the module is a realistic representation of the F14 and it's weapons if there is a refusal to implement functions which have been stated in official documentation to be on the missiles. Functions which by the way are always described with well know military aviation nomenclature. You are looking for specific, explicit and detailed information on a certain function which has been adequately described elsewhere to be modelled with more than enough confidence. Choosing not to model it due to the lack of said explicit description will be making it infact deliberately unrealistic, approximating with best effort will infact be more realistic. If you are going to guess either way, it is best to guess in the direction the evidence points rather than settle at a baseline far below it. Don't get me wrong, I have a lot of respect for you guys and have flown the module in the DCS competitive scene since realise. Earlier this year I had to struggle to force myself to switch modules because it was not performing well at all after January. I keep going back to it after each update and it keeps getting worse and now as we see in this post it is suffering in single player and in multiplayer PVE in the same way. In it's present state I can assure you, the DCS World F14B is no defender of the fleet.
  8. If it is their intention to omit functions and behaviours becuase they don't "have enough information then they can not model an acurate and realistic interpretation of the Phoenix. In fact, this can not be done at all if they are unwilling to gestimate somewhat on these matters to approximate as best they can. You can't call a module realistic if 70% of it is unmodelled becuase you don't have explicit writing stating what has been confidently delivered information is 100% accurate. These functions are well known to be on the missile (54C) and are being minused because of slight unsureness. That is not a recipe for realism, it is a recipe for disapointment. The radar deserves the same thoughts as there are simple functions everyother radar had as a near contemporary to the AWG-9 which has not been implimented, again due to being "unsure". Well both the F14's radar and missiles in DCS have been consistently performing worse since January to the point of complete uselessness in for what many would deem perfectly acceptable scenarios.
  9. The big issue is that they are flying themselves into the notch as if they have a fixed lead point in front of the target. No optimal control on the track. Another problem seems to be that even when the TID shows a track has not been lost the missile can fly off the rail dead when they shouldn't as seen in the tacview posted. Maybe once the API has been completed better results will be seen but I doubt it these days as previous conversations with the devs shows that they are unwilling to impliment changes based on the highly probable way the missile should be tracking because they claim they don't have it in writing. The Phoenix used to work better because of magic INS but that has gone so all of it's inefficiencies are clearly seen. For the AIM-54C we will need optimal control and command innertail to see any real difference which most likely (according to previous conversations) will not be implimented. Saying that though it seems like there is very little proportional navigation being used whilst under AWG-9 guidence. There is also the problem of zero track memory in TWS which makes no sense. I mean it has enough memory to hold 24 targets but they won't sacrifce tracking all those extra targets to help the missile maintain a track and extrapolate through a notch, also no memory in STT I think too. This seems an odd thing thing to not build into a million dollar missile and a forty million dollar jet if you ask me which is why I don't get why it is being modeled this way on the DCS Tomcat. Maybe they will change their minds though and here's hoping!
  10. Squadron: Task Force Trident Timezone: 18:00z 19:00z Aircraft: F14, 15, 16, 18. Maps: Caucasus, may be able to add more later.
  11. Squadron: Task Force Trident Timezone: 1800z best time. Maps: Cauc, PG
  12. Pilot: {TFT} Rage RIO: {TFT} Stahl F14A
  13. Squadron Name: Task Force Trident Discord ID on MVP Discord: Triggerjo Contact person Discord ID: Triggerjo#4238 Aircraft Selection. F-18, Pilots: UK- Rage Infest
  14. It should be under BVR, Radar modes, Target size I think.
  15. You yourself say you lose half or more of your Phoenix's per sortie. You are also assuming how people fly. If you can't Crank or turn during a TWS launch then how can you descend? A crank and boards to 0.8M is a valid real word tactic and it was used in the F14 too. Cranking to 0.8M preserves range and forces even greater flight time into the oppositions missile. Who said the bandits have been beaming? Tracks drop when you are both nose pure. What does nose pure mean you ask? It means the bandit is in my HUD and I am in the bandits HUD. Tracks drop when we are both above the horizon line and nose pure. This is not a look down scenario. No one has been relying on Active launches. The issue here is not a lack of understanding or over expectation of the radar but a lack of comprehension of the problems people are describing. RIO or no RIO the issue I am describing still occurs. What you have to understand is that I am not saying it is the Tomcat either. It may just be a DCS issue as the same thing seems to happen on both the 16 and 18. I don't know however what causes it exactly but I know it is not intended as when testing engagement tactics in 1v1 PVP the TWS reliably tracks 100% of the time even when I crank and don't dive below the bandit and I slow down to 0.8M. However on a loaded server with more 4 or 5 people the WCS reliably does not track. I know when a missile is lost becuase the bandit is too low or is manoeuvering too heavily or in a notch. The scanarios I describe are not those instances but rather instances when the WCS should have no issues. To go from 100% reliable tracking to 0% reliable tracking using the same engagement tactics just becuase server conditions have changed is a rather blatent issue. I have tracks of F18 vs F18 practices but will have to dig for them. Also Tacviews but will have to dig for those too. Do remember that there have been updates to the 120 since those patches and sometimes changes do not actualy make it into the patch notes. The missile launch not giving an engagement warning during Radar slave is very easy to reproduce folowing these steps. 1. STT lock the bandit. 2. TCS slave to Radar. 3. Radar slave to TCS. At this stage the bandit should have a lock warning. 4. Hit PD or P search. The bandit no longer has a lock warning. Symbology on the TID expresses Radar slave to TCS. 5. Launch Phoenix. The bandit does not get an engagement warning and still has no lock warning. The missile can not be notched and will track as long as you have a TCS track. This works 100% of the time. Easy to test, get an F14 pilot and RIO to go through these steps vs another player in the opposing aircraft. It will only work at or under 40nm as aircraft on the TID only seem to render inside of those ranges.
  16. The 120 does reaxquire on the F18. If you lose track during a missiles flight it will begin tracking again if you pick up the track again on the same target. This is in part due to the memory mode on the 18's radar however if I set the memory to 4 seconds and lose a track then it can still reacquire the track and continue to guide the missile even when acquisition occurs after 4 seconds. No the 120 not going pitbull is a diferent matter completely but it can go pitbul. Bug or not it does do it. I have seen 120s be notched by myself when fired from around 20nm and no longer supported then they will acquire a friendly behind me who thinks it is a high energy missile. I have tacviews with me in quite heavy manoeuveres whilst maintaining TWS track on the bandit, now if I fly 1v1 then this is repeatable over 20 or more fights. Yet I also have experiences were the WCS will lose track 80 or more % of targets when niether myself or the target are manoeuvering. I have no idea if it is a Tomcat related issue or a DCS issue as the same things can happen with the F18's TWS. There are quite a few issues with desync right now with the Phoenix. The SD-10 has issues also however it needs greater ping or server load to see it and the 120c also however needing even more stress to see. My point with the issues with the Tomcats TWS is that I had never experienced any issues like this until right after the late January patch. Now I know the urge will be for people to say well you are acting as if it still has magic INS but that is not the case at all. Magic INS was removed before that patch and happened at the same time as the big WCS updates late last year. There was only one update added on the patch notes for the WCS in the late January patch and that was the (dissociation of the missile from the DCS object).
  17. Yes will definetely need clarity on that becuase it certainly gives the impression that is in game. Other things which are not implimented yet such as Data-Trans have (not yet implimented) on them. If this is a bug soley on the Tomcat then it is very dificult to pin down. All I know is that I can fire on a player 1v1 and have the missile track all the way to pitbul everytime so long as the opponent does not try to notch the radar. On other ocasions though and especaily when there are a good few people on a server it does not track at all. I am not so convinced it is a Tomcat related bug though and maybe something to do with netcode or ping in DCS perhaps. From what I have seen, the majority of people who have not experienced this fly PVE rather than PVP. The ones who do fly PVP resort to STT launches. As a small example; If you fly the F18 much at all in A2A then you will probably be aware of a bug where the F18 will not see a target right in front of it at co-alt and nose pure. The get around the bug you have to swap from A2A into A2G then back again and magicaly the bandit appears. There are also instances where TWS tracks will drop as a missile comes off the rail or halfway through flight. The 120 can survive this of course as once you reacquire lock the missile will continue to the tartget. The Phoenix of course does not do this, but when the tracks can be lost so easily at times even though both yourself and the bandit are nose pure on each other and not manouvering then you stand to lose more than half of your missiles like this if not more. STT at longer ranges is not much of an option becuase of the 2 minute long engagement warning a bandit will get to tell them a missile is inbound. I will try and dick through tracks and tacviews for the best examples of it. Sorry for the large response but I have another question. I was wandering if this is also a bug or not. The Phoenix and the AIM-7 can track from TCS without giving either a lock or engagement warning to the bandit. Certainly a great feature if it is intended however I don't know if it is or not. I have seen in some F14 manuals it says a target can be tracked silently via TCS but they never state this is with a missile or not. In the HB manual it says the Radar slave to TCS is equivilant to an STT lock and as far as I am aware the TCS takes over from the CW antenna which is what gives an engagement warning. I have limited understanding on this but just thought I would ask. Thanks for your previous reply. Edit. If the no engagement warning is a bug and you want to know how to reproduce it then simply STT a target the slave TCS to get a TCS track, then slave the radar to TCS. Once you have done this you hit Pulse or Pulse Doplar search to unlock the bandit. Now launching a missile will not produce a warning of any kind yet the Phoenix will track all the way to target.
  18. Squadron: Task Force Trident Timezone: GMT 1800 Zulu Aircraft: JF-17, F-14, F-16, F18 Maps: Caucuses, PG, Syria. https://taskforcetridentsimulations.com/ https://discord.gg/ag57DBg
  19. Never saw people saying the missile had a lock in ARH just that the missile was active. In the manual it states the missile will revert to SARH if a lock is not gained on a target. Yep, this is what the missile does just now. The AIM120 in DCS will reacquire but not the Phoenix. Are there any updates on fixing tracking issues in TWS for the Tomcat. It seems to be a big issue in multiplayer since the late January patch.
  20. This is refering to when firing in P-STT, PH-ACT or ACM cover up. The missile is active off the rails but will refer to an STT locked target if it can not find a target on its own. This feature has been implimented, you can find it in the manual under the Phoenix section.
  21. Why not just try to make an F14D, there is actualy data on that although even with that you will find it incredibly dificult to get enough data. You could go the fictional route with that and put 120's on it. Beyond that though, although I would like to have an ST-21 in DCS it would be 100% guess work. Even the artist renditions of it are guess work and not official desings.
  22. I am not confusing the DL with link-4 as far as I know it should be on a diferent frequency as others have told me. I have said I am looking for the right answer here as some tell me one thing and others tell me another but there never seems to be documentation to back it all up. Well if I can not see the documentation how do I know the others do and they are not just speculating. Documentation was posted which states that the Phoenix uses SA-PD antennas which would make sense for PD-STT then goes active with A-PD and not SA-CW. I think it is posted on page four to six on this thread. Also, other missiles of the same era used methods of tracking which meant that even when in STT a fired Fox 1 would not give a missile warning and this was by using data link. Considering that the Phoenix which is of the same era, is a fox 3 and made by a country with more technology, and the missile uses DL then why would it not be possible for it to track without a missile warning using SARH/DL. FWind posted information to the contrary of your claim that the Phoenix use SA-CW, as far as I know SA-CW is for the AIM-7. You see the confusion here I hope.
  23. Where does HB state that the target should get a launch warning from PD-STT (SARH/DL). That would settle the argument don't you think and since I have not seen this when reading the HB manual so can you link it please? Thanks.
  24. Again were is the documentation to support that data link to the missile is the same frequency. I did not say then data link was on a radio, I said it is a diferent frequency as far as I know. Again, were is the documentation.
×
×
  • Create New...