Hi,first of all I love RC3. GREAT WORK!Now to the possible bug. On my german system the options are not saved correctly. It seems that you save the slider positions as double. So the values are stored as "y,x" and not "y.x" with german settings. As you use ',' as the field delimiter the options are not read correctly. If I can help to solve the problem let me know.Another question: Is it possible to disable the synthetic chatter and only play chatter waves if available?RegardsThomas

Hallo,did you already get RC? Wow! Where in DE do you live? Yesterday I had it not yet in munich.So, tell me, how will you change the software so it can run here on any german version of Windows XP with german version of FS2k2?I will not swap my system setting to the US field delimiter, 'cause many other programs would not like that. JD has to change the VB program and recompile it all over again for german systems, I guess. Maybe there are other problems with calculations within the RC program what will only show up here in germany and are no problem at all in other countries.JD, what do you think about that?Ciao, t_a_h>Hi, >>first of all I love RC3. GREAT WORK! >>Now to the possible bug. On my german system the options are >not saved correctly. It seems that you save the slider >positions as double. So the values are stored as "y,x" and >not "y.x" with german settings. As you use ',' as the field >delimiter the options are not read correctly. If I can help >to solve the problem let me know. >>Regards >>Thomas

Hi,I live in Frankfurt. You don't need to do anything it runs fine on a german system. The only thing you need to do is to set the options everytime you open RC3.Thomas

Don't know if this is the same thing but some European users had a problem with the VB flight plan converter programs I released a few years ago because their systems were set to use the comma instead of the point as the decimal symbol. It drove the lat/lon calculations crazy!The solution was simple - just go into Control Panel and change the decimal symbol from ',' to'.' in the Regional settings but I note that t_a_h is refusing to do this.;http://jdtllc.com/images/RCbeta.jpg

Well, call me Torben.Yes I dont like to change my settings. I use FSMeteo, FSNav, FDC, FlightPlanner and some other FS2k2 ADDON progs. And of course other non FS2k2 progs. I dont wanna change my setting every time I just start FS2k2, not using any prog in bg which need my german setting of the decimal point/commata. Some need it, some not. And I could forgett from time to time that I have to re-set the settings after I quit FS2k2. So, the RC3 VB program has to be changed so it can be switched for the other users in other countries can change just and only the RC settings.So, I wonder if the database of all VORs and DMEs and airports etc. are with lat/long entries and these ARE different interpreted here in germany with the setting different. So, are you sure THERE ARE NO other problems? Well, I do my planing with Unlimited Airlines and FSNavigator and export these plans to FS2k2 and to whatever I have to. There the data is just right and all works well. But I have another planing software where the Lat/long is in error caused by my german settings. So, I cant use this software for planing any longer. Yes, and what IF I forgett to change back my settings and wanna do calculations with excel? Excel needs exactly my german settings when I calculate finances etc.. There is a difference betweem

I agree 100% with Torben, and let me tell you, this is not a "German thing", it's the convention all over the European continent, also here in Denmark.Every Style Guide compliant Windows program knows how to look up this setting in the registry and deal with it. Had I suspected for a moment that RC3 is not one of those, I would not have ordered it. Not because the bug is very serious, it seems not to be, but because such flaws often indicate poor programming practices and, consequently, poor software quality.I realize that it may be a Visual Basic issue and out the hands of the RC team, but usually there's a way around these things for the programmer. Changing the Windows setting back and forth to outsmart a bug (insignificant as it may be) is not only inconvenient, it's unacceptable to me. If Thomas' conclusion turns out to be correct, there's no end to the number of complaints bound to come from European customers until it gets fixed.I also realize how thoroughly RC3 was beta tested, and in many different geographic regions, so I choose to arm myself with optimism until the disk arrives and hope that I'll not have the problem. :-)

i guess i will have to read up on this. never had a problem during testing. i guess they were all using commas in their .csv filesare you saying a csv file is full of periods instead of commas? should be called a psv file :-lollet me check on this.

I will have a try out right away when my key request e-mail will be replied. Just today I found the realy nice slim case of RC3 within my post /snailmails. I am soooooo exited, but have to weait till I get the code! Than I will try out all and especialy the save function if all works with my german version of windows and FS2k2.CiaoTorben.

Henrik,ACLoader does that exact check, to see what the delimeter is on the user's system, then adjusts accordingly. The fact that RCv3 doesn't have it is probably my fault since I should have brought this up. JD had no reason to know at the time. No one on the team (even the European guys) ever mentioned it.

Scott, JD,Thanks for your replies. I'm sorry if I came through as a pedantic grumbler. I have just received RC3 and can't wait to install it.The reason for my post was that some of the previous posters seemed to think that this issue didn't have to be looked into, because it could be bypassed and only affected a few stubborn Germans who don't know what a decimal point looks like ;-)As long as it is recognized as a real, albeit minor, bug, I'll live happily with it until it gets fixed :-)