[Ganordi]

Binding a program to a hard disk is not a very good solution. It was necessary either to the processor or somehow to the motherboard. Hard drives break, sometimes they have to be changed due to the small volume.

[saocean]

I want to ask a question. Does anyone try to donate to the tokenmaster twice to extend the usage time or increase the number of activations?

[Twointje]

Is this version of the Launcher Pro still so slow when trying to open a CAFD file with FDL Editor?? or when trying to FDL code something ? Sometimes it took up to 5 minutes before opening a Cafd file to FDL code with version 3.4.0 build 191 ??

[D.Abel]

Is this version of the Launcher Pro still so slow when trying to open a CAFD file with FDL Editor?? or when trying to FDL code something ? Sometimes it took up to 5 minutes before opening a Cafd file to FDL code with version 3.4.0 build 191 ??

Already out new 3.4.1.208  Jun 21, 2019 - Improved CAFD processing and mapping, 200-300% typical

[UnFan]

I want to ask a question. Does anyone try to donate to the tokenmaster twice to extend the usage time or increase the number of activations?

Yes you can

[Twointje]

Just installed the new Launcher Pro version 3.4.2.216 is still verry slow opening a CAFD file with FDL editor took about 3 minuts to open the file. And also when i am connected to the car and want to FDL code ,when i try to read the CAFD file it takes longer then 3 minutes .

Before i had no troubles with this , this has happend since the previus version of the Launcher Pro and i whent back to earlier versions but this does not correct the problem anymore. I updated my windows10 pro the the latest version 1903 and still the same problem, so i am thinking of doing a clean sinstal of this version of windows to see if this corrects the problem of the launcher pro being so slow opening CAFD files with the FDL editor or when tring to FDL code. But this is allot of work installing a clean version windows 10 and maybe it will not change anything on the problem of the new launcher being so slow. Is anyone else also still having the problem of the Launcher Pro being so slow ??

[Deimis]

Just installed the new Launcher Pro version 3.4.2.216 is still verry slow opening a CAFD file with FDL editor took about 3 minuts to open the file. And also when i am connected to the car and want to FDL code ,when i try to read the CAFD file it takes longer then 3 minutes .

Before i had no troubles with this , this has happend since the previus version of the Launcher Pro and i whent back to earlier versions but this does not correct the problem anymore. I updated my windows10 pro the the latest version 1903 and still the same problem, so i am thinking of doing a clean sinstal of this version of windows to see if this corrects the problem of the launcher pro being so slow opening CAFD files with the FDL editor or when tring to FDL code. But this is allot of work installing a clean version windows 10 and maybe it will not change anything on the problem of the new launcher being so slow. Is anyone else also still having the problem of the Launcher Pro being so slow ??

I have no problem with windows7 - 3.4.2.216 after a fresh install of esys E-Sys 3.33.4-39276e2 64bit. 

[jjan]

Hello, I have problem with fem mapping.

Try this: delete %Temp%\Cache content 

It's not working for my pc, every time I open cafd file with launcher I get same mapping and in my temp/cache   new files.

Where can I find the cache files? I have mapping issues and can’t locate the cache files. Thanks

[BMWDriver999]

Hello, I have problem with fem mapping.

Try this: delete %Temp%\Cache content 

It's not working for my pc, every time I open cafd file with launcher I get same mapping and in my temp/cache   new files.

Where can I find the cache files? I have mapping issues and can’t locate the cache files. Thanks

look for c:\temp\cache

[Ganordi]

NBT,E-sys 3.27.1 ,Launcher Pro version 3.4.2.216 verry slow activate FA,very slow opening a CAFD file with FDL editor took about 2-3 minuts to open the file.