<TIP> how to raise airbase action on the ground
-
@regev Freedom Is All. Thanks you for your suggestion. Looks like someone thinks that the Sim Is his property.
-
No.
It does not seem like someone thinks the sim is his property.
It does seem that somebody with knowledge and common-sense is trying to ensure that - by questioning a questionable modification of a very nuanced system - everybody’s sim performs the best for everybody with the least risk of bugged behaviour.
pr0n
-
@Aragorn well the First post looked like too much “protective”. I fully understand your efforts to bring us this gem but what the user said Is only an advice
-
@MaxWaldorf said in <TIP> how to raise airbase action on the ground:
Please do offer advice but not on things you don’t even understand fully the consequences…
These cfg values are new (or recently refactored) and documented in BMS-Technical-Manual.pdf… without any obvious caveats or warnings.
Is there a safe upper bound (20 min)? That should be called out in the docs, or enforced in the code…
If users changing these is not supportable, should they be removed from BMS? (just hardcoded to 10 min, or left as potential cfg, but hidden/undocumented)
-
@airtex2019 I may be wrong, but like noplayer-play, I want to say these have been around for a long time. I’m away from my computer so can’t look at the tech manual, but are they listed in the .cfg lines with a rev bar next to them on the left margin (the way in tech writing you know if this has been changed since the previous manual revision). I think what @MaxWaldorf is saying is that especially in a new release where there is some bug smashing going on it will cause the devs to chase their tails a little with a bit recommended setting. So if you change it since all of their testing was with 10, you have to state that when making big reports and you could be inducing GIGO.
If I’m remembering correctly one reason this setting fell by the wayside is that it could cause a massive performance hit too.
-
People are free to try what they want but playing with cfg parameters can have consequences especially when you go from 10 to 70…
I think there is a middle ground…
My point was when you have a fresh release, we want to detect bugs that are with stock parameters. With little experience in BMS, people will change stuff they don’t understand and come back to us to complain this is not working…
Have a bit of heart and help us to save some time for ourselves and families…
If you guys want me out then fine… Let’s see who will lose the most here…
-
It’s all cool and dandy , but you guys remember, once you play with modding/non-default configs you’re kinda on your own.
Pls, if something gets broken don’t bother the team before you confirm existence of issues found in stock install, default config, Korean theater.
Have some respect for their time and devotion . -
Should always use the stock korea and vanilla install for few weeks so the team can get a picture of how the update is doing.
This is how they squash bugs…
Its all for the good of the sim.
Also dont forget the devs do this for “nothing”.
-
@MaxWaldorf of course I appreciate the practicality of needing to repro bugs on stock, unmodified BMS with default settings. the “test matrix” of BMS is already so huge… the theaters and texture mods … different launchers and mission editors … fullscreen vs borderless modes … windows dpi scaling … and support for OS all the way back to Win7 … and many dozens of cfg paramaters. it’s actually quite amazing.
(If I had a vote, I would recommend to trim back some of that test surface… I think even Win8.1 is eol later this year)
But to me this thread was just saying “hey look at this neat cfg variable I found”, which seems totally fair play to me. It’s documented, and highlighted as new/modified in 4.36. It’s not like he hacked the binary to find it.
I think it’s a fair response to say “please be reasonable, keep it under 30 min” or “please folks don’t do this right now, we’re still trying to narrow down causes of crashes in 4.36”. or just warn everyone that this is not well tested over 10 min and will very likely have a huge impact on perf and stability.
-
@airtex2019 For my part, I feel like I am also guilty of starting lots of threads suggesting people modify things that I don’t fully understand the consequences of. (Eg. just yesterday I recommended to try enabling force-warp DX override flag, on their server VMs.)
I’ll try to rein myself in, and stop doing that unless/until I’ve actually tested deeply whatever it is I’m thinking of recommending. Especially during the first few weeks after a major release.