deimos256

YES! This has been at the top of my most wanted list for some time. Instant day 1 purchase for me!

As the title says, right after takeoff I got a CTD. In the attached log it seems to have crashed while the TBM was downloading data from the FAA and references a SSL cert issue. Log.txt

Not sure if it's related but after updating to 11.30b2 I ca'n't get the plane started anymore. I move the throttle out of cut-off and get a warning about fuel residue, replace the part, try to start again, same result.

Well no I'm not doubting anyone just curious as to what to look out for or test.

My question is why does this have to be so difficult? What are the devs doing where this much effort has to go into fiddling with the toe brakes? Judging from other topics on here 1.0.6 seems to have not alleviated the situation or in fact made it worse.

Perhaps unrelated but I was having CTDs too after periods of use and then I realized that my page file was really small so I set the minimum size to 16GB and max to 24GB (1x and 1.5x installed memory) and knock wood but since then my crashes have disappeared.

The first version I installed I think was 1.0.2 and on 1.0.5 I can definitely notice improved performance even if my frames seem largely unchanged, mostly in terms of less stuttering when looking around. I’m currently trying to determine if loading a stock plane first then the 900 or re-loading the whole sim gives me a better frame rate boost, because both scenarios have given me boosts. 20 FPS vs30+ when changing planes or re loading.

I’ve mentioned it elsewhere but I’d like to add in here that after editing the pref file a second time I had success with my brakes. The first time I was focused on just removing any instance of 6 or 7 and I was ignoring other, higher values. Once I set everything above 4 back to 0 and deleted the XP control profile for the TBM everything was working as it should. Important to note if you have a control profile in X-Plane for the TBM you must delete it. After I edited the pref file the brakes would only work under the default user profile until I made a new custom profile for the TBM.

I should note that this perhaps originally didn't work for me because I was focusing on the values of 6 and 7 and I missed the fine print that said any unusually high number, and I found a bunch of 22s and 10s so I just set anything above 4 back to 0. Hopes this helps.

Ok after trying the preference file tweak (removing high values for axes assignments) a second time and deleting my control profile that I created for the TBM and making a new one, everything is working now.

I have not tried to delete all prefs. I’ll give it a try when I get home later. Also, are there any known plugin conflicts at the moment? I forget the issue the last time but I had the remove my xjet plugin (AirfoilLabs) because it was interfering with another addon. Just trying to cover all bases.

Sounds like the opposite of my problem. I went and tried the joystick pref file delete that I’ve seen going around, but the issue persists.

Also having toe brake issues, have an open topic about it, and deleting that pref file didn’t solve my issue.

The joystick pref file edit didn’t solve my problem, even totally removing the file didn’t solve anything. Still cannot get the plane to recognize my brake pedals. Rudder axis is just fine.

Yeah the lack of any sort of acknowledgement thus far is concerning. I hate to sound hyperbolic but I can't fly this if my brakes aren't working.

As the title says the TBM doesn't seem to recognize the brake axes for my CH Pro Pedals. I have calibrated them both in the sim and through CH control manager and have also verified that all other addon aircraft respond to the brake axes. I also attempted the taxiing tutorial but the brakes weren't responding when I had control. Am I missing something or are there known plugin conflicts, anything that could cause this? Thanks!

Well if I set my Vsync to Adaptive, Half Refresh rate in Nvidia control panel it externally locks the frame rate to 30 and the pauses go away. Not a fan of flying at 30 fps when I typically get 60 but at least I can use the 733 again.

I believe I have isolated where the stutters are coming from, I went through the whole process starting from cold and dark and got the IRS's aligned, route entered and checked, everything except starting the engines. At this point no pauses, as soon as I started the first engine the pauses began. This behavior is isolated to this addon specifically, and quite frankly I have to shelf it until the issue is addressed, which is a shame because this has been my favorite addon since the release.

On the contrary I think coding at every frame would be beneficial. I've stressed this to Laminar as well with their recent blitz on frame rates, which have also caused stutters where there never used to be any, high frame rates are useless if they aren't stable. Stutters due to fluctuating frame rates are far more jarring and noticeable than a low frame rate, which is why you have people setting their refresh rate and FPS limiters to 30, because they value smoothness over FPS. FPS turns into a number that gets used as a bragging point. I understand Laminar's push for high frame rates because of VR but that sad fact is the stutters that they are causing because of this will kill the experience. They've also acknowledged they exist and they won't go away until Vulkan, which won't be any time soon. Sorry for the deviation from the matter at hand but I feel they are related in terms of what developers tend to focus on.

I get a very similar heartbeat. My frame fluctuate from 60 down to probably high 40's.

I respectfully disagree that this is a hardware issue for several reasons 1. I have gone forwards in terms of specs, upgrading my CPU and RAM, while maintaining the same graphics settings as I did on my older hardware, and my experience with the 733 is worse now than before. 2. The above point is rather moot as I've found that this pause issue has only started after updating the plane to 1.2. Prior to this update I had a relatively pause-free experience. 3. This is the only aircraft where I experience this issue. Doing the same flights in the same weather conditions and same time of day with comparable aircraft in terms of systems depth and visual fidelity, I get no such pauses. 4. The pauses happen only when I start turning on systems in the 733. I haven't nailed down exactly when they start yet. Ok So I went and started cold and dark and checked for the pauses after each step in getting the plane ready for flight, I got all the way through powering the plane on, starting APU, aligning IRS, entering and checking flight plan, through starting engines. Up to this point I have no pauses. The next step for me is transferring power from the APU to engine generators, setting the pressurization, turn on yaw damper, turn on window and probe heat, and turn on engine bleeds. Somewhere in that process the pauses began. I then reversed all the steps I did to see if the stutters would stop, they did not. Perhaps they just happen to start at a particular point in time and are not dependent on an action I'm performing in the cockpit. I have attached my X-Plane log as well as my Gizmo log. Hopefully this will help. GizmoLog.txt Log.txt

Well I guess I spoke too soon. Just did a quick flight with the radar off and still got the constant "throb" of pauses.

Been flying the 737 since it was first released and only with this latest version have I noticed the stutters. They seem to occur every second or so like a heartbeat, as describe in this topic. I have indeed tried to disable all AI aircraft but to no avail. I also need to test this again but I have a feeling perhaps the radar is the culprit. I did a flight last night and noticed that it was rather stutter free (though I was flying over water so not sure if this was due to reduced object overhead) at least until I realized I had forgotten to turn the radar on. Once I did the stutters started, and even after shutting the radar off they seemed to hang around. Again I need to test more but that's what I initially found.

This so much, earlier it was mentioned the ground model was modified to allow slow taxiing again, how about posting the amended script so people can just get past the 1 thing that is actually debilitating and then you can tweak to your hearts content. I can deal with an inaccurate flight model but not if I can't taxi to the runway to take off.

Well turning off post processing worked for a little bit but now the crashes seem to have come back.