I have to agree. Those who use beta versions should understand that only reports pertaining to aircraft functionality are relevant and are intended, as ilankrt pointed out, to help improve the aircraft model. If you are having the same problem with a non-beta version then please report in that sub forum. And if you do, please always attach your log.txt as well. Otherwise, it's practically impossible for anyone to even begin to understand the issue.
I'd advise the following approach, one I arrived at after many months of initial frustration:
1) Always assume that you are making a mistake (or using a fix in a flightplan that is not recognized by the AIRAC, even if it is a current AIRAC).
2) Read pretty much most of the online documentation and watch the tutorials on a specific aircraft. I know it is a lot but this isn't just some game, it's a pretty realistic simulation of the real thing for which real pilots study and practice for years before they fly on their own and even then they always have a copilot.
3) Think about what you would want to know about someone's system and setup if you had to solve a problem for them and provide that information when you ask for help. The log.txt provides most of it but sometimes you need to add how many monitors you use etc.
So, coming back to beta, using an aircraft beta with XP11beta just multiplies the uncertainties and makes individual problem solving almost impossible. If you just want to enjoy flying a fantastic aircraft, like the A320/330, I strongly advise to stick with XP10 and the latest NON beta version of the aircraft.
ilankrt wrote:Some of you will certainly see me as a notorious critic, but as someone who is very involved in the beta tests, I think I have a good reason. Beta tests have the task of helping JAR during the development process and not solving their own problems. Unfortunately 90% of all contributions are user questions which have to do with their own mistakes or incompetency. This fact does not contribute to the development of the model.
Even more annoying is the fact that the questioners often don't read the tutorials or watch appropriate videos to learn from their own mistakes. This could help to make fewer questions and to talk more about program bugs which should be then corrected by JAR.My appel is to invest more work in the learning for being qualified for contribution as beta tester. Personal questions could be dealt with somewhere else. Perhaps JAR should set up an extra discussion forum.
And to the x times the note: Please add to each contribution your soft- and hardware configuration. E.g. Almost always is not clear whether X-Life was activated ....
iMac5K 27” (2015), i7 4GHz, OSX 10.14.6, 32GB, AMD M395X 4096MB, Saitek X52, TPM, Radio, Switch & Multi, TM MFD, XP11.35r1, FFA320v0.11.2-2305, ToLiSs A319 v1.3.3, JDA320 v3.4r1, JDA330 v3.2r1, XL v4_250719, FM v2.6r2, GndHdg v.4.010719, Air Plugin v4.8.3, FWL 2.7.19, 3jFPS-wizard, PI v2.73.06, NOAA v2.4.4, XSPs v2.75, XCL v1.37, BPB v0.47, SAM 1.1.0