Had that happen with the engine too.
I created a topic over on the official Inibuilds forum. Would be great if those of you like @Jigsaw407 who have this issue can add any details:
Had that happen with the engine too.
I created a topic over on the official Inibuilds forum. Would be great if those of you like @Jigsaw407 who have this issue can add any details:
Yes, 2020 liveries are no longer compatible with 2024 native aircraft. The AO/Roughness/Metal textures are using a new format, an Asobo only version of ktx2.
Not to mention the whole structure of 2024 aircraft is different from 2020. More modular now.
Added my 2cents at Inbuilds Forum on fuel issue. Still looking for cause.
They showed up with the older version of the T-33, but when I updated to the newer version (specifically for MSFS 2024) they vanished.
Okay, Inibuilds reports the problem is due to the more detailed engine simulation. As with a real first-generation turbojet, you have to advance the throttle slowly and steadily or the engine will stall out.
At first, even doing this, I was still getting stalls. Then I realized I had started the flight with the hardware throttle pushed forward to about 66% and then pulled it back rapidly, which to the sim looked like a quick shove forward at start and then fast reduction.
So next flight, I pulled the throttle all the way back before clicking fly, and then upon starting the flight, held the brakes and slowly and steadily advanced the throttle to full. Everything worked great! Engine stayed up, no stalls, flew a perfectly normal flight.
Well, until landing, when I realized Iād come in way too fast and bounced, so I instinctively slammed the throttle forward as I raised my gear to go around. And that stalled my engine.
But that was pilot error, not a problem with the sim. RIP Lt. Denny and his T-33. ![]()
Good to know it works - saw that post this morning. And nice to know itās because it works the way the real one does. Well done Inibuilds. Off to fly.
Which engine model do you recād? Default or the other one? Whats the difference?
The default engine seems to model the Rolls Royce Nene 10 that was used in the Canadair-built T-33s like Ace Maker, which iniBuilds says was their research aircraft for the project. Itās more powerful and quicker to spool than the modified one, which simulates the Allison J-33 used in Lockheedās T-33s (and the P-80 before it). The main thing youāll notice with the modified one is the much slower spool time and also a bit less power overall. Which one you like comes down to taste.. or a question of which aircraft you want to simulate - a late-40s/early-50s T-33 (modified engine), or a Canadair T-33, either a period one or a modern private one like Ace Maker. Most of the T-33s currently flying are Canadair-built or have been given the Nene engine.
But⦠what makes it blurry is that in iniBuilds seems to have combined Rolls-Royce Nene 10 performance with some⦠but not all⦠of the Allison engineās systems and procedures. They donāt seem to have settled on one or the other. Real-world T-33 pilots have posted suggestions on their forums but their response is that they wonāt be doing any revisions. Itās one of the factors that makes the T-33 a little less than study-level and a little less than it could have been.
One additional note - the MSFS 2024 version of the T-33 takes advantage of the new simās more complex engine modeling, so the default one will need more careful management than it does in MSFS 2020. Short version - donāt slam the throttle. Be smooth.
Hope this is helpful.
Thank you for taking the time to inform me about this. =D Are there any difference in what āfeelsā correct to use you think, or is it just a matter of taste?
Think itās a matter of taste and a matter of authenticity. I only tried the modified version briefly - not long enough to do it justice. My impression - and itās only that - was that the mod affected spool time more than overall power, so the engine got to the same max power level, but took longer to do it, and in a less linear fashion (most of the lag seemed to be focused on lower half of the throttle range). But donāt take this as definitive - I should have spent more time with it, and maybe itās also been updated since then. I typically fly period aircraft as though theyāve been restored and are flying today, so the default model is fine with me. It seems right for my use case, as opposed to flying a period-authentic airplane.
Iām not spending that much time with the T-33 these days. In MSFS 2024 it seems to be a stutter-fest - I thought the problems were with the sim until I tried other aircraft. It isnāt very well optimized. In MSFS 2020 the flight model can be wonky - to me the instability seem exaggerated at slow speeds. So for that kind of experience Iām more inclined to fly the Shrike F-86 (really good except for the much-too-aggressive pitch-up under power - it demands massive amounts of down trim) or, best of all, the AzurPoly Fouga Magister, which is an underrated masterpiece - it has one of the most authentic-feeling flight models in the sim.
But with any of those aircraft, the lessons learned on the T-33 apply - the engine is underpowered and spool-up is slow. so on approach, the best practice is to throttle way up (as high as 90% RPM) and hang out all the drag - full flaps and speedbrakes. If you have to go around, itās much more effective to get rid of the drag than it is to slam the throttle up and get no response - or worse, kill the engine. So the T-33 is a good trainer in that regard.
Again, hope all this helps, and makes sense.
Yes indeed a stutter fest here lately too. And i agree about the F86 trim. That needs sorting drastically, you loose a good portion of control authority which isnt great for a born and bred gunfighter
I also have been not happy with the F-86 trim up until today. The trick is in the controls setup. I am using the VelocityOne Flightdeck Stick and Throttle as well as the Velocity one Rudder pedals.
I find not using any default buttons or axis on your specific controller is the best approach.
The controller field is the General profile, Aircraft profile and the Specific aircraft profile.
The best way to set up the General and Aircraft profiles is to go to General and on the gear cog showing (None), create a duplicate and name it to your own stick or throttle combo. Then assign all your preferred commands. On my setup I have to do my Stick, Throttle and Rudder all separately making sure Iām on the right unit.
I use the default switch on my stick for trim. When I made my own profile for the Shrike F-86 trim, I now get instantaneous trim input and can trim to level flight after takeoff with just several nose down inputs.
I have been having the same trim problem as you since the day I got my Sabre flying. I would have to hold the trim button for a very long time in pitch with little to no effect and the plane just wanted to climb.
It now trims really nice and quick to have much improved flight control.
I only made a new profile under the General and Aircraft headings by duplicating the default none section and naming my own profile. I have not set up the specific F-86 aircraft section as I save my profile to be the default and save to all aircraft. I mostly fly fighter jets although applying to all aircraft works for my GA aircraft as well.
I had almost given up on the trim until I reassigned all my profiles today. Hope this may help. Happy trimming in the F-86 and of course the T-33.
Creating a duplicate and making your own profile also keeps it from being erased all the time. This new control setup is very time consuming and hard to get used to. Good Luck
Is there something fishy with the Autopilot in the T-33. I set HDG, Altitude and climb to later change to from HDG to NAV. When pressing AP whole hell brakes loose. Aircraft going very steep and with roll to the right. Seemed to hunt some other direction then the one i wanted. Tried to apply AP several time without luck. =/ I prefer the old school instrumentation, but sometimes you want the displays.
Sorry for the late reply - got caught up in work obligations. And sorry to all for the off-topic, but wanted to respondā¦
I donāt think default mapping is my issue. I use Viripil controllers, and to my knowledge none of them has a default profile. So Iāve been assigning elevator trim to buttons. It works on most aircraft if you make allowances for the erratic speed (starts slow, gets fast). And itās actually effective on the F-86 - just seems to have the wrong starting point.
Which makes me wonder, now that I think about it, whether thereās an issue with the way takeoff trim is set. Will check that out. Worth noting also that I havenāt tried the F-86 in MSFS 2024 - Iām sticking with developersā compatibility updates. So none of this may be valid.
Back on topic - the T-33 seems to trim nicely, much better in fact than in MSFS 2020. Iād be enjoying it if it wasnāt for the continual stutters.
Iāve only tried the T-33 autopilot once, in MSFS 2020. It seemed to work OK, but I canāt honestly recall how I used it - what the button press sequence was. Maybe something changed in the MSFS 2024 setup. Iāll try to have a look.
I have lost my T-33 MSFS 2020 pilot(s) . They no longer show up???
iniBuilds say it is MS have interfered??
Just downloaded again and no luck.
Suggestions?
When flying in FS24 with an FS20 aircraft the pilots wonāt show up. This is an FS24 thing and has been made known to Asobo by many developers.
How did you install into MSFS 2024? The iniBuilds app now offers two separate downloads, one for each sim. Only the MSFS 2024 one is fully compliant. If you drop the 2020 version into 2024, several things will go wrong (speaking from experience here).
In my 2024 install, Iām able to see the pilot - Iām using a personal, hand-built avatar with military flight gear, not one of the pre-loaded ones. However, Iām unable to display the copilot/instructor/backseater).
Hope that gives you some clues to work with.
The 2024 version has some problems - the main one Iāve come across is heavy stutters - so itās possible youāre running into something else thatās gone wrong with it.
No, I just downloaded the new iniBuilds T-33 definitely the MS2020 version.
For sure a problem and I keep chasing iniBuilds and they pass it on to
ātheir teamā ??? One reply stated that it is Microsoft that is causing the problem.
Was it an update? I am staying with MS2020 for awhile.