Bug Reports!!!

[JamesChams 108]

UPDATED:

Aerosoft Staff,

With all the different bug reports being posted it is hard to keep track of all of them. Would you consider making a forum just for that?

If so, please include these minor issues:

1. For F-16C Hellenic AF, 528, 337 Mira, Larisa AB configuration file ATC ID = USAF 678 ; shouldn't it be *Greek* Hellenic Airforce 528 or AIR FORCE 528?

2. NAV1/ILS on HSI/MFD-HSI do NOT coincide even if setup to be both using NAV1.

3. Tail Light burried under chute.

Thank you.

These were posted by me earlier in different thread:

(CLICK the following links)

1. 4 Major Issues

2. HUD.xml Color Issue/Solution

3. Flight Envelope Problem/Solution

PS: I'm using the v1.01 with FSX Acceleration on a VISTA 64 machine.

Finally, I want to thank all of you for making this awesome FSX model. I look forward to all the fixes and FINAL BOXED RELEASE.

[Guest Dag]

Man, that's the first time I've seen an ATC ID posted as a bug

BTW, you should not change the ATC flight number if you want an accurate SMS display...

[JamesChams 108]

Dag,

Yeah, Mr. Kok will probably poke fun at me and name it after me; but, I'll leave it all up to you/Aerosoft to fix ...

I won't change my model except to test/fix your suggestions; With one exception the .cab files with the updated HUD.xml.

Thanks for the SMS info.

[Aerosoft Team [Inactive Account] 51562]

Dag,

Yeah, Mr. Kok will probably poke fun at me and name it after me; but, I'll leave it all up to you/Aerosoft to fix ...

I won't change my model except to test/fix your suggestions; With one exception the .cab files with the updated HUD.xml.

Thanks for the SMS info.

Keep in mind that not all you send are actually bugs, some issues have not been implemented and will never be implemented for several reasons. To keep it simple, if it is not described in the manual it most likely is not simulated. From memory hud brightness settings, some buttons on the MFD etc were mentioned by you but simply will never be included. Other things are impossible or near impossible to fix.

[JamesChams 108]

Keep in mind that not all you send are actually bugs, some issues have not been implemented and will never be implemented for several reasons. To keep it simple, if it is not described in the manual it most likely is not simulated. From memory hud brightness settings, some buttons on the MFD etc were mentioned by you but simply will never be included. Other things are impossible or near impossible to fix.

Thats fair; but at this time, with all the posts, of the few *bugs* that users are reporting; it is impossible for *us* to discern which is which.

However, I do hope that you will at least implement the functional/simultainous use of the MFD's for Navigation (e.g. use a HSI on Left MFD/GPS Map on Right or review stores on Right MFD and MAP on Left MFD) and the need for loading approaches into the flight plans; this kind of functionality is a necessity for the overall navigation. That feature is a must, in my opinion, to go along with your sales pitch "... this model is all about flying the Bird."

Thank you for your time and attention.

[Finn 873]

The real F-16 doesn´t have a database with approaches, SIDS or STARS, infact it doesn´t have a GPS system that displays what most people think.

It has a GPS reciever hidden somewhere inside the fuselage. This GPS unit updates the inertial reference system, wich is the prime system for navigation.

During developement we found that the current blocks and upgrades not even have a moving map like the Aerosoft F-16 features.

It don´t know nothing about VOR, ILS or Navfixes.

What it is able to how is tactical information like flightplan (simply the route between waypoints made up of latitude and longitude entries), FLOT line (line between friend and foes), Prplanned SAM sites with range rings as well as freefire zones and datalinked objects from AWACS, JSTARS and other F-16's.

Most of the above mentioned items can simply not be implementet within FSX.

Due to the fact that most of that stuff can´t be displayed on the MFD, using FSX, we opted to include the moving map (something planned on the real F-16 Block 60). AI aircraft shown outside what resembles the onboard radar cone can be considered datalinked objects from Your fellow F-16 wingmen, AWACS or JSTARS, where ever they are hiding within Your FSX airspace.

What Scott has achieved with those MFD's is, in my eyes, the closest possible way to simulate the real MFD's plus some extra stuff to make up for what is missing.

Finn

[Zaltys 0]

Nice work on aircraft and it's cockpit! It's shame that most features can't be impemented inside FSX!

I've found one more bug with air brakes indicator - as far as I know, it shows dots when air brakes are open and stripes when air brake is closed. Currently it's vice versa.

