With the 777, 707, B-52, etc. - I am not sure if there will ever be a 2.5 patch.  I hope I’m wrong, but meanwhile I will attempt to fix what is in my power to fix.

I’m creating this thread as a work-in-progress for the various issues I am attempting to correct.  My goal is to use this thread for feedback and help as I make the corrections.  Once completed, I’ll package up all my work here and update this post with release/download info.

Some of the remaining bugs with version 2.4 reside in the aircraft’s model.  This means only CS can make these changes with the model’s source file.  The good news is some of these issues can be fixed manually with a hex editor, bypassing the need for the source files.

For example, this is how I fixed the Heading Select switch bug in the vc.  Previously, the switch would remain stuck in the ON position requiring the user to open up the 2D panel to shut it off.



In the hex editor image above, the highlighted value is the click event for the heading select switch…it is incorrect.  Instead of reading AP_12_007_SW2_POS, it should be AP_12_007_SW2_POS_CLICK.  Once I made this correction to the model, the switch worked properly.



Another example is the Oil Quantity Test button. It was broken; instead it moved the oil pressure needles when tested.  After some hex editing and a small line of code to one of the gauges…they now work as intended.



Unfortunately, this process is limited and certain issues cannot be fixed this way.  Also, the HSI Nav1 problem needs a totally new gauge that will be able communicate with the 727 "sys logic" in order to get Nav2 information.  I have some ideas as a workaround that I still have to test out....but the only true fix will be from CS.  In addition to this, the pressurization system is FUBAR’d and I probably won’t even touch the thing.  I've changed my mind...will look into the press system.

I’m sure CS would not appreciate me offering modified versions of their model for download.  To prevent this, I will offer these changes via a “byte patcher” installer.  This means my download will only contain the data needed to be changed without containing any of the product’s assets.  Without the original files, the patcher will be useless hex data.

Other issues already fixed:

Black Engine Smoke
Currently, you have to manually activate the smoke system by using the “i” key.  Furthermore, with this approach you get unrealistic smoke that doesn’t take into account if an engine is offline.  For example, if engines 1 and 3 were off, you would still get smoke from all 3 engines instead of only engine 2.

I made a new gauge to correct this.  The black smoke is now automatically engaged based on throttle position.  Also, the smoke is tied to each engine now, so if you lose engine 1, you lose the smoke too.  I can tweak this further based on user feedback.

Properly Working Tail Skid
Tail skid now works likes the real thing (fixed typo also).  Instead of having to manually extend it via the tail hook command; now it automatically extends and retracts with the landing gear.  I’ve also fixed the annunciator light to function like the real thing which is how Lou described it in another thread. Now the tail skid light briefly illuminates while the skid is transitioning from open to close and vice versa.

Other issues to be fixed:
Will be announced throughout this thread as I work on them.

I'm trying to fix the S/O's annunciator panel on the -200 (-100 model is ok).  The "Aft Door" and "Service Door (aft)" presently do not have any indicator lights associated with them when they are open.  Also, the "L Service Door" indicator is broken and not associated with any door. See image below.



I would like to correct this.  If anyone knows about this panel or has the flight manual explaining it...please share. I have some questions:

-Are the current annunciator labels correct?  The reason I ask is the unused indicator is named left service door; I don't see how this label can apply to either of the two doors that are lacking indicators.  I will also have to make a new indicator since we are short one.  If someone can clear up this door/annunciator confusion for me I would really appreciate it.  

-What is the "Cargo V Closed" indicator for?  Presently, I don't see it tied to anything other than the "test" indicator.

CoolP,
Thank you for taking the lead and doing great job. It is essential that user findings  be reviewed and it should be included in 2  FIX Lists. One critical fixes should be listed on your FIX for CS and If can be easily can be fix by members, these fixes should be listed on "Members Fix" list.

Before FIX submitted to CS. Members should review and if any changes between fix lists, it should be reported back to you. Then you and your team can review the lists. If all finalized should be submitted to CS.
CS should assign a developer member (Tina) to your team.

This is my suggestion.

Sanal

Quote:

Very good idea.

The necessary ones depend a bit on the preference.
My list of current ones (which has to be checked, writing this from memory) is:
- 'don't sink' fix
- the one for the MDA light
- maybe the NAV/GPS button (since the GPS popup is there, but you can't connect it)
- FDE mod (I would leave that optional)
- INS mod (optional too)
- DME display tuning (like on the current 707, so you have both DME measurements on each side)
- Sound fix (SoundOffWhenSimIsSlew=0)

I think the ALT rollover is ok in 2.4.
I would love to see the sound gauge fixed without my 'use the 707 gauge' trick. You know, this old bug that the 727 has to be loaded twice to get the switch sounds and stuff.

I can help you on the mod pack if it's offline. But this will take until Monday or so.

Edited:

Thanks for your update on this. I didn't like the wording in the last paragraph though, so maybe you don't mind setting up something like 'I get the impression that the thing is on low/very low/no priority' instead of the current phrase.
The meaning may be the same, the respect is greatly enhanced though.

Don't worry, that would be just a wish of mine and would also make sure to stay fair on the wording side.


Interesting read about the CDI knobs and I was really wishing for a fix there.
I'm a TrackIR user and take some of the FOs instruments into account too. This may be a flight sim special since in the rw a guy would sit there and would also be able to report stuff.
It's neat to have some cross radial setup and watching the own and the FOs CDI for example. Far more accurate than the small RMI in my humble eyes.

Also interesting to read about the severity of the pressurization bug. I could only assume there so far, but your words actually show why it takes time and work.
The DME idea is a good one. Maybe not genuine Boeing, but a nice feature which leaves the user the opportunity to use it or not.

Thanks for keeping us in the loop.  

Captain, thank you for your input here with fixes. Concerning patches - please see calendar.

I hope to correct and / or add:

- Switch strobe lights
- Smoke generated from N2
- Pitch / trim less sensitive, something similar to that of DF.
- Any gauge that identifies the CG
- A table for EPR TKFF/ CLIMB/CRZ or a PDCS.
- Now with modernization of the fleet, it would be nice to update with a GNSS or GPS Trimble, even a simple one, only with VNAV.
- And the hush-kit stage 3, the F40 block.

MatzeH84 wrote on Jul 21^st, 2011 at 8:37pm:

You are aware that 2.4 is out for over a year?
Lets suppose that 4 was a typo of yours and just vote for the next update (after the 757) to be related to the 727 instead of using the old 'I'm a customer and now fix my stuff' tenor.
That doesn't help at other companies too.


Saul Galeno, I suggest to look at the free flight model mod from Michael2 concerning some of your wishes. At least the CG thing and the tables will be items you may love.
Quote:

I don't think that there is a real 727 with the full implementation of VNAV. Only a sort of guidance or rough T/C and T/D calculations may be present.
Some had a early FMC retrofitted, but I think it lacked of true VNAV capability like seen on e. g. the 757, which can fly the plane through all SIDs and STARs with the work of LNAV, VNAV and AT.

If you referred to LNAV instead, you may use the GPS gauge coming with the plane to allow that. You have a clickspot in the VC for that gauge. If you use the small NAV button mod, you are able to couple the AP to the GPS.
This may also work with some addon GPS gauges, but I haven't tried it myself since I'm flying either VOR to VOR or fancy (Lou: 'sissy') INS.
To get the INS into that plane, I did a small tutorial right here in the forums. Looks more genuine to me than any GPS thingy. Personal preference decides.