First images of my new T-45C Goshawk

[hey_moe]

My kind of plane. Dino, where do I send the credit card to...Mike

 

[mmann]

For now i will remove the animation (too bad for a carrier compatible aircraft).

Maybe you could name the folders and files so it doesn't conflict with your original Goshawk. That way one could use the older version for carrier flights and the newer version for regular flights.

Regards, Mike Mann

 

[sparouty]

The bad part is that reusing assets from the existing VC screws up the launch bar attach points in the external model (which is weird as they are two different files... but I have experienced all kinds of strange FSX behaviours) so either I remake everything from scratch or loose the launch bar animation.
For now i will remove the animation (too bad for a carrier compatible aircraft).

Hello Dino, Auguri!
You're problem looks like the one I had with my launch attach points.
We talked about that by mail many months ago (may be one year?).
One of the explanaition I though about was a conflict due to an effect attached point included into the VC.
There are a lot of mysteries with attached points ... For instance, I noticed that every effect attached point of the exterior model is shown up from the VC view: the 2 .mdl are not so independant than I thought (??)

I don't know if it is the reason of your conflict but try to check your VC model and see if no unexpected attached point remains ( a quick Ctrl+F into your .x or .xml file may help)?

I hope it will helps,
Regards,
Sylvain

 

[Dino Cattaneo]

Hi Sylvain

Yes, I remember our conversations about that - thanks!
The good news is that, at present, the problem is gone and the launch bar works - but I was unable to understand the reason why...
One thing that was not clear to me is that the issues seems to depend on the VC model indeed. Removing the VC makes the issue disappear. Replacing the VC with the old T-45 VC makes the issue appear again. The new VC is, for the moment, OK.

Attachpoints seem a little buggy in FSX:A / SDK... and this happens if you use them to tag the A/B effects, too (I think this happens also in the stock Hornet - there is a white light effect in the one of the A/B flames - same thing happens in my Tomcat).

I also have reports of launch bar issues with models that work perfectly on my system - although I am not sure those are "real" (i.e. I am not sure the user is doing what he should)...

For these reasons I was thinking to use a different animation tag for the launch bar - but I'll wait and see if the problem happens again.