[JamesChams 108]

The real F-16 doesn´t have a database with approaches, SIDS or STARS, infact it doesn´t have a GPS system that displays what most people think.

It has a GPS reciever hidden somewhere inside the fuselage. This GPS unit updates the inertial reference system, wich is the prime system for navigation.

During developement we found that the current blocks and upgrades not even have a moving map like the Aerosoft F-16 features.

It don´t know nothing about VOR, ILS or Navfixes.

....

Finn

Thank you Mr. Finn; I'm aware of the real aircraft's GPS functional capabilities and FSX's inability to do TACAN and/or limitations in using INS/IRS systems.

But, since you've stated that your/aerosoft's F-16 MFD's are FSX "Type" MFD's, could you include that as part of the Flight Planner? So, (e.g.) if I use FS' ATC I can do a GPS procedure approach and see the approach path/fixes on the MFD Map page. That would enhance the FSX MFD for functionality and navigational flyability. And that's really what I'm saying. Also, the features I'm describing are embedded in US Naval F-16N's after the 1990's.

Also, Mr. Scott has indicated to me that he is already aware of the gauge *bugs* and he's working it out.

Thank you.

[Aerosoft Team [Inactive Account] 51562]

Nice work on aircraft and it's cockpit! It's shame that most features can't be impemented inside FSX!

I've found one more bug with air brakes indicator - as far as I know, it shows dots when air brakes are open and stripes when air brake is closed. Currently it's vice versa.

Damn, you are right. We'll add it to the list.

[Aerosoft Team [Inactive Account] 51562]

Thats fair; but at this time, with all the posts, of the few *bugs* that users are reporting; it is impossible for *us* to discern which is which.

However, I do hope that you will at least implement the functional/simultainous use of the MFD's for Navigation (e.g. use a HSI on Left MFD/GPS Map on Right or review stores on Right MFD and MAP on Left MFD) and the need for loading approaches into the flight plans; this kind of functionality is a necessity for the overall navigation. That feature is a must, in my opinion, to go along with your sales pitch "... this model is all about flying the Bird."

Thank you for your time and attention.

Sorry at this moment we can't do any cross functioning of the MFD's. We tried it but it just puts too much load on the FPS, even when displays are not shown they partly run and that's just too hard. The main cause of this is that the both MFD's have been started as separate systems and not as one unit, a mistake that is not too complex and expensive to solve.

[Guest Dag]

Damn, you are right. We'll add it to the list.

I would double check and then check that again if I were you Mathijs.

Edit: Yes, dots open, diagonal stripes, closed. How the fart did we overlook that??

[Finn 873]

I even looked at it during the implementation of the Speedbrake script, but didn´t notice either !!

Bummer or ?

Finn

[saprintz 82]

Sorry at this moment we can't do any cross functioning of the MFD's. We tried it but it just puts too much load on the FPS, even when displays are not shown they partly run and that's just too hard. The main cause of this is that the both MFD's have been started as separate systems and not as one unit, a mistake that is not too complex and expensive to solve.

To add a little to what Mathijs said, for us to properly do the "swap" feature (and to allow any of the MFD pages to be on either MFD at once), the logic would basically require that there be four GPS gauges at once. Not easy on a system, as you can imagine. Still, I'm currently reviewing this again to see if there's any way at all that we can provide more flexibility with the MFD's, like which pages can be where and in what combination. But realistically, adding NEW features has got to be second priority behind fixing the features that are already in there. So... just please keep that in mind.

Thanks,

Scott

[saprintz 82]

I would double check and then check that again if I were you Mathijs.

Edit: Yes, dots open, diagonal stripes, closed. How the fart did we overlook that??

Heh... I'll tell you how Dag. We get so caught up in the absolutely tiny (some would say insignificant) details that we sometimes lose sight of the BIG ones! Been there myself. ;-)

[JamesChams 108]

Gents,

Well I have faith in you guys, that you'll fix it all and make it all work out quite nicely; even you Dag; that is, after all the "buming and Farting around" is all over... But I guess that you'll need that to celebrate your success and hard work thus far. Keep up the good work!

Now I'll leave you guys with these issues and let you work them all out and perhaps others issues too; Signing out now!

[JamesChams 108]

POST (SP1) v1.10 Bug Reports

Staff,

These are a few things that are currently Bugs in SP1 (v1.10); Hope you can fix these as well.

1. When All lights are turned ON:

