I guess you are right, they’ve never talked about a frame cap. All they’ve talked about is a frame target which they set at 35. If it dips below 35 they start reducing LOD and textures. If it goes above 35 they increase LOD and textures.
So given that it’s a target and not a cap, theoretically I guess you could be flying in a super simple airplane over the ocean or something with no clouds and be getting more than 35 FPS. But that’s never happened to me because I can always see a LOD limit. If they are targeting 35 and there’s enough headroom to get to 120, I should be able to see everything in super high LOD all the way to the horizon, which I can’t.
So my question still stands for how heavy this plane is on graphics rather than FPS. The XBOX doesn’t work like the PC, where you set graphics settings and the FPS fluctuates based on headroom. On the XBOX, the FPS is predetermined and the graphics settings vary around that. I’ve heard reviewers online say the DA42 decreases their FPS on PC, as almost all add-ons do. All I want to know is if it’s enough to notice. For example, I notice on the 414, but not on the Comanche. But this is a problem I can easily solve by buying it myself and trying it out. I will report back after I’ve done that.
I love this plane, and the recent update. But I have really been missing the old liveries. I especially liked the red and gray livery. I wonder if we will ever get those back.
My custom livery started crashing the sim upon load, and I think its that the state saving got into a funky state. I can load in with other liveries. Does anyone know where the state saving data is saved? Where the data or config files live? For instance, the Comanche ones are here: C:\Users[Username]\AppData\Roaming\Microsoft Flight Simulator\LocalState\Packages\a2a-aircraft-pa24\work
but I’m not finding Cows employing a similar location. I want to see if I can copy a healthy one over it.
Thanks. I had assumed they were. There is something livery-dependent causing this one livery to crash on load as opposed to others that work fine, and it was within a week of me enabling state saving for the first time, so if its not something related to the state-saving that is the difference causing the crash, there is some livery-contingent reason it is crashing that I need to investigate. So wherever the state config is, if a user knows where those files are, I’d appreciate the answer and if not, I’ll hop over to their discord later.
(even if I load in with another livery, enable dev mode and switch to the livery I want with the airplane selector, it will crash upon trying to load)
Taking your info, I loaded into one of the other liveries, disabled state saving and engine failures, and now that livery that wasn’t working will load. Not sure what was happening, but for whatever reason, ti works now.
excellent aircraft, many thanks ! finally a GA aircraft with a nice flight model. happy that i decided to purchase.
also in VR with quest 3 no issues what i saw. worked fine.
I love this aircraft so much. Nice to have a robust little study-level twin prop. The issue I mentioned above ended up being a corrupt rolling cache completely unrelated. Took the Twinstar out over the weekend to do a flight across Sicily for a friend, and had a lot of fun crafting a new livery for it and putting in a lot of effort into cutting it into a nice vid. Just such a solid experience, from the sounds to the systems. Great all around.
Thanks. Yeah, I wouldn’t doubt that that’s what I’m doing, but I hadn’t thought so. I’ll need to check my behavior, but I seem to recall it going off at times during strong winds, and the aircraft will be in uncoordinated flight, so then i’ll stomp the ball till it goes out. I could be doing it all wrong though. Thanks for the tip.
I figured out why I’m getting the <RUD and <AL warnings in the Twinstar. Its because of my Brunner force-feedback yoke and rudder pedals. It has a fantastic turbulence system but without the sim being aware of it, I think its being rightly taken as input to the controls. Its a bit of a shame, but I just turn of the YD when I’m flying the Twinstar. I had been in analog steam gauge planes before commiting to spending time in the DA-42, so I’m assuming I’ll get it with any Garmin 1000 glass cockpit. Just coincidentally using the DA-42.
