+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: 【
RE: Launcher Pro 3.1.0 - Released - AutoExe3219 - 14-04-2018
(14-04-2018, 09:13 AM)Almaretto Wrote:1EF6_006_025_106.NCD(14-04-2018, 08:55 AM)AutoExe3219 Wrote: I run LauncherPro in Dynamic activation.
I opened the first NCD file without problem but the second showed the dot.
Is this a limitation of the dynamic activation?
No. Which NCD is not displaying descriptors?
If i first to opened this file,it displaying descriptors.
After another NCD file,it dont displaying descriptors.
RE: Launcher Pro 3.1.0 - Released - Almaretto - 14-04-2018
(14-04-2018, 09:18 AM)AutoExe3219 Wrote:That is a memory issue.(14-04-2018, 09:13 AM)Almaretto Wrote:1EF6_006_025_106.NCD(14-04-2018, 08:55 AM)AutoExe3219 Wrote: I run LauncherPro in Dynamic activation.
I opened the first NCD file without problem but the second showed the dot.
Is this a limitation of the dynamic activation?
No. Which NCD is not displaying descriptors?
If i first to opened this file,it displaying descriptors.
After another NCD file,it dont displaying descriptors.
Use settings to remove unneeded kiswb
Install 64-bit Java (JRE7 for 3.27 or JRE8 for 3,32).
Copy Files over to jre_x64 created folder in E-sys directory
Edit memory for 4-8GB
Run Launcher again to open E-sys
Check logs: search javamem & see if max matches set target in settings
RE: Launcher Pro 3.1.0 - Released - BMW_Fun - 14-04-2018
Already E-Sys - Conversion to 64-Bit JAVA
Java-Version : 1.8.0.121 64 Bit
p.s.
E-Sys is currently not supported under Windows 10. Workaround for display problems under Windows 10: E-Sys.exe -> Properties -> Compatibility -> "Override behavior at high DPI scaling" -> Scaling performed by: "System"
RE: Launcher Pro 3.1.0 - Released - AutoExe3219 - 14-04-2018
My system is WIN7 64bit with JAVA1.80.131 32&64bit.
Do I need to downgrade JAVA1.8.0.131 to 121?
I tried Almaretto's way but no luck.
RE: Launcher Pro 3.1.0 - Released - BugFix - 14-04-2018
java in E-sys folder
c:\EC-APPS\ESG\E-Sys_3.32.1\jre\
RE: Launcher Pro 3.1.0 - Released - Almaretto - 14-04-2018
(14-04-2018, 10:20 AM)AutoExe3219 Wrote: My system is WIN7 64bit with JAVA1.80.131 32&64bit.
Do I need to downgrade JAVA1.8.0.131 to 121?
I tried Almaretto's way but no luck.
You do not need to downgrade. But...
3.27.1 uses JRE7
3.32 uses JRE8
You are copying over to new folder in E-sys directory. Afterward, you will have both jre and jre_x64 folders.
RE: Launcher Pro 3.1.0 - Released - danyro - 14-04-2018
i am using jre 1.8 64bit(copied from c:\program files\java) in e-sys\jre folder not jre_x64 and i can use 4gb memory with java (verified by logs).
e-sys v3.32.
RE: Launcher Pro 3.1.0 - Released - georgia55 - 15-04-2018
Are there still problems coding HKFM ECU?
Thank you very much
RE: Launcher Pro 3.1.0 - Released - Almaretto - 15-04-2018
(15-04-2018, 07:01 AM)georgia55 Wrote: Are there still problems coding HKFM ECU?
Thank you very much
No, there have not been problems for awhile with HKFM.
There are three HKFM2 CAFD's (2098, 570E, & 5710). Only 570E is not mapped, but all share identical descriptors so you can use others as reference as well as duplicate the same Launcher Cheat Codes (just change cafd id).
RE: Launcher Pro 3.1.0 - Released - mcrussell - 15-04-2018
Has anyone managed to get the ecu tree to open collapsed instead of expanded in 3.32? I have ticked the box in settings "show collapsed SVT" but when I read ecu's they still show expanded.