Jump to content

Why is there again no change log


FoxDelta

Recommended Posts

With the same logic all changes on the last OB update were published two weeks ago and the only thing missing i can find is the fuze setting for Mavs needed now to be able to fire.

 

For me this could be included in the "reasonable" category.

 

As a new customer to the Harrier, I couldnt agree more. Its really frustrating to find out that the procedure changed with no notification.

 

I get it, this is the way it was supposed to work before hand, but dang not a single doc was updated - ive read the manual, several times, the relevant pages I found were on 89-93... Nothing about fuzing...

 

TJ

Link to comment
Share on other sites

RAZBAM mismanaged whole process about AV-8B N/A considering we were going to get Harrier finished this December. After that word has been said nothing big came to Harrier and there hasn't been any communication about lack of consistent updates for bug fixes and features to it, many bugs that has been in Harrier since day one are still there.

 

Comparing F/A-18C to AV-8B N/A with bugs is a spit on the developers of Hornet as its been changing quite fast and dont forget Harrier was 5 months old already when Hornet got released.

Link to comment
Share on other sites

This is a hard thread to read.

:book:

 

I'm hoping through all of this, it's become clear to =DECOY= that pretty much a large portion of the Harrier/RAZBAM customer community is simply asking for communications about that which has changed, (with respect to the RAZBAM Harrier), and was pushed out through the sim as each updated release is sent via the typical every-two-week update from ED for the Open Beta.

 

I don't at all read this as a demand for increased physical changes to the aircraft on a weekly basis.

 

A "Change Log" simply lists the changed function or functions which were included in the immediate release that differs from the feature state in the previous release. This is what has just occurred, not what will be in the future state.

 

It is not unreasonable at all to expect that coders and feature engineers are tracking their changes and tracking the expected state of that change/feature from release to release. That's a basic discipline of the job frankly, and not doing so can be a fast track to chaos as a coder.

 

In fact, a Change Log would help us, the "Beta Testers", return better insight and to effect better functional testing of those changes by exercising the systems impacted by these logged changes. In turn, helping said software engineering staff squash bugs more quickly.

 

Things can only get better from here, incremental change takes a while, and we aren't the most patient bunch though we can learn to be. Communication at this level will go a long way to keeping the partnership intact.

 

Thanks for wading into all these challenges =Decoy=, we know it's not easy.

:thumbup:

(1AF) "THUD" | 55th FS



Joint Task Force 1 | Discord

Link to comment
Share on other sites

Remember remember, the 7th of November.

The defects of sidearms are gone.

I know of no reason why in this winter season

Instead of magnums you'd fire your gun.

Lincoln said: “Nearly all men can stand adversity, but if you want to test a man's character, give him power."

Do not expect a reply to any questions, 30.06.2021 - Silenced by Nineline

Link to comment
Share on other sites

who's flying so late through night, so wild?

It's Deadpool +1 both steering their kites.

He's tucked his body secure in its pit,

He holds the throttle and control stick.

 

Wingman, why hide your face in fear?

See you not, lead, the defects near?

The defects in light and defects in sound?

Wingman, 'tis but the snowy ground'.

 

Sweet lovely pilot, come, go with me!

What wonderful games I'll play with thee;

Failures, most surprising, yours to behold.

My coder, for you has put work on hold.

 

Flight lead, flight lead, can you not hear?

What RAZBAM is promising into my ear?

Be calm, stay calm, o wingman of mine;

it's just air, rushing over the canopy fine.

 

Wouldst thou, fine lad, go forth with me?

My testers should royally wait upon thee;

My testers conduct each night their binge fest

Blinding themselves, not doing one test.

 

Flight lead, flight lead, and can you not see

RAZBAM's testers, there on our three?

MY wingman, my wingman, I see it quite clear;

It's just our escort, so grey do appear.

 

I love thee, I'm arouse by thy beautiful dash;

And be though not willing, I'll take thee by crash.

Flight lead, flight lead, he's clutching my plane!

RAZBAM is to me a terrible bane!

 

The flightlead shudders and onwards presses;

the gasping wingman he constantly adresses;

He reaches the SAMS, and begins the runs

He looks on his wingman and sees him shoot guns.

 

:megalol:

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
Link to comment
Share on other sites

I suspect the real issue is that the team don't know when their update will be sent out, so it is better to say nothing than to announce changes that miss the update altogether.

 

But, yes, it is frustrating, to say the least.

 

 

This is a hard thread to read.

:book:

 

I'm hoping through all of this, it's become clear to =DECOY= that pretty much a large portion of the Harrier/RAZBAM customer community is simply asking for communications about that which has changed, (with respect to the RAZBAM Harrier), and was pushed out through the sim as each updated release is sent via the typical every-two-week update from ED for the Open Beta.

 

I don't at all read this as a demand for increased physical changes to the aircraft on a weekly basis.

 

A "Change Log" simply lists the changed function or functions which were included in the immediate release that differs from the feature state in the previous release. This is what has just occurred, not what will be in the future state.

 

In fact, a Change Log would help us, the "Beta Testers", return better insight and to effect better functional testing of those changes by exercising the systems impacted by these logged changes

 

Very well said

 

I agree its frustrating. Its like a game every update to turn on and find the easter eggs.

 

I suspect some of this is true, ED sometimes will post videos or updates about whats coming and the posts dont actually always match that following week with what we get. However I read change logs from other Developers every month. And when they textual change-logs are posted. It reflects exactly what is in the patch and release candidate that I am downloading that day. Not sure where the disconnect is or why its a matter of contention for seriously so long to match these. Also very nice Deadpool lol

 

Maybe January will see a new leaf turned. New year changes and a different set of processes possibly. I do know that several community members have been extremely helpful and on point with file / text / sound fixes for these nuisance bugs that have come the last year.


Edited by Shrike88
Link to comment
Share on other sites

  • Recently Browsing   0 members

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