• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Dino Cattaneo's F-14D Tomcat version 2.20 release

Dino Cattaneo said:
Good day Emile,

as far as I can tell, there is something wrong with the .fx files (or their textures) - alternate causes may be system running out of video memory (this may cause errors in texture loading) or graphics driver error .
Given that nothing has changed in my model in that respect, and also that I cannot replicate the problem and you are the only user (out of several thousand) that reported this, I tend to believe the problem is in your system.

Affected files *MAY* be (juding from the pictures):
fx_strobe_h.fx and/or
fx_navwhih.fx

they both reside in the effects folder

They both use - which resides in the Texture subfolder of the folder effects:

fx_2.bmp

You may want to try to selectively delete (after backup of course) the files to identify the root cause...
Apart from that there may be specific problems due to video card or video memory... the last Tomcat model is slightly more resource consuming than the previous one.
Click to expand...

Hello Dino ,
I deleted the (I have a backup..)
fx_navwhih.fx
fx_2.bmp

I have created the
fx_strobe_h.fx From the fx_strobe_t45.fx

But same negative result.
More suggestions?
Thanks in advance
 
Good day Emile

it is very hard for me to provide support on this issue as, afaik, you are the only user having this issue.

Two questions:
- have you tried using the default Tomcat files (no additional mods)?
- have you tried the A/C after deleting the files (and with the default files)?

BR

Dino
 
Wingsweep problem

Hi Dag,

As to your wingsweep problems:

First: are you sure you using FSX-Accelleration ??
Because in the wingsweep gauge, I use a standard FSX variable that is ONLY defined in FSX-Accelleration (NOT in FSX-SP2 !).

Secondly:
Make sure that the FSX-flaps function is NOT controlled by an Axis; neither in FSUIPC nor in the standard FSX controller assignments (check this for all your connected controller hardware).
Reason:
Besides the actual Flaps, Wingsweep also uses the FSX Flaps function.
But even the slightest "jitter" on that Axis makes the gauge unusable, because it makes FSX immediately overwrite the flaps-position I calculate/set by the Flaps-position dictated by the Axis position.

If both OK:
Try this:
- Load the F14 (either via the aircraft menu or existing flight on the runway).
- Go into Spotplane view and observe the wings.
- Press the key for FlapsUp (default key: F5) several times.

What you should see: Flaps (if extended) are retracted, and wings should be swept fully forward.
Pressing F5 again may visually cause the wings to be swept back a bit, but this is immediately (less then half a second) corrected to fully forward again by the gauge.

Is this working for you as well ?
If not, what do you observe ?

Note: the F14D always starts up with auto-wingsweep enabled; even if you save a flight with the F14D in manual-wingsweep.
Because the used wingsweep variable is "private" variable which is not saved in the FSX saved-flight data.

Regards, Rob

PS: I don't use P3D, so I can't test this myself other then in FSX-Acceleration.
But from Dino's (and others) report, I can only assume it works as-designed in P3D (1.4 and 2.0) as well; if it wouldn't, a lot of other FSX-designed (flaps-related) functions wouldn't work in P3D too.

EDIT: just noticed that you have this problem in P3D.
So the question on FSX-Accell is obsolete; other points are still valid.
 
Dino Cattaneo said:
Good day Emile

it is very hard for me to provide support on this issue as, afaik, you are the only user having this issue.

Two questions:
- have you tried using the default Tomcat files (no additional mods)?
- have you tried the A/C after deleting the files (and with the default files)?

BR

Dino
Click to expand...

Hi Dino,
Yes both questions.
OK thanks for your help.

Forget the problem I will "fly" with the aircraft like it is.
Have a nice day.
 
I am afraid I am using Prepar3D 2.0.
I will test further over the weekend.

Best regards
Dag
 
As far as I can tell, there should be no difference between FSX and P3Dv2 from the gauge's perspective... seems to work perfectly on my system.
 
Dino, I have all three sims, FSX, Prepar3D v1.4 and Prepar3D v2 installed. I use all three for checking my scenery production. As far as I can tell, your fantastic F-14D Tomcat version 2.20 works perfectly in all three.
 
Looking pretty nice!!

dino have you thought about what i already said.. why not release the S-3 so we can used it as AI tanker until we can fly it.
 
As I already explained, the release of a AI-tanker only S-3 is an option being evaluated very seriously.
Still, a specific model needs to be built for that purpose (especially if we want the tanker to be fully Tacpack compatible) - this is not a big work, but I am short on time.
Current priority in the S-3 project is to complete the base geometric structure of the Virtual Cockpit.
Special AI-Tanker will be made when I'll have a little more time - and when I will be in the right mood...
 
Dino Cattaneo said:
Good day Emile,

as far as I can tell, there is something wrong with the .fx files (or their textures) - alternate causes may be system running out of video memory (this may cause errors in texture loading) or graphics driver error .
Given that nothing has changed in my model in that respect, and also that I cannot replicate the problem and you are the only user (out of several thousand) that reported this, I tend to believe the problem is in your system.

Affected files *MAY* be (juding from the pictures):
fx_strobe_h.fx and/or
fx_navwhih.fx

they both reside in the effects folder

They both use - which resides in the Texture subfolder of the folder effects:

fx_2.bmp

You may want to try to selectively delete (after backup of course) the files to identify the root cause...
Apart from that there may be specific problems due to video card or video memory... the last Tomcat model is slightly more resource consuming than the previous one.
Click to expand...

Hello, you are right these files are corrupted or changed :
fx_strobeh
fx_vclighth
fx_navredh
fx_navgreh


In fact it seams that the files with an "h" at the end are corrupted...:banghead:
I have the same "problem" on other aircrafts.

Where can I find the correct ones?
Thanks in advance
 
Emile said:
Hello, you are right these files are corrupted or changed :
fx_strobeh
fx_vclighth
fx_navredh
fx_navgreh


In fact it seams that the files with an "h" at the end are corrupted...:banghead:
I have the same "problem" on other aircrafts.

Where can I find the correct ones?
Thanks in advance
Click to expand...

Hello,
Solved with this this tool : gauges_recovery_fsx.zip
:wiggle:
 
Good to know you have solved the light problem and enjoy the F-14D!

Aside, I am still collecting feedback for an upgrade - I am constantly looking for improvements.
 
You must log in or register to reply here.
Back
Top