OnCourse Software

Hey Dave,

I was wondering if there is a way to create or place a copy of the PF3_Freqs.dat file back in the PF3_Display folder in FSX. When the 3.17.0 change was implemented it inadvertently caused a problem for those of us who use MCE voice recognition. The MCE copilot used the PF3_Freqs.dat in that folder to read the PF3 frequencies. For example if I stated "Tower Com 1" The MCE copilot would respond with the correct tower freq. However now he only sees the last file that was created prior to 3.17.0. The work around has been to copy the file manually to the PF3_Display folder.

Thanks again for the support,

Tony J

No problem... it's done!

Hi Dave,
have you done this for FSX only? I have the same issue as i use MCE, but with P3D V5.3 and the Freq dat file isn´t copied into the PF3_Display folder of P3D with version 3.19.
Actually i´am using a batch file to copy the file as a workaround.

By the way, the new heading information within the Push&Start instructions is cool.

Bernd

Hi Bernd,

When Dave said "It's done" I think that he meant it has been reinstated in the next update which hasn't yet been released.

Martin

pointy56 wrote: *

Wed Nov 23, 2022 8:33 am

Hi Bernd,

When Dave said "It's done" I think that he meant it has been reinstated in the next update which hasn't yet been released.

Martin

ha! Must be the british way of meaning "done", indeed. I still forget this from time to time...

Anyway, i really appreciate how non-complicated Dave is supporting his great Software. And i wish him a fast recovery from illness. And though i´am happy to wait for the "fix", beacause i´ve just created a batchfile for doing the anoying copy of the file, having done a batch file for the first time and put some time on it to learn how to do so. Now i can enjoy the batch copy a little longer.

Dave has released beta Version 3.19.1 (see top of forum) which addresses this issue.

Cheers,
Martin

pointy56 wrote: *

Mon Nov 28, 2022 5:54 pm

Dave has released beta Version 3.19.1 (see top of forum) which addresses this issue.

Cheers,
Martin

...support at it´s best!