In search for the Ultimate Tomcat...

As I design FSX add-ons for fun, when the projects come to the final polishing stage (which is very boring) I tend to lose the focus on their completion, and usally start working on other things.

Which in this case, as some of you are aware of, would be the T-45C update.

I've been playing with the new Goshawk for some time... but I have to confess that I could not get it right. That is, there are so many things I'd like to change that I grossly underestimated the amount of work. I've also considered buying professional 3D data to speed up thing... but apparently there is no data available. So I am not so sure it is the right thing to do, right now.

On the other hand, while looking for a T-45 3d mesh I found some nice meshes for the Tomcat at a reasonable price... Played with the 3D yesterday night and the results were really good. Long story short I am putting the T-45 on hold and make a new version of the Tomcat first.

So, the status of my projects is as follows:

F-35A Lighting II
I've almost finished remaking the MFDs. Then I have to finish a couple of repaints and the external weapons model. These are the last outstanding items in my to-do list, apart from a final round of tests - just to be sure everything works.
As for the release...it will be release as soon as I've finished moving into my new home - and the new home is connected to the internet.

T-45C Goshawk 2.0
Delayed. Simply put, it is not coming as nicely as I hoped - and requires much more work than I thought. I have to think about that (...and find the time to read the Natops - thanks Phil)

F-14(D?) Tomcat 2.0
Warming up the engines. Initial work with professional 3D mesh is VERY promising. Undecided between B and D versions. It will be freeware, but may be will have payware additions (to cover the cost of the mesh license) - meaning that the base package will be freeware, and "optional" features (like different weapon loads) could be payware. Or a freeware "D" and a payware "B"... I don't know. Still, trust me, the preliminary build is looking very good.

TA-4J Scooter
Project evaluation. Well, the fact is I want to do a top-notch naval jet trainer - and I'm considering the TA-4J as replacement of T-45 - you know, in virtual reality you have the time to run backward :-)
It is just an idea, for now, but I'll probably make some preliminary work on it - if it will look good, I may decide to do this instead of the Goshawk...

Unhappy with the F-14...

I think that product quality and developer satisfaction do not come together... I know the T-45C and the F-14D are not bad for being freeware... But I am not happy about them. That is, the more you work and the more your skills improve, and the more you learn about your modeling subject.

And then... I am also never happy with what I do, and that is the main reason for the F-35 delay - for example I just started the third version of the MFD.... which is kind of stupid, given that the previous one was working almost perfectly...

Yesterday, during some F-35 flight tests, I took the old Turkey for a spin... and was unhappy. There are several small things that could be improved, let alone the fact that rebooting the F-14 with my current skills, and possibly starting from professional 3D data like I did for the F-35, could bring a much better model.

So, long story short I am considering an update/reboot of the F-14, too. I am undecided between a quick update to the existing model, or a major rework.

Some things I do not like ad that could be fixed in a quick update (say maximum 10 hours or work) are:

- Decent afterburner effects. I think the F-35 ones are much better, and I could do similar effects for the Tomcat.

- Collimated and perfectly translucent HUD.

- Minor glitches to the external model

On the other hand, investing like 200 Euros in professional 3d data and at least 200 hours in modeling / integration with the existing Tomcat model (i.e. reusing the good stuff) could bring a much better model...

What are your opinions? What should change and what should stay the same?

F-35 project update...and other things.

It is quite a busy period for me (...well...as always!) but I'm doing my best to complete the F-35 soon. The most time-consuming thing, for me, is that I'll be moving into a new house in the next few weeks... which, for you, means another potential delay in the F-35 release (due to the fact that it may take few weeks to activate the internet connection in my new home)... Still, rest assured that the F-35 will be released as soon as possible.

This blog

As you may have noticed, the AdSense banners are gone (their decision, not mine). While the reason for the suspension for the ads was unclear, I think it was due to the fact that I was suggesting to click the banners - which is against the AdSense rules. My fault - I had not read the AdSense policy carefully. It was not my intention to cheat or anything. Also, as I had not read my home e-mail for a while, I've missed the 72 hours time limit that AdSense gives you to fix your site. I've filed an appeal but as it was my fault it is likely that the ads are not coming back.

Not a big deal for me, although I appreciated the fact that the advertising paid for full access to airliners.net, for example... Anyway, I just wanted to let you know that those empty boxes you see are, in fact, empty. Will rearrange the layout of the blog asap.

F-35 Lightning II

It is almost done, meaning that it is already at least as good as my previous project... but as I was not satisfied with the MFD "interface", I am extensively reworking it. It will be closer to the actual F-35 in both graphics and functionality, although still not as customizable to the real one and given some artistic licence for FSX limitations and playability.

