It might be wasted effort, because I think the dev will get around to fixing the app at some point.
Ideally, if you really want to just explain how to hack the default profiles it should be done as a proper tutorial, with code examples and warnings for script newbies so they don’t screw it up.
You can’t assume every potential person who might want to do it is a coder, or understands config files, you need to start from the assumption they don’t even know what JSON is. There’s a lot of people who don’t btw, and why should they?
Adding in other unwanted effects is easy. From an installed copy, and finding out where the customised user profiles are stored for each plane, they could be modified in a similar fashion also.
What the program does for a new plane is determine the aircraft type (piston etc etc) and load the relevant default file from Program Files (x86)\FSRealistic\Data\Profiles and save it as a new file under the new aircraft name in \Program Files (x86)\FSRealistic\Profiles . Any changes you make are then saved to the new file that was created in \Program Files (x86)\FSRealistic\Profiles.
Yes, so what I would do is modify the default “archetype” files, so that new planes I buy are covered. I would then run through all the profiles I have created for my existing planes, and modify them in the same way.
Once it’s done a single time I never need to do it again, barring an FSR upgrade that might tweak those default profiles with new features, or flat out overwrite them.
Thanks for the paths. I will double check that mine is the same. I normally install all my apps on another disk, rather than C, but I don’t remember if FSR ever gave me that option.
I emailed the dev about this quite a while back, with replication examples, and all I got was an acknowledgement. Turn overspeed off, was the only “fix” I found: FS Realistic was just released - #383 by Sonicviz
Turbulence setting also has issues with some aircraft, causing the camera to shake like crazy.
Initially I thought these were specific aircraft issues, but eventually I traced it to these FSR functions that were causing it. The strange thing is it doesn’t happen with every aircraft, but it happens enough to make it a problem.
At least you don’t need to edit the config files, or go and write another program to edit the config files, to “fix” it.
As for an official fix, so far it’s the same dev response with the feedback I gave him about the inability to set your own aircraft default profile, though ie: nothing.
It’s possible he’s working on all the issues raised, and is aiming for a SU10 release to roll them out.
I hope so, it’s a great app, but has some annoying issues atm.
Putting it out on the forum for public discussion is an attempt to get more visibility on the issue(s) and show the developer I’m not the only one with the issue.
Workarounds and hacks are great, but they don’t solve the core problem, which is with the app itself.
But you do realize that not wanting to use a great addition to the sim anymore just because a couple of clicks are too inconvenient is blowing it a bit out of proportion?
“just a couple of clicks”? okay.
Here’s a use case that’s super annoying with the defaults as they are.
User wants to flight test all the planes in each reno class. 10 planes x 4 classes = 40 planes.
Or lets say just one class, 10 planes. Or even half a class, 5 planes. Back to back flight testing. They just want to load and fly.
They are flying solo in single/dual seat aerobatic style aircraft, intentionally throwing them around.
What do they get with FSR out of the box, each time they load a new aircraft: Cabin ambience of people talking, scary ride people screaming, sneezing, someone vomiting continuously, and other sounds not relevant to the context.
Each time they have to scroll through, unclicking these options, which while it’s ok to do now and again, it very quickly gets repetitious and annoying. That’s more than a couple of clicks, it’s a workflow impediment and bad UX. A non-technical user may not know about editing config files to work around it, and they shouldn’t even be required to do that anyway.
Same scenario could be said for any aircraft testing as well, when you’re testing a couple of new planes back to back. Don’t blame the user if it’s not their fault.
I get it. I have some pet peeves of my own… the snow in summer in live weather for example. I’m getting more and more frustrated and vocal about it, the longer the issue gets ignored. Keeping the fingers crossrd for the both of us.
I’ve downloaded the trial version and trying to figure out the best settings. For now, it looks easy to configure but…
Does anyone know if FS-Realistic changes the “Asobo_UI.BGL” file?
No, it doesn’t. No addon should manipulate any Flight Simulator “system” files unless it asks you to do it manually yourself (like the Small Taxi Ribbon mod). FSRealistic should only connect to the sim via Simconnect and put an entry into the XML file for autostarting external addons.
Indeed the ‘Small Taxi Ribbon’ mod was deactivated after I installed FS-Realistic. I can’t recall an message which indicated it would be deactivated. I could simply re-install STR by using the adjusted .BGL file so all works well now.
I’ve come to regret purchasing this for all the reasons you state. The most egregious being the way it messes up the zoom controls. But also having to turn off all the “sneezing, screaming, flushing…” ■■■■■■■■ for every aircraft makes any gains absolutely not worth it for me. There should be a master off switch for all these silly effects, for every effect. Alas, until this gets some fixes and sensible attention by the developer, it’s staying off my rig, and off my recommended list to my mates. Hope it improves.
I’ve been experimenting with the trial version for 3 days now, and adjusted most of the settings I use.
I found a good balance to give FS just that bit of realism I missed until now.
Besides having to reactivate ‘small taxi ribbon’ I didn’t experience any flaws or abnormalities.
It was interesting to watch some YT video’s of real time pilots and hear their opinion of FS-R. I also compared FS-R to real cockpit takeoff footage. Most of the shaking effects look realistic enough.
Because I have some experience as sound engineer I’ll enhance some sounds to my liking, or replace them entirely. With 4 days to go before this trail version ends, I’m still fairly positive.
Dev contacted me the other day and said one of reported my issues (not these) was fixed in the next release (no release date given).
I suggest contacting him directly with your concerns too. The more people that do that, as well as raise visibility on the issues as major UX annoyance fails, the more chance he will prioritise a fix for them.
Honestly though, I think the point of these official forums is for users to voice their opinions about a product. If a developer is any good they will monitor the feedback here and respond to it by improving their product accordingly, and actually engaging with their customers - I know tech support isn’t allowed, but product awareness, progress, and updates are. The first thing I check before purchasing a product is what others here think of their experience with it.
I’ve resorted to just making a default profile with all the rubbish turned off and then copying that profile to any new aircraft and then tailoring the profiles accordingly after that as necessary. Turning off a lot of the over-g, g-effects stuff seems to have stopped FS Realistic messing with the game’s zoom functions for now. If it pops back up I’ll just leave it off altogether. As I understand it, the zoom issue isn’t something new.
Glad the dev seemed reactive to some of your concerns. That’s a good sign.
Glad the dev seemed reactive to some of your concerns. That’s a good sign.
It was a loooooooong wait for a reply, so only half good.
Yes, they should be monitoring but I have no idea if they are.
A poke with a sharp stick from many directions is more likely to wake them up to issues though, so I would strongly suggest you also ping them direct. Manual has the details I think.
Whilst you’re here, is it a known problem within your app since SU10 that affects some planes in terms of how the camera moves vertically with the new “gusts” elements in live weather?
I first noticed it on the new Islander version by Black Box Simulation, but since then had a very similar thing happen in other aircraft (such and the Tiger Moth by Ant’s Airplanes and H145 by HPG) under certain weather conditions. It’s not every time.
The only “solution” is to switch off the Turbulence setting in FSR. Even sliding this down to zero (where it changes to the word “disabled”) has no effect.
Also in those same aircraft there seems to be a problem with the way Windshield noise is interpreted. Below a certain speed (18kts) it’s silent, then the instant you go over that speed it plays the audio loop at full pelt. Changing the volume slider has no effect.
It’s only affecting a few aircraft so not sure where the fault actually lays. Any thoughts?
There are more detailed descriptions that may not be reliant on my failing memory on the actual threads. Will link it below!
