JanHas Models & Skin Thread -Compatible with 4.36
-
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
-
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
easy fix => identify the faulty LOD and remove it from DB with proper editing of distances
That will eat a little bit more of fps but at least you will get proper results without breaking everything
edit : too bad it seems to be on LOD 0 and 1 …
Easier fix => do not use burner
bah ,seriously this is basic bug, Janhas should fix it in 5 Minutes
-
easy fix => identify the faulty LOD and remove it from DB with proper editing of distances
That will eat a little bit more of fps but at least you will get proper results without breaking everything
if it can still eat something I could have 15 fps in the pit cause atm I have 23/25 against 35/40 with the original model. All set to max settings. Thank you for the tip.
-
if it can still eat something I could have 15 fps in the pit cause atm I have 23/25 against 35/40 with the original model. All set to max settings. Thank you for the tip.
tip not working
from 40 to 25 for 1 model
=> OUCH !!!
-
tip not working
from 40 to 25 for 1 model
=> OUCH !!!
with older mobo and sockets the result it’s 15 fps lost, there’s no chance in any new settings.
-
Minus 2 fps here, with 16 birds in line…
-
Dear Mav-jp,
While I huge respect your work in FM arena, I don’t understand your aggressive attitude and statement in here.
I understand that you don’t want us to edit your FM, because it break proper flight simulator experience in some cases.
You think your work should be respected and protected, since you spent a lot of time on it, don’t you?
If so, I DO think you are right.However, in my point of view, as JanHas posted, it’s also a matter of user’s choice.
Since the thread for warning already exists as sticky, the risk for editing FMs should be known for all of us.
As I understood, FM is the “core” of this great simulator. The quality should be maintained if we want to experience it.I would like to thank BMS team and all of the previous Falcon 4.0 developers for making their work as editable/flexible.
As my understanding, that’s one of the reason F4 is still growing, and greatest point and advantage in today’s modern combat flight simulator community.
I’m pretty sure not only the 3rd party developers in here thank that truth, but also all of players.
Because we are receiving that benefit in any way.It’s just sad and unfortunate if that great tradition will be lost in the future.
-
I have completed the modeling process for the F-16I CFT LOD1.
-
I took Jan’s advice that he wants to check where his model problem is coming from and not to continue flying with them. We also didn’t choose flying 50 with 52’s FM for a graphical fix and stil flying current 50’s FM with Jan’s AC data(which should not tounching any FM part but only Model part). We were not happy to fly 50 having PW engine.
-
I might be an idiot but i cant seem to find the download link for the skins and models on this thread… i mek post, halp! XD
-
I might be an idiot but i cant seem to find the download link for the skins and models on this thread… i mek post, halp! XD
-
-
just making a small note in here so i can find this back in the future.
The bms forum team tries to provide support and it must be noted that using these mods can then make our life much more harder trying to help ppl because of small unexpected mods hacking some part of the code.
A few weeks ago we has an issue with the jetseat not giving output for afterburner anymore for some us. After some research some guys identified the issue with janhas models. It seemed that for whatever reason the noz pos gauges was hacked and wasn’t following the documentation. As a consequence the third party jetseat software wasn’t working correctly anymore with these models.
Luckily the issue was found just before the author of the jetseat program tried to fix the non issue and luckily because if he did that he would have broken its jetseat software for the ppl that did not mod their install with the noz pos hack from janhas model.As said above, you are all free to accept that a third party developper, skin maker, 3d model maker, screws up your install and create other issues further along the line. Eventhough i don’t believe that you guys are warned enough.
- indeed who amongst you may think that the fm are hacked while you install a 3d model -
I made this note on the simple purpose to be able to find it back and link it whenever i need to explain that support can not be given because of wild modding.
Gents be more mindful of the sanity of your install - especially if you are flying MP or a pit builder -you have been warned of what may happen even if you don’t expect such hacks.