I've made some minor changes to the flight model (with thanks to Roberto Leonardo for providing major improvements to the Alpha and Beta1 versions) and the external models are done - with exception of the launchers and the external loads (with should not take more than a couple of hours to make).

So, the big unanswered question is the release date.... and I have no clear answer, yet. The Beta 2 / (potential) RC1 is just few work-hours away, but the actual release date will also depend on when I will have the internet connection in my new home.

T-45C Goshawk 2.0

I had very good feedback on the "T-45 Goshawk 2.0" project. I've received the .pdf files for both the T-45A and T-45C Natops (thanks Phil) and placed them in my documentation folder - together with almost every Goshawk file available on the internet.

The only thing I'm missing right now are good, hi-res pictures of the cockpit - I have some (the ones I've used in the current release), but are not as good or as complete as I'd like.

Also, I've received some appreciation e-mails from former and current T-45C pilots, so the new version will include "first hand" feedback. By the way I was happy to hear that they found my FSX rendition to be realistic - although I've learned that in most cases, real pilots are more forgiving than other users, in terms of simulation realism... I think it is due to the fact that they realize that FSX is, afterall, just a game :-)

F-14D Tomcat

There is some chance I will make a small update to the Tomcat before reworking the T-45C. While I am not satisfied with the F-14, and while I know it can be vastly improved, there are a couple of issues with the latest release that can be easily fixed. Also, I'd like to apply some of the "tricks" I've learned making the F-35... We'll see...

By the way, seems that the download links from rapidshare are broken. Will fix that too, although you can find the Tomcat at flightsim.com.

E-mail

Unfortunately I had no time to reply to many of the emails I've received in the past few weeks -my apologies. I tried to reply to the most urgent ones - and I will reply to the others asap

That is all for now. In the next post I will provide some hi-res pictures of the latest F-35 build.

Real AF-1 ready to fly at Edwards (and F-35 drop tests)

F-35 AF-1 with final painting/finishing. Will fly to Edwards soon.

In the past few weeks, the real F-35 project achieved several major milestones, including first vertical landing for the F-35B, first flight of a fully mission-equipped plane and drop tests of the F-35C. Now the AF-1 is back from the calibration lab and received its final livery (which looks close to the one I did based on drawings - the major difference is that the real characters are smaller).

By the way seeing the F-35C drop test videos (link below, also on youtube - and good source to estimate F-35 carrier landing parameters) reminded me of drop tests we did when I was working for major mobile phones company... but on a much bigger scale!

Sources:

AF-1 Completes Final Finishes, Scheduled to Return to Flight

http://www.lockheedmartin.com/news/press_releases/2010/100413ae_af-1-final-finishes.html

First Lockheed Martin Mission Systems F-35 Enters Flight Test

http://www.lockheedmartin.com/news/press_releases/2010/100407ae_f35-mission-systems-flight-test.html

Lockheed Martin's F-35C Lightning II Carrier Variant Undergoes Drop Testing

http://www.lockheedmartin.com/news/press_releases/2010/100409ae_f-35c-drop-test.html

F-35 Lightning II - project update (finally) and some screenshots

My apologies for not having posted any update on the F-35 recently... I had not much time to work on it, and I am also at that point in which you keep on making small, almost unnoticeable refinements... and you are never happy with the results.

Anyway, at present the external models for the AA-1 and AF-1 are done. The operational F-35 still needs some modeling/texturing, while the "clean" texture set is done. I'm also tinkering with a couple of other repaints.
The Virtual cockpit is, finally, almost bug free - some MFD freezing still happens, but it is very rare on my machine. Also, I've been working with Jitko Rusev to improve the Virtual-HUD resolution and appearance - with very good results IMHO.
Flight model is also almost ready - with thanks to Roberto Leonardo who provided several improvements and corrections. I'm making some very minor changes here and there...but I am pretty happy of the flight behaviour.

As for the release date - well, its done when its done. I think this project needs roughly 20-25 work hours to be considered "complete", but I really can't tell when I will find that time.... hopefully the release is just few weeks away - I really don't know.

In the meantime... here are some screenshots:

AA-1 model is complete...

