-
Posts
236 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Rissala
-
You would be correct. As Viper13 said in his original comment: Now, as you might have seen in testing, the weapon is pinpoint precise. I think the cause might be in that the SLAM-ER flight profile has been mixed up with the SLAM flight profile.
-
need track replay Simulated breakdown or bug?
Rissala replied to pognhek's topic in Bugs and Problems
Do not move until you hear "rearming complete". The "ground crew" needs to reset the stores system etc. -
+1 can also confirm something is wrong with the way the modexes are created
-
Terminal settings, at least terminal true heading, worked on all JDAMs at some point. They attempted to satisfy all terminal conditions e.g making a chicane curve before the target to get the terminal heading. This did however reduce the range of the weapon so you had to take the terminal movements in to account. However, I did some testing today and it seems that terminal settings do not work with any GPS/INS weapon, including the GBU-38. Both PP and TOO were tested with all weapons. Expected behaviour: -Weapon attempts to satisfy the terminal conditions e.g. terminal heading Current behaviour: - Weapon goes for a direct attack to the target regardless of settings. In the track I set a bunker and some containers representing 000 and 330 true headings. JDAM was given a terminal heading of 330. It ignored it and went for the direct path even with enough energy for the terminal setting. Attack heading was about 350, so the change would have been very modest. @Ahmed, I would update the title to: Terminal settings not functioning with JDAM (/JSOW)*. *(they have never been implemented to JSOW) JDAM terminal.trk
-
Yes I agree. It just isn't up to us to decide on what is priority and what isn't when it comes to bugs. We can just hope ED would at least acknowledge bugs/issues when they are pointed out.
-
I hope @BIGNEWY you understand that: The difference between the SLAM needing that final guidance (realistic) and not needing it (not realistic) is very much the difference between it being a fire-and-forget weapon or not. A realistic employment of this missile would require the DL pod and the fighter being inside the downlink radius. Currently, you can just fire and forget 4 of these missiles from 100km away and get out without ever installing a DL pod on your jet. This changes the whole point of this missile in DCS drastically. I have my doubts about the non-existent CEP this weapon has in DCS, especially when it was introduced 7 years before the original JDAM. And again, as Wags already described on his video, this behaviour is not correct in DCS.
-
This is not an excuse to not list bugs. This is why this Hornet bugs forum exists. Also, as I have many many times stated, I am not pushing for immediate action. I'm pushing for the acknowledgment of this bug. (purpose of this forum!?!) Only supporting "nice" and "useful" things gives everyone an unrealistic simulation of the aircraft.
-
This directly contradicts Matt Wagner @BIGNEWY. This topic is about the SLAM, not SLAM-ER. SLAM-ER has this precise GPS accuracy as a feature. The SLAM does not. (Makes sense since the original SLAM was a 90's weapon) (Source: Wagner's video) Or is there something which I have missed after Matt Wagner's video on the subject? Based on his video, this is very much not "correct-as-is".
-
-
I thought it would be obvious but here is a picture of the .trk. Target is set in the middle of the "H". The SLAM itself is probably a better indication of where the precise point is...
-
Target was the center of the helicopter landing circle "H" mark. It hits it right in the middle with pinpoint accuracy. This was done to basically show that it is that accurate with 0 manual guidance.
-
@BIGNEWY Is anything being done about this? The SLAM is being used without the DL pod as a precision guided weapon with pinpoint accuracy.
-
Still an issue in the latest patch at this moment. Pinpoint accurate with no guidance. slam accuracy.trk
-
reported Roland acquisition time is way too long
Rissala replied to Rissala's topic in Bugs and Problems
Human controlled. The AI reacts faster than the CA controlled unit. 10 seconds spent waiting for a lock is very long compared to other controllable units in DCS. Here the reaction time is quoted to be 6-8 seconds which includes the turret rotation and alignment. 10 seconds is more than the entire reaction time for the system. https://wikimili.com/en/Roland_(missile) Yes I understand what the delay represents. Just compared to other systems it is very long. -
reported Roland acquisition time is way too long
Rissala replied to Rissala's topic in Bugs and Problems
Yes of course. The numbers are completely arbitrary with the other systems as well. IMO the 10 seconds is just a bit too much thats all. -
When driving the Roland SAM system, it takes 10 seconds to acquire the target. This seems way too long to be realistic. It leads to surreal moments where a target is slowly turning towards you while you are unable to react even when the perfect shot is lined up. Is reducing it to 4 or 5 seconds possible? (similar to TOR) roland aq time.trk
-
reported TK PRES LO above 20k feet with empty centerline tank
Rissala replied to Nealius's topic in Bugs and Problems
I don't remember getting the warning without external tanks but I rarely fly without them so I could be wrong. -
reported TK PRES LO above 20k feet with empty centerline tank
Rissala replied to Nealius's topic in Bugs and Problems
I think TK pressure automatically means external tanks -
At least forbid the AI BMP's from shooting with very high lead. This is in my opinion the cause of much annoyance since IRL these shots would be almost impossible. In DCS unfortunately they are all too common.
-
Status terminal guidance parameters for JSOW and Walleye/SLAM/SLAM-ER?
Rissala replied to Wizard1393's topic in DCS: F/A-18C
For JSOW it would be extremely helpful. SLAM-ER too -
w.i.p Wobbly Hornet rudder movement on final with light turbulence/wind
Rissala replied to Rissala's topic in Bugs and Problems
Already reported here: Will come with FM remodelling some year. -
This is done currently with scripts in practically all missions even though it should be a basic tool. The default code of 1688 is used in all instances with no way of changing the code. @BIGNEWY since we discussed this in the chat earlier, can you confirm that this indeed is a limitation of the ME currently?
-
All JDAMs have terminal modes, the 31 and 32 are just big and heavy so only moderate terminal maneuvering is possible. Also I am not sure about the accuracy of the angle and velocity setting. The bomb attempts to satisfy individual settings to some degree but with multiple settings set, it just does the heading. Maybe they are more useful with a relase point set and with some high level planning done before the mission. (not really possible in DCS) Who knows...
