Jump to content

Recommended Posts

Posted

Nope, I've haven't either.

 

I've entered a heading into TERM options. Doesn't make a difference.

 

The normal HSI LAR zones we have already disappear when you enter the IN ZONE region (as per HUD), the actual IZLAR is completely missing. Nothing comes up when IN ZONE. What drives IN ZONE anyway? I thought it should be the terminal parameters.

 

I've noticed that the 'flight time' indication for a dropped bomb is about 20-30s too long too.

 

No instructions to help us along at the moment.

Posted

afaik the dashed line going through the centre of the HSI is the theoretical max range regardless of impact angle and speed. The big ring is the max range for a set impact angle and speed, and the little ring is the min range.

 

The dashed line (Default To target line, and Predictive Max range) should disappear when you enter the Big ring (In Range LAR).

 

IZLAR should be a trapezoidal shape displayed to show the LAR to achieve the terminal parameters.

 

Again AFAIK,

'In-Range' is shown when within the In Range LAR

'In-Zone' is shown when within the IZLAR

476th Discord   |    476th Website    |    Swift Youtube
Ryzen 5800x, RTX 4070ti, 64GB, Quest 2

Posted
afaik the dashed line going through the centre of the HSI is the theoretical max range regardless of impact angle and speed. The big ring is the max range for a set impact angle and speed, and the little ring is the min range.

 

The dashed line (Default To target line, and Predictive Max range) should disappear when you enter the Big ring (In Range LAR).

 

IZLAR should be a trapezoidal shape displayed to show the LAR to achieve the terminal parameters.

 

Again AFAIK,

'In-Range' is shown when within the In Range LAR

'In-Zone' is shown when within the IZLAR

 

Yep, I agree with all that. So the max range and default to target line disappear correctly. (I’d forgotten that - thanks.)

 

But the trapezoidal shape doesn’t show. I’ve tried entering hdg, angle and velocity for a PP TGT. But nothing. I get the little azimuth line on the target symbol (Not correct terms), but it’s random, doesn’t correlate to inputted impact azimuth. Plus I think that was there before patch.

 

Have you played with flight timers yet and seen hoe accurate they are? or not?

Posted

Plus I’ll add that I haven’t actually got AUTO to release a bomb. Holding the pickle and the release cue passes the fpm, and nothing. All my drops in MAN mode as before.

Posted
I haven't played with times yet not. One thing I noticed is that altought the HSI doesnt have an IZLAR, In range and In Zone are displayed on the HUD as you would expect

 

Yeah, so how’s it calculating IN ZONE. IN ZONE indication appears somewhat dynamically, sometimes straight after IN RNG, sometimes after a delay.

Posted
I've had success with AUTO in TOO, but I just tried PP with Term on one bomb and nothing on the other neither of them dropped.

 

I’ve only tried PP. Looks like an issue. I’ll play more tomorrow.

 

The patch notes state ‘heading is defined for IZLAR’ - does that mean term parameters are suppose to be working. Kinda implies it.

Posted
It does, however I think entering term will brick the JDAM. I need to test that more though

 

I think tomorrow will be day of uploading a few track files with reports.....

Posted

Just tried Auto Loft set for 30 deg. It worked, although I pulled up late. Release cue came down as I was passing 20 deg and JDAM released. It hit the target.

 

No IZLAR either. I thought HSI was decluttered from JDAM options but it wasn't (doesn't even work yet)

Also, I have to verify TTI...

Posted (edited)

I can confirm this feature isn't even close to functional. IZLAR's never appear, heading changes (watch the "tails" from the targets) make no sense (180 degrees and 181 are > 70 degrees from one another), and QTY greater than 1 are ignored in AUTO mode and treated just like manual mode, as in it doesn't plot a solution for all selected bombs, just the currently selected station.

 

Pretty disappointing for an extra month in the oven. I hope they don't think this anywhere near done.

 

EDIT:

Some things I've tested:

1. Impact Angle - does nothing

2. Impact Heading - does nothing

3.AUTO/LOFT in PP mode - does not work. Bombs will never release

4. IZLAR - never appears, no matter what mode or what TERM settings exist

5. QTY - ignored. Only limits STEP function, has no bearing on centroids or bombing solutions in AUTO

 

As far as I can tell, not a damn thing has been added. The HUD now has indications, but it's always towards the current station's target not to any centroid if a QTY > 1 is selected.

 

EDIT AGAIN:

I have a sneaking suspicion the wrong branch or merge point was pushed to production. The JF17 is missing 1/2 of it's DTOSS features. Haven't tested the other modules yet but it looks to me what we got was some point halfway to what was supposed to be released. Pure speculation on my part, but I'd like to think a patch this bad wasn't actually pushed in this state, not after all the rumblings around here lately and the almost month over deadline. I'm nervous to test the AMRAAM and I can't put my finger on it but my the speed or drag seems different, though I don't recall seeing any aero or engine changes in the notes.

Edited by LastRifleRound
Posted
I can confirm this feature isn't even close to functional. IZLAR's never appear, heading changes (watch the "tails" from the targets) make no sense (180 degrees and 181 are > 70 degrees from one another), and QTY greater than 1 are ignored in AUTO mode and treated just like manual mode, as in it doesn't plot a solution for all selected bombs, just the currently selected station.

 

Pretty disappointing for an extra month in the oven. I hope they don't think this anywhere near done.

 

Yeah, my limited testing confirms all that. Not even close to being done. So much missing. Flight times/time to impact all wrong as well.

 

Big disappointment as well. Would be nice to know how complete ED thinks this is. Big WIP still or complete now till 2021.....? Shudders....

Posted

Is it already ok to say "the emperor is wearing nothing" by this time?

There nothing complete about this AUTO at the moment. Perhaps wrong build, perhaps god knows what... But saying it's a complete feature or even a functioning feature - it's a joke.

Posted
Is it already ok to say "the emperor is wearing nothing" by this time?

There nothing complete about this AUTO at the moment. Perhaps wrong build, perhaps god knows what... But saying it's a complete feature or even a functioning feature - it's a joke.

 

Yup.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...