-
Posts
792 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Muchocracker
-
Mk-20 in CCIP drops several hundred feet short of the CCIP piper
Muchocracker replied to hinapilot's topic in Weapon Bugs
My dude. It's been acknowledged in multiple threads and been told there's a fix coming. There hasnt even been a patch after it was acknowledged yet. Calm down bro. Spam mentioning ED employee's in every thread is not going to make the fix come any faster. You're just being annoying. -
It's always been there??
-
Lightening II TGP Laser Marker Mode (Laser Type)
Muchocracker replied to guitarxe's topic in DCS: F/A-18C
They have nothing to do with eachother but use the same models. The programing that makes all of the systems/interfaces/functions happen individually for each module. -
Sir this is a wendy's
-
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
Watch this -
wait for update Defaults fuzes require action in cockpit to work ?
Muchocracker replied to Anubis_94's topic in Bugs and Problems
wait for the next patch. There are 5 million problems with the avionics side of the house after the new fuses were introduced -
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
bro i don't write the manuals -
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
also accurate to how the jet works. It's required for the TOO entries 1 and 2 to even work for ripple dropping. -
Came with the fusing changes, it's an MC load fault. It happens when you have bombs of the same type loaded with different fuses. They have to be the same.
-
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
Yeah pretty much everything over a year old is out of date. That was when the coordinate handoffs were automatic and constantly updating with no pilot input. -
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
Like i had mentioned. Using SCS towards the tgp and cycling the contrast tracking modes will only make a handoff if there isnt already a designation made. What you're doing really shouldnt even be working as the designation doesnt even actually go away in the first place as seen by the designation diamond still appearing on the HUD. But it hands off when the track mode changes nonetheless. i would consider this a bug. Get in the habit of using TDC Depress. That is the proper way to do it. -
JDAMS and TOO. Not releasing first time and "inzone" errors.
Muchocracker replied to cptmrcalm's topic in DCS: F/A-18C
Because you have a bunch of cuts in the video it's hard to tell what exactly you are doing incorrectly. But to me it seems like you have a misunderstanding of how the designations mechanization works for the hornet. You should not be switching master modes, that does not "reset" anything. For IAM's in TOO mode the coordinates being generated by the TGP line of sight do not get automatically handed off as you move it. When you create a new designation it will handoff the data to the selected bomb, but if you're trying to move the pod around and drop on a new target you need to manually hand off the data to the next bomb with "TDC Depress", or by undesignating and creating a new one. Earlier in the video with the JDAM drops at 11 minutes. You're doing it in a roundabout way by switching master modes. By doing that you're resetting the designation, and then creating a new one by switching the TGP out of inertial track back to area track, which then gets handed off. But you're not doing subsequent handoffs to the next JSOW and it doesn't have coordinates. That is why your second JSOW is not releasing. The mission page is your greatest place to sanity check that the bomb does in fact have the right data handed off to it. You can watch the coordinates get updated here every time you TDC Depress or create a new designation. -
Designation is not a "mode". It does what the name implies. It creates a designation along the line of sight of the TGP or the cursor for the HUD/Radar. It does not auto slave to the LOS of the pod as you move it, and that's how it should be. That is a required mechanization for ripple dropping jdam's in TOO delivery.
-
not a bug GBU - Change the Lasercode in flight
Muchocracker replied to maikchaos's topic in Bugs and Problems
From a cold start i don't think they are. I could be wrong. -
There is. The issue is the on the avionics side in the aircraft. Hopefully it'll get fixed soon. You're never going to get a default that works for everything. Just how it's gonna be moving forward. Set up the fuses you need for the target you're going after.
-
not a bug GBU - Change the Lasercode in flight
Muchocracker replied to maikchaos's topic in Bugs and Problems
It's absolutely correct as is. Paveways are not a smart weapon. All you are doing in the SMS is telling the jet what the bombs are set to so it knows when to yell at you if you have the codes on the pod set differently to the selected weapon -
not a bug Mission 10 BUG or bad trigger...
Muchocracker replied to PhoenixFC3's topic in F/A-18C Raven One: Dominant Fury campaign
That part of the mission worked as exepcted for me. You could be doing something out of order like shooting the HARM. I remember there being a similar issue there in testing with the first HARM shot it would break the mission if you fired before Sluggo does. Play it again for me and post the track file.