a. The Anti-Collison Lights and switch are NOT ON; I have to manually turn them on in "Ready to Fly" Mode.

b. The Landing light remains ON (Lit), in the VCockpit and outside the aircraft, after gears are raised.

c. Tail light out of position in some models.

2. Aircraft.cfg file data, for Tail/Flight Numbers and Callsigns, don't match texture sets.

Thank you for your attention.

[Guest Dag]

Re cfg entries; you'll loose SMS stores if you alter the ATC flight number. For the "airline" entries, maybe you are able to alter them yourself, you seem capable enough with the amount of stuff you post ??

Anti collission light is normally turned on when rdy to taxi, you should possibly be able to do that yourself?

[JamesChams 108]

Roger Mr. Dag!

I can manage some things by myself and leave the rest up to you "wizard developers" to fix.

Also, Here is one more I found accidently. Missing textures for the canopy and weapons.

Tusen takk

[Finn 873]

Regarding the landing lights visible after gear has been retracted.

I think to remember that You use the Shockwave redux lights James...

make sure that You have enabled the shockwave gauge in the panel.cfg's found in:

\Aerosoft F-16A 9\Panel\ and \Aerosoft F-16AM Display\Panel\ folders.

They should read:

....

......

gauge07=MFD!RMFD, 182,310,165,170

gauge08=VIPER!ex_light_control, 0,0,1,1

gauge09=VIPER!AS_Mastercaution, 0,0,1,1

gauge10=VIPER!Eng_smoke, 0,0,1,1

//Remove slashes when using shockwave lights

gauge11=shockwave_lights!SW Lights_gear, 1,1,1,1 //shockwave light

^

Remove slashes //

I will look into the tail light issues, but if You could bring me a list about wich one are having the issue it would help alot.

I will also take a look on the missing textures for the Shaw F-16's stores.

Finn

[JamesChams 108]

Thank you Mr. Finn,

I will put together a full list for you and post it shortly; But, the Shaw AFB and Syracuse NY models still have the tail light misplaced in this posting.

BTW: Thanks for the REDUX Panel Light Fix. How did I miss that

Regards,

[Guest Dag]

Hi Finn,

Go to the aircraft folder in question (F-16C 120-9-12-370-184-28) and look up the Shaw texture folder. Paste in the texture.cfg from one of the other texture folders and you'll have the textures in question showing. The line no. 1 in the fallback is wrong.

Taillight fix:

light.7 = 3, -19.70, 0.05, 2.80, fx_f16_formation.fx ,

No further "Tusen Takks" please Mr. Chams.

[Finn 873]

Thanks Dag !!

Finn

[JamesChams 108]

POST v1.11 Bugs:

Gents (Developers/Staff),

This is my continued BUG REPORT update list; Hope you guys can continue to fix this bird to make it what it should be with v1.13. Thank you.

1.

2.

3.

4. This one is a REPORT/REQUEST Update listed HERE.

Thank you.

[saprintz 82]

POST v1.11 Bugs:

Gents (Developers/Staff),

This is my continued BUG REPORT update list; Hope you guys can continue to fix this bird to make it what it should be with v1.13. Thank you.

<snip attachments>

Thank you.

James, as to the info on MFD's and HUD, my impression is that you maybe have not experimented enough with what does what and responds to what and what is supposed to show when. Tinker with the knobs more and I think you'll see. Some of the numbers you mention, GPS headings and such, are not matching each other because they're not supposed to. Be aware of what HUD Nav mode you're in.

[JamesChams 108]

James, as to the info on MFD's and HUD, my impression is that you maybe have not experimented enough with what does what and responds to what and what is supposed to show when. Tinker with the knobs more and I think you'll see. Some of the numbers you mention, GPS headings and such, are not matching each other because they're not supposed to. Be aware of what HUD Nav mode you're in.

Mr. Scott,

Please look at it again more closely.... I am aware of the ICP modes and the toggle mode switches; including the one for GPS/NAV1/NAV2 usage in the MFD; But I still get these errors with them configured as the Manual perscribes. If you have a proceedure that you would like to spell out, I will do it for you just for academic purposes; to show you that it is NOT a USER Knowledge limitation issue but a functional defect in the gauges programming. Furthermore, I have done several flights for each mode and have found these issues (See Pic 1. below) to be consistant. Furthermore, I know that some features are not yet implemented and I hope that you/developers (staff) will find the time to address them.

Thank you.