JanHas Models & Skin Thread -Compatible with 4.36
-
It’s planned. Somewhere close after the HAF D52+ model.
-
The data for nozzle position in the fm file is a bit of mystery to me. How they all work together? I’m sure I can figure it out with a lot of trial and error. I’m not a big data editor and I prefer to spend my time on other models. If someone finds better values that can make it look/work better I’m sure I will add the new values to the fm’s.
Jan its ok mate i will send you a PM latter today with my modified .dat for you check. Did you see what i mean about the LG up/down sequence?
-
Hi Jan, is this particular version somewhere in the horizon?
https://cdn.airplane-pictures.net/images/uploaded-images/2010/7/30/97189.jpgThe dude in the back looks like he’s just had his mind blown.
-
The data for nozzle position in the fm file is a bit of mystery to me. How they all work together? I’m sure I can figure it out with a lot of trial and error. I’m not a big data editor and I prefer to spend my time on other models. If someone finds better values that can make it look/work better I’m sure I will add the new values to the fm’s.
I will make you very confortable then
–-------------------
Nozzle Max Chart
Determines the maximum NozzlePosition in AB depending on Mach and altitude
auxaerodata:
nozzleMil x , determines the maximum Nozzle Position value in MIL
LGIdle (0/1) : if set to 1 , Nozzle has different behavior LG down / up
nozzleIdleLGUp : position of nozzle in Idle LG up (not in 4.33)
nozzleIdleLGDown : position of nozzle in Idle LG down (not in 4.33)This controls the NozzlePosition value, this value is used both for Nozzle Gauge and Nozzle DOF
From that value , the DOF of nozzle is derived, and there is an aditionnal layer to adjust the DOF vs the NozzlePosition value
animExhNozIdle : not used
animExhNozAB : not used
animExhNozABMax : not usedanimExhNozMil (ther is a typo here, that should be animExhNozMin but will not be changed) : is the minimum DOF value when NOzzlePosition value is 0
animExhNozMax : is the maximum DOF value when NOzzlePosition value is 1animExhNozRate : si the speed rate of the DOF
-
The dude in the back looks like he’s just had his mind blown.
He’s saying: “I can’t believe how detailed this model is!” :woohoo:
-
I will make you very confortable then
–-------------------
Nozzle Max Chart
Determines the maximum NozzlePosition in AB depending on Mach and altitude
auxaerodata:
nozzleMil x , determines the maximum Nozzle Position value in MIL
LGIdle (0/1) : if set to 1 , Nozzle has different behavior LG down / up
nozzleIdleLGUp : position of nozzle in Idle LG up (not in 4.33)
nozzleIdleLGDown : position of nozzle in Idle LG down (not in 4.33)This controls the NozzlePosition value, this value is used both for Nozzle Gauge and Nozzle DOF
From that value , the DOF of nozzle is derived, and there is an aditionnal layer to adjust the DOF vs the NozzlePosition value
animExhNozIdle : not used
animExhNozAB : not used
animExhNozABMax : not usedanimExhNozMil (ther is a typo here, that should be animExhNozMin but will not be changed) : is the minimum DOF value when NOzzlePosition value is 0
animExhNozMax : is the maximum DOF value when NOzzlePosition value is 1animExhNozRate : si the speed rate of the DOF
Mav sorry for the bother but the line animExhNozIdle worked for me in the Jan dat file.
I corrected using the information you send the following lines:
nozzleMil 0.05 ( open to discussion for the PW-220 engine)
animExhNozIdle 32.0 ( it was set to 0)The changes in the line put the nozzle operating like you said always closed from idle to Mil with LG up. It opens very little close to Mil to mach the 5% opening.
The full line code is the following:
typeEngine 0
nEngines 1
engine1Location -18.7 0.00 -0.31
engine2Location 0.00 0.00 0.00
engine3Location 0.00 0.00 0.00
engine4Location 0.00 0.00 0.00
engineSmokes 0
normSpoolRate 3.0
abSpoolRate 10.5
nozzleMil 0.05
LGIdle 1
jfsStartUpTime 15
jfsSpoolUpRate 15.0
jfsSpoolUpLimit 0.25
lightupSpoolRate 20.0
flameoutSpoolRate 35.0
jfsRechargeTime 60
jfsMinRechargeRpm 0.12
jfsSpinTime 240
FTITStart 6.100
FTITIdle 5.100
FTITMax 7.600
FTITAB 7.623
mainGenRpm 0.63
stbyGenRpm 0.55
epuBurnTime 600
DeepStallEngineStall 1
engineDamageStopThreshold 15
engineDamageNoRestartThreshold 3
engineDamageHitThreshold 40
complexnozzle 1
animExhNozIdle 32.0
animExhNozMil 32.0
animExhNozMax -5.0
animExhNozAB 0
animExhNozABMax 0
animExhNozRate 50.0
PropEngineSwitchStates 0
animEngineRPMMult 10
HeatBlurShift -7
hasReverseThrust 0 #Added Falcas
ReverseThrustFactor 0.0 #Added Falcas
minReverseThrustSpeed 0 #Added Falcas
animReverseAngle 0 #Added Falcas
animReverseRate 0.0 #Added Falcas -
Mav sorry for the bother but the line animExhNozIdle worked for me in the Jan dat file.
I corrected using the information you send the following lines:
nozzleMil 0.05 ( open to discussion for the PW-220 engine)
animExhNozIdle 32.0 ( it was set to 0)placebo effect, animExhNozIdle is not used in the code , put whatever value in there , there will be no change.
-
And again you are correct sir
So back to the drawing board
-
placebo effect, animExhNozIdle is not used in the code , put whatever value in there , there will be no change.
Well, he might end up shorter
-
The new models template available?
-
I’m almost done with the LOD1 of the F-16DM-52. The biggest problem was finding poly’s to replace the less cabled F-16I main gear bay with the USAF block 52 model. I had to delete some of the goodies like NVG’s and WSO helmet cover. Next will be the LOD2,3 and 4…
-
I’m almost done with the LOD1 of the F-16DM-52. The biggest problem was finding poly’s to replace the less cabled F-16I main gear bay with the USAF block 52 model. I had to delete some of the goodies like NVG’s and WSO helmet cover. Next will be the LOD2,3 and 4…
Nice dear Jan.
Go ahead…
Nikos. -
:headb:
-
Jan, your work is utterly AMAZING!!! I couldn’t tell a big difference between your “low poly” and “high poly” models!!! You’re “low poly” models LOOK HIGH POLY!!! OUTSTANDING WORK MY FRIEND!!!
-
The F-16DM-52 model is ready. It’s single skin model without some of the goodies because I needed the poly’s for the basic parts. NVG’s, 3D seatbelts and Towed Decoy are gone. Maybe they will come back in the future… You can download the package via my website; janhas dot net. The HTS and SniperXR pod skins are separated from the main F-16 skin so I don’t have to do this at a later point in time…
Next LV3 model will be the Block DM-40
I also released slightly fixed block 40, 42, 50C’s and F-16I models. The 40/50 LOD2('s) had a front gear part missing and the 42 LOD2('s) a small intake missing below the right side of the canopy. The F-16I (non cft) model has a fixed texture. The “danger ejection seat” triangles were missing for the WSO.
-
-
Beautiful Jan…
-
Amazinh Jan.
For now its great but for the B model for the MLU we should take this one and chage the skins or a new model?
-
The F-16DM-52 model is ready. It’s single skin model without some of the goodies because I needed the poly’s for the basic parts. NVG’s, 3D seatbelts and Towed Decoy are gone. Maybe they will come back in the future… You can download the package via my website; janhas dot net. The HTS and SniperXR pod skins are separated from the main F-16 skin so I don’t have to do this at a later point in time…
.
I hope LODEditor Replacement tool to remove poly limitation!
-
Amazinh Jan.
For now its great but for the B model for the MLU we should take this one and chage the skins or a new model?
The MLU’s will have their own models (after the DM-40). I think of compiling a package with a bunch of MLU B models from the different countries using it: RNLAF, BAF, FAP, RDAF, RNoAF. Then the user picks the one he wants to use and install.