For me, the meaning of ATC messages (instruction itself) is definitely more important than its form (i.e. a name according AIRAC). For example, I personally prefer to be given 'SP2' (Sierra Papa Two) to 'BALAD5L' (Bravo Alfa Lima Alfa Delta Five Lima) and to have an internal convention that 'SP2' means "clear direct Waypoint 680 to join BALAD5L Transition".
The problem with that though is the voices. you would have to record every named fix in every airac cycle (because many of them change from time to time) 119 times over. So that's 119 times the total number of fixes in the World times the number of changes each month. So it's not really a feasable option I would say! You would have to have total 24 hours a day 7 days a week global coverage by Vatsim to achieve your goal
And to be honest giving the fix name phonetically is actually correct ATC procedure. If there is miscommunication or a misunderstanding between ATC and the crew then the fix is always as a matter of course read back a second time phonetically. So know your phonetic code and maintain a listening watch. Using an ATC programme as sophisticated and flexible as PF3 is a big wake-up call for a lot of simmers. Suddenly they are in at the deep end in the real world. Having to prepare a relevant flightplan that is suitable for the specific aircraft. Having to fly according to the fpl (knowing what to say to ATC if they can't) and then having to maintain a listening watch in busy areas.
I was probably not clear enough, as you've interpreted it exactly opposite of what I meant. By saying that "the
meaning of ATC messages (instruction itself) is definitely more important than its
form (i.e. a name according AIRAC)", I mean that I do NOT need any phonetic bells and whistles (i.e.
form) since something simple like 'SP2' or 'SP3' is enough for me and I can 'translate' it for myself to a more complex instruction (i.e.
meaning). I hope it is clear now and nobody needs a "wake-up call"
Vololiberista, your posts are sometimes a bit supercilious, but I appreciate your insights into real-world procedures, you clearly have some knowledge and expertise

You say that when you know the variables, you know the procedure. This is a strictly deterministic approach, but I respect it. That being said, I believe that some uncertainty is a fascinating part of a pilot's life and very realistic too. And that is also true for standard procedures, since things like directs, shortcuts, broken ILS systems, etc., definitely happen...
Because I believe that everyone here wants to fly as realistic as possible, I have a suggestion. What about to share your knowledge of real-world procedures in a more organised form? May be a dedicated webpage where, listed according to airports, you and other certified contributors would publish their know-how. It would promote PF3, communicate the competence of its authors and could be free for PF3 users. It's difficult to find this kind of information and to analyse Flightradar24 data or listen to LiveATC is rather time consuming
Roman