...and so is the AF-01 model (this livery is based on a CAD image from LM, AF-01 actually took flight mostly unpainted - I have the "unpainted" livery in the works... but its quality is not on par with the rest of the package, so I'll leave it out - unless I find the time to improve it)

This is the "clean" livery for repaint. No paintkit is available (as I use the photoreal approach) nor it will be - my apologies to repainters... Still, I hope this "clean" texture set will help in making new liveries.

At least three visual models will be included: the AA-1 (initial prototype), AF-01 (weight optimized prototype) and an "operational" F-35 (with proper EOTS and weapon lauchers, and without nose probe). I am also considering adding models with external loads.

Above are a couple of pictures of the new afterburner effects - much better than the Beta 1, IMHO - and hopefully less prone to fx"bleeding" (i.e. special effect misplacement that happens, in FSX, on some machines - usually it disappears by setting the graphic card to "maxiumum quality")

Here is the current cockpit - Most of the bugs of the Beta1 are gone. I'm relatively happy with it - but I'd like to add a couple of functions before the final release.

F-35 Lightning II - Closing Beta 1 testing

While I had not much time to work on the F-35 lately, I've already made several changes - and tried to fix the defects of the Beta 1.
My current "internal" build is now significantly different from the Beta 1, which is to be considered out-of-date.
I will keep updating the Beta 1 WIP post as reference (link below - please note it is not up-to-date in the moment I am writing):

http://indiafoxtecho.blogspot.com/2010/03/f-35a-beta-1-test-work-in-progress-post.html

At present, the only thing I am unable to fix is the occasional "jamming" of the MFD - the associated XML code seems correct, and the root cause seems to be a FSX "delay" in passing some internal parameters between the gauges... I will try changing the code once again, as soon as I will have the time - but chance is that this defect will be there at the time of release.
By the way, before the product is released, I will publish a document with a complete list of known inaccuracies and defects. The product will be available for download on a "no refunds" policy, which is common practice for many e-commerce sites. While I do not like the "no refunds" attitude, there are no practical ways in which I could support refunds. The best thing I can do is to give to potential customers the most accurate and complete information I can provide.

Here is an updated project schedule (realistic best-case scenario):

03/21 - Closing CR's for Beta 1
03/23 - Start AF-1 and F-35A model conversion
03/31 - All models complete
04/04 - Submit Beta 2 for final checks
04/11 - Create final build
04/15 - Submit to e-commerce sites

And while the virtual F-35 is late... it seems that the real one is making huge steps forward: the VTOL version is moving towards vertical flight test - currently slows down to 40 knots!

http://www.f-16.net/news_article4027.html

UPDATE:

F-35B achieves first vertical landing!
http://www.lockheedmartin.com/news/press_releases/2010/100318ae_f35b-vertical-landing.html

other videos (short take-off, hovering) here:
http://www.lockheedmartin.com/products/f35/index.html

F-35A Beta 1 test Work-in-Progress post

*********************
NOTICE TO TESTERS
I noticed from the test reports that there is a misunderstanding on how the new HMD should be used. The new HMD does not require the SHIFT+1 superimposition - doing so will be confusing and redundant.
There will be, in the final version, a simple superimposition of some information (e.g. mock weapon status) to give the "feel" of an HMD... but flight data will be fixed in space in front of the A/C. This is also the way it works (afaik) in the real plane - only some tactical and weapons information (and night vision) follow the head movement. The rest is fixed like a HUD - with an exceptionally wide FOV.
***********************


Below is a list of issues either known or found in the Beta1 build as released to testers tonight. This list includes only the "accepted" issues - i.e. things that I acknowledge as actual defects (if compared towards the scope of the project).
I will keep this list updated, as reference for me, for the testers and also for anyone interested in the project progress.

Note to testers: no need to rush - I won't have much time until the next weekend. While evaluating the flight model, please keep in mind the fact that the aircraft is loaded with two JDAMs.

UPDATED 16-03-2010

External model:

1) Nose gear door does not close perfectly. STATUS: CLOSED - there was a glitch in the animation sequence, fixed on model build 48.

2) Fuselage/engine nozzle do not merge as they should. STATUS:CLOSED - modified nozzle 3d model on build 49

3) Nose gear - one piece of the old nose gear structure is still visible. STATUS: CLOSED - deleted on model build 49

4) Right Slammer misplaced. STATUS: CLOSED - Fixed on model build 49

5) Visual interference of main wheels into gear doors. STATUS: CLOSED - Fixed on model build 49

6) Pilot reflection on canopy glass is too strong (especially evident with canopy open) - STATUS:CLOSED - minor issue, but enhanced glass transparency so that the effect is less evident on model build 49

7) Uneven brightness of the A/B base textures. STATUS:CLOSED, minor issue but a/b base texture redone.

8) Shiny engine surfaces in A/B area do not look good (depending on lightning). STATUS:CLOSED, shiny attributes removed from engine inner surfaces

9) Asymmetry in the slats position. STATUS:CLOSED. There was a mistake in the animation tags, fixed

10) Slime lights offset from the tail surfaces. STATUS:Closed. Fixed position of the slime light polys - a small gap is still visible under certain conditions (gap is present to avoid clipping issues).

