JanHas Models & Skin Thread -Compatible with 4.36
-
The ALE-50 Towed Decoy, from Raytheon E-Systems, provides long-range detection and extremely fast deployment against most radar-guided threats.
For full specs , pls. contact manufacturer
All this and more , including various systems, F18blkIII+CFT / IRST on this page (long read):
https://thaimilitaryandasianregion.wordpress.com/2015/10/30/f18-super-hornet/
Cheers
-
Hi Jan,
Quick question.
The nozzle positions and or fuel flow have changed (in MLU-BE and blck52 as far as I know, didn’t check other models) compared to the vanilla BMS acdata, right? Not to question your knowledge on the matter, or that of the BMS devs, but what has changed and why? Were they incorrect in the vanilla install?Reason I’m asking is because since I’ve installed your models (and new Balkans were they are also), we are having issues with Simshaker. Now it triggers the AB trembling when I’m out of AB because it was based on nozzle position and fuel flow combination. When I revert to vanilla KTO I get no trembling out of AB because FF goes <8000PPH and noz goes to certain position. In Balkans when for example I get a clean jet, go full AB, climb to FL200 and accelerate to M1.75 and then go to MIL power, PPH stays slightly above 8000 and noz remains at +/- 50% therefor still triggering AB in Simshaker logic.
Just trying to decide which one is incorrect, and if your models are correct, what the best behavior is to figure out AB is on with the data available in shared mem only.
I have exactly the same issue with simshaker. Any way to fix it?
-
-
Hi Jan,
Quick question.
The nozzle positions and or fuel flow have changed (in MLU-BE and blck52 as far as I know, didn’t check other models) compared to the vanilla BMS acdata, right? Not to question your knowledge on the matter, or that of the BMS devs, but what has changed and why? Were they incorrect in the vanilla install?Reason I’m asking is because since I’ve installed your models (and new Balkans were they are also), we are having issues with Simshaker. Now it triggers the AB trembling when I’m out of AB because it was based on nozzle position and fuel flow combination. When I revert to vanilla KTO I get no trembling out of AB because FF goes <8000PPH and noz goes to certain position. In Balkans when for example I get a clean jet, go full AB, climb to FL200 and accelerate to M1.75 and then go to MIL power, PPH stays slightly above 8000 and noz remains at +/- 50% therefor still triggering AB in Simshaker logic.
Just trying to decide which one is incorrect, and if your models are correct, what the best behavior is to figure out AB is on with the data available in shared mem only.
go into the F16x.dat file (not the AFM) and find nozzleMil
For PW engine….so…MLU f16ambe, f16amdk, f16amjo, f16amnl, f16amno, f16bk42, f16bk52, f16bk52+, f16bk52+cft, f16bk52+eg, kf16bk52.dat files and change the nozzleMil value from 0.5 to 0.05
For GE engine…so…f16bk40 and f16bk50 and change the nozzleMil value from 0.5 to 0.13
This will put your nozzle position at military power back to the default BMS value.
Hope this helps
-
Thx that fixes th current problem of my Seat vibrating when it shouldn’t.
But I’d still like to know if the janhas version is correct for pw220, cause in that case, the Seat software should be changed instead -
Thx that fixes th current problem of my Seat vibrating when it shouldn’t.
But I’d still like to know if the janhas version is correct for pw220, cause in that case, the Seat software should be changed insteadStraight out of the real 1F-16CM-1
Non-AB Operation in Flight PW220
Regardless of temperature, nozzle position should not exceed 30 percent at MIL.
Non-AB Operation in Flight PW229
Regardless of temperature, NOZ POS indicator indication should not exceed 20 percent at MIL.
Non-AB Operation in Flight GE100
Regardless of temperature, stabilized NOZ POS indications should not exceed 15 percent open in MIL.
Non-AB Operation in Flight GE129
Regardless of temperature, stabilized NOZ POS indicator indications should not exceed 15 percent open in MIL.
-
MaxABRPM Chart
#–---------------------------------------------------
2 # mach breakpoints
0 2.5
2 # alt breakpoints
0 100000Alt: 0
0.97 0.97
Alt: 100000
0.97 0.97
in this way?
Yes but than F-16 Blk50 RPM gauge works like if he is blk40 and having a P&W engine which shoud not be the correct behaviour compared to RL.
Jan. If you could find the time could you fix the problem? or is there any other test we can do for you?
-
Yes but than F-16 Blk50 RPM gauge works like if he is blk40 and having a P&W engine which shoud not be the correct behaviour compared to RL.
Jan. If you could find the time could you fix the problem? or is there any other test we can do for you?
The AB issue is something I will fix when the next BMS update is released. There are numerous small issues that need fixing and the current .33 LV3 models will need a few tweaks to make them compatible with the new update. I want to do it all in one sweep and not peace meal.
I probably will have to build a new AB model to fix that GE issue.I’m currently spending all time I have on the F-16I. The external LOD1 model is almost done. Apart from the DASH helmet for the front pilot (maybe swapping the plain HGU-55 helmet too for the wso if poly’s permit) all other new parts are in the LOD1 but still need a proper skin. The helmet is something I will start working on later today. I will also tweak the front gear so the nose will be a bit lowered.
-
Thx Jan. I will wait for your updates.
-
The AB issue is something I will fix when the next BMS update is released. There are numerous small issues that need fixing and the current .33 LV3 models will need a few tweaks to make them compatible with the new update. I want to do it all in one sweep and not peace meal.
I probably will have to build a new AB model to fix that GE issue.I’m currently spending all time I have on the F-16I. The external LOD1 model is almost done. Apart from the DASH helmet for the front pilot (maybe swapping the plain HGU-55 helmet too for the wso if poly’s permit) all other new parts are in the LOD1 but still need a proper skin. The helmet is something I will start working on later today. I will also tweak the front gear so the nose will be a bit lowered.
Thanks for the update and keep up the awsome work.
Keep us updated too
-
I’m currently spending all time I have on the F-16I.
Christmas is coming early. I can’t wait to see the end result.
-
Hey Janhas pls make TuAF!!
-
I have completed the modeling process for the F-16I CFT LOD1. I had to do A LOT of optimizing of existing parts so all the new parts could be added. The only major eye candy I still can add is the details glare shield (front of HUD) but only if we get the situation where the pods are separated from the model itself. I hope soon… I had to remove the NVG’s because they ate too much poly’s and only human player could use them if he wanted. I gave the poly’s to the open oxygen mask for the pilot (hose looks dark but this is only in LE because of the scale dof it has). Also the license plates patches on the arms have been deleted to use the polys for other parts. This is not a real big issue since from what I have seen all pilot/wso’s have the same flag/squadron patch combo for the entire flight. The upper arm texture will move to the tail texture so I can keep the pilot dds file clean and re-use it for all squadrons. The visor of the pilot will not open because I have no reference material for the part behind the visor. Since I see a lot of photo’s where the pilots have the visor down when walking around the plane I thought I would use the lack of reference material and put the poly’s into the open mask. Also note that the WSO arms rest on the canopy rails when the canopy is closed but will move to the legs when the canopy opens up. For now I work only on the CFT model. Once that is released I will convert it to the non-cft version. Under the CFT are no body poly’s and I have to switch the rear ladder. Next step is skinning.
-
Masterpiece Janhas!!! Once again congrats!!! Wonderful work!!
-
Great work again dear Jan!!!
Nikos. -
MaxABRPM Chart
#–---------------------------------------------------
2 # mach breakpoints
0 2.5
2 # alt breakpoints
0 100000Alt: 0
0.97 0.97
Alt: 100000
0.97 0.97
in this way?
Guys
DO NOT CHANGE FM VALUES OR I WILL BREAK YOU NECK BIG TIME
the data here relates to the way your RPM gauges work and power is delivered
you will break big time your FM if you try to fix a LOD issue with FM data editing
jeeez !!
-
Hi Jan,
Yesterday I flawed Blk50 and Buner fires in front of the nose.
As seen in the picture it even occurs in close formation range.We also tried applying Blk52’s dat file to blk50’s then the anomaly has disappeared.
there is a REASON data file is different between a block 50 and a block 52
they have two different engines with two different engine laws
by editing the Data file you break the engine laws, and therefore you break your FM !!!
AB FLAME ON THE NOSE IS A MODEL PROBLEM , NOT A FM PROBLEM
STOP EDITING F16 FM FILES !!!
i will make sure they are encrypted next iteration if i see people doing that !
-
Guys
DO NOT CHANGE FM VALUES OR I WILL BREAK YOU NECK BIG TIME
the data here relates to the way your RPM gauges work and power is delivered
you will break big time your FM if you try to fix a LOD issue with FM data editing
jeeez !!
I do not approve of your (hypothetical) threat to break someone his neck just because someone edits some data.
It’s the users choice to use the models with edited data. If they do then they accept the consequences. Some are prepared to sacrifice realism for some eye candy… still their choice to make.
The engine data edit is a temporary fix until I have a solution for that issue…
-
I do not approve of your (hypothetical) threat to break someone his neck just because someone edits some data.
It’s the users choice to use the models with edited data. If they do then they accept the consequences. Some are prepared to sacrifice realism for some eye candy… still their choice to make.
The engine data edit is a temporary fix until I have a solution for that issue…
sorry janhas , with all respect
the model is wrong , not the FM .
You should fix it or at least advise people to not alter the FM file
and you know why ? it’s been a 15 years job to create a proper FM
i can not let people editing FM file because a LOD is badly done without proper WARNING that doing so they break the thousands of hours developers have put and offered freely
at least this is your duty as a serious and talented 3D developer to make sure the job of the other developers do not get broken
i understand this is temporary fix, and as you said, WE made the choice to not encrypt BMS so people are free to pork their installation
but at least people are due a proper WARNING
hope this clarifies
-
Guys
DO NOT CHANGE FM VALUES OR I WILL BREAK YOU NECK BIG TIME
the data here relates to the way your RPM gauges work and power is delivered
you will break big time your FM if you try to fix a LOD issue with FM data editing
jeeez !!
yes, already tested and replaced the zip dat files cause no joy here, I just wanted to avoid that burner issue on the nose, but still no joy after editing. I hope in a easy and fast fix for this problem.
Regards