UllyB

Our 3D Max operator, Logan4 is fiddling with the shapes of the "B" model and tries to keep the model as accurate as FCK-1 "B" model close ups pictures we've got.

The C model, WIP and some of its arsenal.

Hello friend! I am really sorry to hear about your brother M., please accept my sympathy. May God have mercy of his soul!

We started work on the C model as well adding supplementary pylons and correcting/adjusting model data as necessary.

I think you've missed that: " For now I can let you know that we will have four FCK-1 versions (yes, two seat version included, and, yes, you are welcome). Logan4 already corrected the FCK-1 3D model we have, there were some issues with it.(See the pictures included to compare some changes). As soon as we will have the UV mapping, for both models, we will start the work for some skins which will go nicely with them. We also found a better model for SU-34 than the built one we had, and we will bring it soon before commencing the work to SU-34 project effectively. "

WIP finishing touches to the LOD

We have some update for you with the current project. There has been some 3D work made and corrected (lamps, canopy actuator, lower pitot, plane's hook), damaged meshes added. Logan4 also built and adapted , from scratch, a brand new HF-2 surface to air missile. Work will continue to the project as planned with some expected (slightly) delays due to the summer holiday I think. We'll see when the time comes.

I still have the Win 10 installed. Never tried it on Win 11. Game was made fully compatible to Win 7. Win 10 and 11 have the same NT core. It should be working. Strange that you say it doesn't. Try what Eric suggested and then try to run it as admin.

Status update - the scoops and gear door actuators are finished. - there have been added most of the antennas - a hook was made for the aircraft - Maverick rails ready - other 3D model improvements Further "to do list": - the canopy mechanism - adding the bottom and spine light meshes - L/R landing lights at the main gears. - afterburner emitter texture and mesh - further skin work

Yes, reshade makes wonders, even in new games, not just the old ones. I am using it in different presets for my own games, including the new ones.It's a very good bargain and choice.

More WIP... Gear, gear door animations tested, correction and polishing almost finished. Minor aircraft body correction as well. Weapon pylons for AG ordnance finsihed and polished. Added external fuel tanks to the model. Some tweaking and editing for the main plane's files. We also work for some skins. Landing lights, gear door actuators, canopy mechanism, missing airscoops/outlets, Maverick rails will be next on the to do list.

How about you read again the post you're referring to ? ;) The answer is there.

I trimmed yesterday the old thread, from all these began, "What will be next" and I reread this part: Let's take the Su-34 as an example. I would love to have it in game, but first we have the cockpit issue - a Su-34 with F-111 or B-1B cockpit - no, thanks, I'd rather have something else. Then we also have the various pylon and rail taypes used on the Su-34 for A2A, A2G missiles, bombs, drop tanks, etc. I doubt many modders would be interested and would spend the time needed to model all correct pylons and rails for the Su-34 and having bombs loaded on missile rails or missiles on bomb pylons is a no-go for me. Well I don't know if Svetlin remembers his post but I want to let you all know, Svetlin included, that...we will have these...various pylons fro A-A and A-G missiles, bombs, drop tanks etc :) Actually half of the work is already made. You are welcome :)

Some WIP shots. I would like to add that we are making serious progress with our FCK-1 project. Our 3D Max "operator", Logan4 is binding things together with a ferm grip; our project starts to get a clear contour.

Oh, didn't know that. Yes, I agree, small mistakes there could mean death, unfortunately. They knew the risk, they all do.

well, they are profesionals, that's what they do.

Yeah , the other fellow collegue already flagged that in the thread. Take a look to what SUNDOWNER said about the issue.

Taking into account that is a issue with a stock thing (no matter its purpose) it needs a serious investigation. When you think to TK who was a one man band and what he did by himself for us , it's hard to think that he forgot or did something wrong there. Of course I left from the basic premise that what that collegue said is true (he never changed anything and played just a stock faulty campaign mission)

Well first idea that crosses my mind is to copy over another similar file. If that and other will give the same crash it would mean one thing: 99% people who played the game, never tried that Mercenary side and realized that something was missing from that library. Only TK would know I guess, if that's the case. I would have upload it for you guys but I am not home right now. If the matter will still count , in a few days, I will upload it, to give it a try.

As Sundowner pointed out (that's news to me , too) the event viewer could give you a clue which module faulted. Take a look there and let us know. Maybe we can pinpoint the problem.You do know to read a event viewer log right (Win 7/10)?

I agree , I've been carried away. I was describing what kind of crashing I encountered myself in the days I was creating campaigns and I just skipped from here to the matter.

Righteous26 beat me to it. These are obviously custom made. The game stock ones are limited to what I already told you.

The metamorphosis of our plane...

Where did you see runway 7 or 8 ? Did you see that in a STOCK file ? Or was it a modded one ? Or are you just asking ? If you did see it in a stock file, please share the info, I would like to take a look. If it's a modded one, there is no need to show it to me.

I know what a razor is :). You missunderstood. It's not about precision in Ocam's blade (sac!), it's about...chance, logic and statistic, in that order. About CPU tests. What games did you test, can you tell/show me ? If you were looking for tests of todays games or even 10 years ago games, you are just beating a dead horse because that is not the subject of the dispute here, you understand that, right ? I was talking (I remind you again) about old 32 bit games, where CPU i-5 and i-7 features won't mean a thing to them. It matters just the brute force and you are telling me that "in the tests you took a look" is just 10% ?? LOL Maybe you are looking in the wrong place. Remember what I said about leaving from WRONG presumptions you end up elaborating wrong conclusions ? I guess you have a hard time to really understand that concept. Please try again. We are talking about brute force (no sofisticated modern CPUs features here). An i-7 has double the cache NO MATTER the frequency its clock runs to, so logically, it will be at least twice faster, with the same load in terms of brute computing force, right ? Twice is 50%., not 10%, not 15, not 20 , not 30 etc. That plus what I already stated (older games , especially flight sims were greatly dependable of CPU power !) send us to the initial conclusion: i-7 beats the crap out of a i-5 in any test under the conditions already stated. Now is it clear for you the exercise in logic I just did or should I try again ? :) About the crash now and your experience , since you decided to help your collegue. Now having your testimony in the matter, the problem is more hazy than it was. Your collegue said initially that it happened when he took off with his plane. For you happened into the mission when those things you are talking about happened. Apparenty there is no connections between the situations, EXCEPT when one type of plane is "asked" by the game's engine to load or it is spawned , the crash happens. So my guess is that those enemy plane loaded weapons that are NOT in those campaign files, so the game's engine couldn't find them and returned a crash as "answer" to that request. It also could be a plane that is not there in campaign files, but being a stock campaign it's a slim chance to be that. or could still be a third situation we are not aware for the moment, because of lack of concludent data.(insufficient data)