11) Nose gear Y-bone and landing lights are too high. STATUS:Closed. Lowered the 3D objects a little.

12) Missing guiding features from the refuel receptacle. STATUS:CLOSED. Action: redesigned refuel receptacle area - still not 100% accurate, but should be much closer to the real design.

13) Lights position/strobe/white nav light. STATUS:Open. Lights position is being changed. Some unintended reflection on the fuselage is possible due to FSX default effects (evaluating custom light effects). Nav white light missing as I could not identify its actual location. Strobe missing for the same reason.

14) Wing vortices location mismatch. STATUS:CLOSED. Action: Roberto sent a file that fixed this issue. Thanks Roberto.

15) Afterburner effects bleeding through the engine nozzle. STATUS: Open. Action:unclear. This is not usually not due to a model or coding fault, but it is due to two things: 1- Misplacement of .fx graphic effects by FSX (happens to various amount on all systems) 2- User graphics driver setting to "performance" (instead of quality) will create major bleeding. I will rework the effect a little, but bleeding may still appear on some systems, depending on setting and drivers. EDIT: redesign of the .fx system should significantly reduce the bleeding.

16) Afterburner effect does not extend much beyond the nozzle profile. STATUS: Open. Action:Complete redesign of the afterburner effect. Now extends beyond the nozzle with a nice halo - afterburner stages are preserved. A little tweaking may be needed for stage 2 - currently too yellow.

17) Oxygen mask animation sequence incorrect. Oxymask floating in the air from time to time. STATUS:CLOSED. Redone specific animation sequence. Still, not 100% fixed as it would required a skinned (non-rigid) mesh - but should be much better in most cases.

Rejected CR's:

- Enhance detail of the nose probe. Reason for rejection: changes would not be noticed by the majority of the users.

Virtual cockpit:

1) MFD pages may occasionally jam. STATUS: OPEN - after several attempts the situation is much better, but still happens. Action: Not sure if I can completely fix it. User can reset the MFD or reselect the page - and this usually fixes the issue. NOTE: Most users do not experience this or do not feel this as a critical defect. Status turned to yellow.

2) ICAWS mode inop. STATUS: CLOSED - Added ICAWS code to XML gauges

3) Incorrect light switches operation. STATUS: OPEN - Action: modified XML tags associations

4) Miscellaneous mismatches of the FUEL MFD page. STATUS:CLOSED - fixed .XML graphic and text calls had left to right mismatch...

5) A-ICE button inop. STATUS:OPEN. Action: add missing code. It is unclear what the real function should be - in doubt, the switch will activate all the anti-ice systems of the A/C

6) A/P: unnecessary bank control code. STATUS: CLOSED. Removed code completely.

7) A/P: missing VVI control code. STATUS: CLOSED. Reworked A/P layout and added requested feature.

8) A/P: A/T trigger not working. STATUS:OPEN. Action: unclear. I may be missing some essential entry for the A/T... since my FSX planes all suffer from this issue.

9) MFD:Graphic "ghosts" in the ENG and FCS pages (and misc.malfunctions). STATUS: CLOSED. It was a side effect of double gauge calls (implemented to limit the jamming issue). Double calls removed.

10) HUD/HMD: Optimize resolution and color. STATUS: CLOSED. Now it looks as good as it can be :-)

11) HUD/HMD: VTOL icon appears when the HOOK/STOVL button is pressed. STATUS:OPEN. Action: this would be correct for F-35B - should be removed from F-35A .

Flight model:

1) Microoscillations when the plane is still. STATUS:OPEN - due to contact points instability - it was fixed on aprevious build but it is back in the latest. Action: Check contact points / aircraft .cfg

2) Minor yaw instability. STATUS: CLOSED. Action: while there may be some margin for further improvement, latest flight model is much less prone to yaw instability. Thanks Roberto.

3) Turn rate may be too good. STATUS: CLOSED. Action: latest flight model show a less optimistic / more realistic turn rate... still, this is, of course, the best guess we can. Thanks Roberto.

4) Potential minor tweaking needed to aileron / elevators effectiveness (slightly unresposive in some areas of the flight envelope). STATUS: CLOSED. Modified aileron effectiveness.


Color key:
Green - issue solved, or mitigated to the point is acceptable or not perceived by most users.
Yellow -issue open, and could be perceived as product defect by many users. Awaiting action or investigation. Or issue open, mitigated to the best of my knowledge but will still be perceived as defect by users. Or issue open but appears easy to fix.
Red - root cause not identified as of today. Or the problem is beyond my knowledge or impossible or difficult to solve.