Release Notes (1.10.7.0/1.10.8.0) Update #5 Now Available

Perhaps its's that I don't like change, but I think the night lights improvements are much too bright and less colorful. If you fly close to a beacon its blinding. The street lights are too big, maybe for screens with less resolution. It seems the G1000 screens are too bright too. But it is easier to find and see the runway and land, a positive for the change.
 
These updates are coming to often for me. I wouldn't mind if they didn't break anything but they always do. The quality control before the updates come out is really quite poor. Yes people will say the game isn't finished but even so you'd expect better. As for the sensitivity setting options, it's awful what they have done to it. I find it really difficult to keep an aircraft on the centre line now and the elevator and aileron movements are just as bad. It's annoying because they were fine before the update. As always 2 steps forward but 1 step back.

I think I'll go back to P3D until the next update comes through...shouldn't be to long they're coming every couple of days it seems.
 
jankees said:
After installing the update all aircraft will use only one texture set, no matter which paint I select....what's this?
Click to expand...

Temporary solution: https://youtu.be/Oy4aMuWP_Uc

Case of fixing one thing, braking the other...

Think related to this "fix":
Performances has been improved in plane selection menu and marketplace
Click to expand...

About the "control sensitivity settings" just RE-SET them, they have now a "+" and "-" side to adjust. Seem they reduced the sensivity also, found sofar reducing it by 50% it flies nice. So if you had it on -50% set it on -25%.

Marcel
 
Yes you must reconfigure your sensitivity settings, I am quite happy with the new system as the old one was way too basic and linear and the new settings allow for better customization.

If you are getting CTD when updating or loading the game, make sure your Community folder contents are moved into another folder temporarily and bring them back after updating and loading the game once, like it says in the Patch Notes. Legacy aircraft seem to be the worst offenders for this.

Speaking of Legacy aircraft, the sim doesn't "officially" support them and they have broken in the past and will almost certainly break again in the future. I wouldn't get too attached to any of your Legacy stuff in the new sim and instead wait for or develop models native to the new sim. All of the SDK documentation that references the legacy stuff basically begs you to use the new systems and stop relying on the legacy systems.
 
Tom Clayton said:
There's a Halloween landing challenge that's rather amusing. The dev's came up with an "interesting" solution for runway lighting, and it's pretty easy to score points.
Click to expand...


We don't need a landing challenge, we need a working sim. Nothing amusing about this latest patch, or update, or fubar, or whatever you want to call it. No more excuses!
 
Yep... zero steps forward and back to square one. Like so many others, I'm dead in the water with a CTD during loading every time. I'm embarrassed for Asobo. They have no discernable development and release process. This is not high calibre software company. A bunch of kids mucking around.
 
Interesting about the liveries. I've only tested two planes, but my liveries install for the C-152 works fine, but not the one for the Bird Dog. With the Bird Dog, it shows the liveries, but never changes to the livery in the hangar. I haven't gone in to look at differences for the manifest or Layout.json or aircraft.cfg yet to see if I could find something that might kick it over. I also didn't try to change livery in the world view either, only in the hangar. Maybe it works in World view, and it's hangar mode that's borked?
 
mgr said:
There is a community fix the texture-selection, see here:
https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-breakes-liveries-heres-how-you-fix-it/
Click to expand...

I kind of figured that might be the difference. I knew the C-152 liveries had model.cfg for the liveries. I didn't know why, or what it does. I'd be interested to learn what adding a model.cfg to the livery does and why it's necessary.

I'm imagining, however, that the BlackBoxSim Bird Dog has model.cfg's associated with the liveries though (I'm still working and haven't had time to look at my sim yet).

I do want to point out the first workaround in the above link is not necessary, the original C-152 megalivery package works just fine for allowing to select any livery. So whatever setup it has is what's necessary (and it does do the model.cfg thing).
 
This is one of the reasons I keep my sim simple. I tried a few different livery packs, but I found myself coming back to the default just about every time. I have a few freeware airports and sceneries like Stonehenge, along with performance mods for the Baron and XCub. I also have my red flashlight and the King Air prop textures. I'll probably spend time tomorrow testing most of those to make sure they're not broken, but what little I've done so far has been good.
 
I had really bad framerates over some of the addon sceneries after the update but a new Nvidia driver came out yesterday so I updated to that and all is well again.
 
I have managed to somewhat tune the control sensitivity (mainly the rudder) so that I can fly it but I wish they hadn't changed it so radically. I prefer the original curves as opposed to the values they have it at now. The CTD issues seem to occur when switching/clicking certain functions. Still a big sigh!
 
I'm going to have to re-do all my steering angle edits.:banghead:

At least I set up a spreadsheet to do the trig quickly.
 
HOTFIX released.

A hotfix for CTDs related to custom input profiles is now available in both the Microsoft Store and on Steam. If you are still experiencing issues with the latest build, please send us details via Zendesk:
Click to expand...
 
You must log in or register to reply here.
Back
Top