

Hielor
Members-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Hielor
-
I also see the "initially slew opposite from commanded direction" with Mavericks in the A-10A. Extremely frustrating.
-
If the weapon impact point pipper is inside the HUD, you're in CCIP mode. If it's at the edge, you're in CCRP mode. To get into CCIP mode, either be low and fast or be in a steep dive.
-
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
Great to hear, thanks! -
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
I don't think these threads should've been combined...this thread was talking about other issues as well... -
Looks to me more like it is an actual particle effect, but with a very limited number of particles. As you're firing, new particles get made, and the oldest ones disappear, so the trail doesn't go very far back. Once you stop firing, the last set of particles remain until they would normally disappear.
-
Su-25T campaign mission ATO-C-P2.4 has incorrect goals
Hielor replied to Hielor's topic in Su-25T Issues
Good to hear, thanks! -
How do I know how many activation's I have left?
Hielor replied to Dudester22's topic in DCS World 1.x (read only)
Is this something that Steam users need to be worried about, or is it handled automatically? -
Can the server-specific discussion please get moved elsewhere and keep this thread just for discussing issues with SEAD itself?
-
I just failed this mission (Su-25T "Georgian Oil War" campaign mission ATO-C-P2.4.miz) with a score of 40 despite successfully passing the recon objectives, getting the recon completed messages, and taking out a couple of groups of ground vehicles. Looking at the mission in the editor, the mission goals are incorrect. For the recon objectives, they use "Unit inside zone" for the player aircraft for each of the recon zones. As far as I can tell, these goals only trigger when the unit is inside the zone when the mission ends, which means you don't get any points if you've just passed through the recon area during the mission. So, if you fly into one of the recon zones and end the mission right there, you'll pass with 51 points, whereas if you overfly both and RTB you'll fail with 0 points. I checked another recon mission in the campaign and it didn't have the same issue. It sets a flag to true when the player passes through a zone along with printing the "recon objective completed" message, and then checks the flag state at the end of the mission. A simple enough fix. The score system is already rather opaque to the player, and things like this can be really frustrating when the player runs into them.
-
Right, I get that now--I was just giving my uninformed thought process that led to the attempt. In my test, the missiles seemed to blow up as expected over the top of the Gepard, but left it with 10-50% health remaining (according to the map). I'll give it another try, both in the Steam version and the standalone version, and will post tracks if I'm still having trouble. Yeah, this is what I'll be doing in the future. ELINT to find the things, Vikhr or -25ML for the kill. Thanks for he help.
-
Thanks for the reply. DCS is updated. I'm using the Steam version, and it was auto-updated to the newest version some time ago. That information not being in my post was my fault--I'd written the post first on my phone and included it, then my phone's battery died and I forgot to re-include the information when I re-wrote it. But yeah, DCS is updated to the latest version. Please actually read my post. I get that you're very knowledgeable about the game, but it's not helpful when you post your (copy/pasted?) reply that misses a couple points of my post. First off, I was attacking AAA, not SAMs: Second off, yes, at least when used against Gepards the missiles can still overshoot. Saying that the missiles "never overshoot" is a little silly when I just saw them overshoot during the campaign two days ago, and also saw a -58U overshoot while testing last night when I posted the edit. Do you need to see a track of the missile overshooting to prove that yes, it still happens? Are these missiles not intended for use against the radar-based AAA? If that's the case, great, but it would be nice if that information were documented somewhere obvious. The obvious conclusion for someone who's not already intimately familiar with the mechanics is "they have a radar, so I can shoot them with ARMs."
-
So, about halfway through the thread, it was claimed that the issue of-25MPUs overshooting their targets and not missing was fixed, and it hasn't been mentioned since. However, yesterday I was flying one of the missions in the SU-25T campaign, and tried to use 25MPUs against SPAAA Gepards. The missiles sailed over the top of the targets and impacted ~10 meters behind them. Is the issue not actually fixed, or has it been un-fixed recently? Or is there something else I need to do in order to get them to work? I saw mention of missions needing to be updated; has the SU-25T campaign not been updated to fix the missiles? Thanks for any information... Edit: Just tried it out with the mission editor. 4x -25MPUs, one at each of 2 Shilkas and 2 Gepards. The MPUs all exploded directly over the targets, but weren't enough to get a kill shot, except for one Shilka. So I guess, against these kinds of targets, I'm better off with -25MLs on those hardpoints and just using the ELINT to find the things. I also shot a couple of -58Us against one of the remaining Gepards. One of them overshot by quite a bit, the other exploded right over the target. Six ARM missiles to take out two SPAAAs and damage two others seems a bit...meh.
-
Depends on elevation of target. If the target is at higher elevations (in the mountains, perhaps), the laser is pretty much required for the fuselage cannon or rockets. Gunpods appear to do it automatically.
-
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
Unguided Bomb CCIP pipper limited to only part of HUD Previous discussion: http://forums.eagle.ru/showthread.php?t=115622 . Making a thread with a more specific title based on suggestions in that thread. A series of images may best show the problem. The Unguided bomb CCIP: The Rocket CCIP: As you can see, the CCIP for unguided bombs is not currently using the full height of the HUD. Compare to the image in the manual, showing that it did at one point: I did some research into previous versions, and discovered that this was introduced in DCS World 1.2.5 -- the latest version of 1.2.4 has the CCIP for unguided bombs that can use the full HUD, while the latest/only version of 1.2.5 has the limited CCIP. It seems that in 1.2.5 the unguided bomb CCIP was changed to be limited to the same region of the HUD as the cannon's CCIP. However, unlike the cannon, the bombs don't fire forward. Limiting the CCIP this way means that dive bombing runs have to be much steeper, and as a result you're going faster and have less time to react, which makes dive bombing runs a lot more difficult to pull off successfully. Please allow the unguided bomb CCIP to use the full height of the HUD again! -
As seen here: As far as I can tell, water reflections in secondary monitors are based on the terrain visible in the primary monitor, instead of the terrain visible on the secondary monitor. My middle monitor is the primary monitor in Windows, with the right monitor being #2 and the left being #3. The issue repros on both the left and right monitors. I have the options set as follows: - 5760x1080 - Aspect Ratio 5.333333... - 3 Screen If there's anything else I can provide to help find/fix the issue, please let me know!
-
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
Thanks for the tip about using the updater to go back to previous versions. With that method, I was able to determine that the CCIP limitation was introduced in 1.2.5. Update to (latest) 1.2.4-- CCIP is not limited and can go to the bottom of the HUD Update to (latest/only) 1.2.5 -- CCIP is restricted so it can't use the bottom part of the HUD. I also noticed that the pylon indicators were indeed in 1.2.4, so it wasn't changed at the same time. The only SU-25T related items in the 1.2.5 changelist: 1 Su-25T: The gun funnel has been adjusted 2 Su-25T Quick Start mission trigger has been fixed. 3 Su-25: Bombs falling short when using CCRP has been fixed. 4 Su-25: Turning ON the laser rangefinder no longer causes the targeting cross to jump outside the gunsight now. Items 3 and 4 are for the FC3 SU-25, just included for completeness. Not covering the pylon indicators isn't really a good reason to constrain it, since the ability to use the lower part of the HUD for bombing is much more important, and at the point when the CCIP pipper will be over the pylons you would already be in a dive and paying more attention to the pipper than the pylons... Seems to me that this might be an actual bug. Is there a specific procedure for reporting this as such? I wish I could change the title of the thread to be more specific. Thanks for your help! -
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
Thanks for the reply. I've searched through several YouTube videos, and the most recent ones I've found showing the SU-25T dropping unguided bombs (from 5-6 months ago) do show the new way of displaying the active munition, but also have the CCIP able to go all the way to the bottom of the HUD. I didn't see anything in patch notes from the last 6 months talking about the CCIP being constrained to only use part of the HUD, and that's really the larger issue here. It makes dive bombing a lot more difficult than it would have been previously. I also spent some time trying to find videos of the actual SU-25T HUD, but my limited knowledge of Russian means I'm having a harder time figuring out what I should be looking for. Combine that with there being so few SU-25Ts IRL, and all I'm really getting are results from within DCS World. I've only started using DCS World recently, so I can't say for certain when exactly this change happened--but given how much more difficult it makes dive bombing, it seems to me that this may be a bug instead of an intentional change... -
SU-25T Air-Ground HUD doesn't match manual (harder to use)
Hielor replied to Hielor's topic in Su-25T Issues
A little more info: I realized that both the manual and tutorials had the HUDs in Russian instead of English, so I tried switching the cockpit to Russian in the settings, but it didn't make a difference--the CCIP pipper was still limited and the ordnance display was just a couple of bars (and sometimes nothing at all, depending on which station is selected). So, the issue isn't just with the English HUD. -
I recently started trying to use unguided bombs with the SU-25T, and I noticed that the HUD differs from the manual and training videos in a couple of ways that make it much more difficult to use. In game: Manual: As you can see, the CCIP pipper is very limited in the area it can traverse on the HUD--it can't go below a certain point. This makes dive bombing via the CCIP much more difficult, since you have a much smaller angle to work with. Is there a way to get the CCIP to have the full travel of the HUD as shown in the training videos and manual? The other issue is with the display of selected ordnance on the HUD. In-game, you only get bars whose horizontal position corresponds to their pylon. If you have different weapons on each station, it can be difficult to tell which set of pylons are actually selected. In the training videos and manual, there's a much more usable layout that shows all of your pylons simultaneously. I did notice that a number briefly appeared above the bars while the CCIP pipper was active, but due to the above issue of limited CCIP travel you don't get much usage out of this. In addition, the training video shows this display being active even when the CCIP isn't (when it's at its extreme edge of the display). I scanned through recent changelogs and didn't see any mention of this being changed. Was this an intentional change, or is there a bug here? Thanks, Hielor