-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
Dino's F-35 Version 2.30
- Thread starter orionll
- Start date
Dino Cattaneo
Charter Member
As for the weight question:
- If you are using the Tacpack, you should use the weapon configurator. Otherwise, the TP will not recongnize them as valid weapons. You can also edit the arcraft.cfg to change your default loadout (note that invalid weights or configs are hardcoded....)
- If you are not using TP, provided you have the weights units in lbs, you should simply enter the number in the proper pylon and it should work... but I have to confess I have not tried without TP in the latest iterations of the Store Management System code...so it may well be there is some piece of code that resets the visibility conditions... Will check and let you know.
- If you are using the Tacpack, you should use the weapon configurator. Otherwise, the TP will not recongnize them as valid weapons. You can also edit the arcraft.cfg to change your default loadout (note that invalid weights or configs are hardcoded....)
- If you are not using TP, provided you have the weights units in lbs, you should simply enter the number in the proper pylon and it should work... but I have to confess I have not tried without TP in the latest iterations of the Store Management System code...so it may well be there is some piece of code that resets the visibility conditions... Will check and let you know.
FentiFlier1
Charter Member
Hi Dino,
The problem was simpler than I thought - after scratching my head and slogging through the .cfg file, I ended up having the bright idea of simply looking in the user interface fsx menu. I changed the measuring unit from kilos to pounds and everything is now working fine. Blush :redf:
Thank you so much for the F-35, it is a fabulous add-on!
Owen.
The problem was simpler than I thought - after scratching my head and slogging through the .cfg file, I ended up having the bright idea of simply looking in the user interface fsx menu. I changed the measuring unit from kilos to pounds and everything is now working fine. Blush :redf:
Thank you so much for the F-35, it is a fabulous add-on!
Owen.
Christoph_T
SOH-CM-2016
Will their be a paintkit for this excellent rendition one fine day??
Would like to do my own paints for this aircraft!
Best Regards
Christoph
Would like to do my own paints for this aircraft!
Best Regards
Christoph
YoYo
SOH-CM-2023
Hi,
I noticed some of changes in the last version of Dino's F-35 (2.38):
1/ No HMD mode? This function was before on Shift+2.
From 2.30 of Panel.cfg:
[Window01]
Background_color=0,0,0
visible=0
ident=10091
alpha_blend=0.90
position=5
window_size= 1.000, 1.000
size_mm=1024,1024
gauge00=F35!F35HMD, 0, 0, 1024, 1024
Now is:
[Window01]
BACKGROUND_COLOR=2,2,2
size_mm=156,308
position=8
visible=0
ident=RADIO_STACK_PANEL
zorder=3
No HMD mode? So = no possibility to use TacPack as it was described in manual (mark a target for guided bombs in A/S mode) or I miss something?
2/ After 10-20 min. I have Warning red massage "Low RPM" and dont know why.
Engine stopped in the air. Any ideas (D-Ice on) ?
I noticed some of changes in the last version of Dino's F-35 (2.38):
1/ No HMD mode? This function was before on Shift+2.
From 2.30 of Panel.cfg:
[Window01]
Background_color=0,0,0
visible=0
ident=10091
alpha_blend=0.90
position=5
window_size= 1.000, 1.000
size_mm=1024,1024
gauge00=F35!F35HMD, 0, 0, 1024, 1024
Now is:
[Window01]
BACKGROUND_COLOR=2,2,2
size_mm=156,308
position=8
visible=0
ident=RADIO_STACK_PANEL
zorder=3
No HMD mode? So = no possibility to use TacPack as it was described in manual (mark a target for guided bombs in A/S mode) or I miss something?
2/ After 10-20 min. I have Warning red massage "Low RPM" and dont know why.
Engine stopped in the air. Any ideas (D-Ice on) ?
Dino Cattaneo
Charter Member
@YoYo HMD - The latest version implements a conformal HMD via Tacpack. This allows proper ground targeting and AIM-9X off-boresight lock and launch...drawback: does not work without the Tacpack. Engine shutoff during flight - I have no idea... there is no reason why it should happen apart from a "normal" flameout...
YoYo
SOH-CM-2023
Hi Dino!
Yes, I have the latest version of TacPack (stanalone), so how I can turn on HMD mode now if I cant use Shift+2?
When I change mode from A/N to A/S or A/A I dont see this digits in corners as automatic and point for targeting system in the center of view (diamond?). Knob from VC only now turns on HUD only. Manual is from the 2.30 still : ).
Yes, I have the latest version of TacPack (stanalone), so how I can turn on HMD mode now if I cant use Shift+2?
When I change mode from A/N to A/S or A/A I dont see this digits in corners as automatic and point for targeting system in the center of view (diamond?). Knob from VC only now turns on HUD only. Manual is from the 2.30 still : ).
Last edited:
Dino Cattaneo
Charter Member
...Well, it should be aleady on.
I am not sure if it falls into the "Experimental Features" category... so it may be disabled. Viewpoint tracking is toggled with CONTROL+SHIFT+H - and camera rolling movements is not supported. Note it will work only with DX9. It should be working fine, as I know it does from other users....
(Note that manual is not updated....nor it will be, I think, as I have lost the source files).
I am not sure if it falls into the "Experimental Features" category... so it may be disabled. Viewpoint tracking is toggled with CONTROL+SHIFT+H - and camera rolling movements is not supported. Note it will work only with DX9. It should be working fine, as I know it does from other users....
(Note that manual is not updated....nor it will be, I think, as I have lost the source files).
Dino Cattaneo
Charter Member
Actually the problem is that some of the Tacpack magic (night vision, HMD, FLIR functionality) works by hijacking DirectX 9.0 calls...those functions will not work in DX10.
By the way, there are some bugs in the weapons release logic which mostly affect release sequence for the inner external pylons.
I have an unreleased build with several fixes (including that) - it will be released as soon as I can find the time.
By the way, there are some bugs in the weapons release logic which mostly affect release sequence for the inner external pylons.
I have an unreleased build with several fixes (including that) - it will be released as soon as I can find the time.
YoYo
SOH-CM-2023
Ok, Thank You for explanations Dino.
As the A/A mode works very well...
... but some questions about A/S.
What exactly this diamond shows from HMD (for sure target but...)? When I press the trigger it isnt in the center of cross but a little less on right of cross, and looks like it lost a position. If I press some times a trigger , this diamond jumps from some positions (objects in FSX?).
As the A/A mode works very well...
... but some questions about A/S.
What exactly this diamond shows from HMD (for sure target but...)? When I press the trigger it isnt in the center of cross but a little less on right of cross, and looks like it lost a position. If I press some times a trigger , this diamond jumps from some positions (objects in FSX?).
odourboy
SOH-CM-2020
I asked VRS about this some time ago...
"The TacPack will work fine with DX-10
preview, but the FLIR imagery will not, and never will.
Regards,
Jon Blum
Vertical Reality Simulations
www.vrsimulations.com"
Dino Cattaneo
Charter Member
Yoyo,
the diamond is indeed the A/S target designator, but it is not linked to simulation objects in any way - it just marks the spot.
Basically, when you select the A/S mode the radar is set to A/G mode and set to radiate mode.
Then, if targeting is TOO (Target Of Opportunity - default mode- you can select it in the SMS page in the latest version of the F-35):
- Whenever the user hits the trigger, radar is steered (within is limits) to the pilot line of sight and the intersection (reflection) of the radar beam with the ground is designated as target (diamond).
- If the selected ordnance is guided, either GPS or laser, GPS coordinates are uploaded to the ordnance (for laser weapons provides guidance reference if the laser beam is not detected).
- If the selected ordnance is laser guided, laser is turned on and illuminates the designated target (and turned off otherwise)
- Ordnance is released by pressing the Pickle button
If the target mode is PP (Pre Planned) the difference is that the diamond is assigned to the current waypoint of the flight plan (by current I mean the one you have not reached yet but the navigation system is currently poiting to).
The A/S system has three bugs that I know of:
- There is a slight misalignment between the pilot LOS and the target that is actually designated (it is not clear to me where this comes from - and if it is a graphical or computation error)
- The target designator symbol tends to lag a little on pilot head movements (I believe there is nothing I can do about this)
- Some users are reporting poor inaccuracy of some ordnance. Root cause is not clear. System also does not report minimum release altitude.
Note that AFAIK Tacpack takes in account the blast radius (targets get damaged by nearby explosions).
the diamond is indeed the A/S target designator, but it is not linked to simulation objects in any way - it just marks the spot.
Basically, when you select the A/S mode the radar is set to A/G mode and set to radiate mode.
Then, if targeting is TOO (Target Of Opportunity - default mode- you can select it in the SMS page in the latest version of the F-35):
- Whenever the user hits the trigger, radar is steered (within is limits) to the pilot line of sight and the intersection (reflection) of the radar beam with the ground is designated as target (diamond).
- If the selected ordnance is guided, either GPS or laser, GPS coordinates are uploaded to the ordnance (for laser weapons provides guidance reference if the laser beam is not detected).
- If the selected ordnance is laser guided, laser is turned on and illuminates the designated target (and turned off otherwise)
- Ordnance is released by pressing the Pickle button
If the target mode is PP (Pre Planned) the difference is that the diamond is assigned to the current waypoint of the flight plan (by current I mean the one you have not reached yet but the navigation system is currently poiting to).
The A/S system has three bugs that I know of:
- There is a slight misalignment between the pilot LOS and the target that is actually designated (it is not clear to me where this comes from - and if it is a graphical or computation error)
- The target designator symbol tends to lag a little on pilot head movements (I believe there is nothing I can do about this)
- Some users are reporting poor inaccuracy of some ordnance. Root cause is not clear. System also does not report minimum release altitude.
Note that AFAIK Tacpack takes in account the blast radius (targets get damaged by nearby explosions).
Dino Cattaneo
Charter Member
...one additional note for users which may not be familiar with the Superbug (and ordnance release modes in general): in AUTO release modes, the actual weapon release is inhibited if certain conditions are not met (no valid trajectory solution available - not within max range - steering error too big).
Last edited:
YoYo
SOH-CM-2023
Thank You Dino.
For sure, in RL I know it. It was just a question in sim but tested Today and it looks like is it better than I think before. Maybe this "diamond" has a small bug, but guided bombs hits a point which I show and mark by HMD. Marking of "Diamond" is on a little less and right always.
: ) !
For sure, in RL I know it. It was just a question in sim but tested Today and it looks like is it better than I think before. Maybe this "diamond" has a small bug, but guided bombs hits a point which I show and mark by HMD. Marking of "Diamond" is on a little less and right always.
: ) !
Dino Cattaneo
Charter Member
You are welcome.
As I said, a minor update is in the works - with low priority.
The Diamond misplacement is probably just a graphical misalignment... I'll check.
Regards
Dino
As I said, a minor update is in the works - with low priority.
The Diamond misplacement is probably just a graphical misalignment... I'll check.
Regards
Dino
YoYo
SOH-CM-2023
Roger Dino! And Thank You for incoming update.
Direct Hits!
And one thing - sometimes I noticed SAFE info on HUD, when I have ARM (here example of GBU-10), on HMD the name is ok too, only on HUD I see different info, see this:
Dino Cattaneo
Charter Member
Will look into the ARM/SAFE thing... most likely one is reporting the MASTER ARM switch status, while the other may show the firing consent (which requires additional condition e.g. Landing gear up).
Anyway, it is good to know you guys appreciate the Tacpack integration - it was a considerable effort from my side...but totally worth in terms of added functionalities.
Anyway, it is good to know you guys appreciate the Tacpack integration - it was a considerable effort from my side...but totally worth in terms of added functionalities.
