# Amstrad Emulator Caprice32 has extreme lag after update to 4.4 **URL:** \ **Category:** General\ **Created:** [April 3, 2022, 11:33am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060 "2022-04-03T11:33:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![worstcase](https://yyz2.discourse-cdn.com/free1/user_avatar/emuelec.discourse.group/worstcase/32/294_2.png) [@worstcase](https://emuelec.discourse.group/u/worstcase)\ **Post date:** [April 3, 2022, 11:33am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/1 "2022-04-03T11:33:27Z")
After updating Emuelec 4.3 to 4.4, the Caprice32-emulator suddenly has massive problems when started. There are audio and video lags from the bootscreen into the game(s). Even when I load the core [1.10.1 - cap32 (4.5 9aac9cb196 HI)] inside retroarch, the same thing happens: slowdowns, lagging… Before updating to 4.4, the emulator worked perfect [core version: 1.9.8 - cap32 (4.5 9aac9cb196 HI)] Any ideas what could be the problem? Is there something wrong with the cap32-core? And what to do to solve this problem? (Right now I downgraded again to 4.3.) Is it somehow possible to use the old, working cap32-core with Emuelec 4.4? Hope, anyone can help me with this issue… Keep up the great work! Thanks! ---
**Author:** ![miwasp](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@miwasp](https://emuelec.discourse.group/u/miwasp)\ **Post date:** [April 3, 2022, 3:59pm UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/2 "2022-04-03T15:59:18Z")
This bug is described here: [The core does not work, constant noise and extremely slow · Issue #99 · libretro/libretro-cap32 · GitHub](https://github.com/libretro/libretro-cap32/issues/99) It is already solved in the cap32 repo. What platform are you on? Are you on discord? ---
**Author:** ![miwasp](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@miwasp](https://emuelec.discourse.group/u/miwasp)\ **Post date:** [April 4, 2022, 5:06am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/3 "2022-04-04T05:06:37Z")
Bug fixed. You can find replacement cores on discord: [https://discord.com/channels/570131631260696576/570131631713550337/960213118687014993](https://discord.com/channels/570131631260696576/570131631713550337/960213118687014993) Pull request created. ---
**Author:** ![worstcase](https://yyz2.discourse-cdn.com/free1/user_avatar/emuelec.discourse.group/worstcase/32/294_2.png) [@worstcase](https://emuelec.discourse.group/u/worstcase)\ **Post date:** [April 4, 2022, 7:03am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/4 "2022-04-04T07:03:36Z")
Yes, that’s the exact problem I’m having! I’m running Emuelec on Amlogic (EmuELEC-Amlogic-ng.aarch64-4.4). The discord-link doesn’t work, unfortunately. Can you post a new, working link to the fixed core? Would be great! And another question: where exactly do I put the new core into the file-system? Do I have to overwrite the old core-file? Where can I find it? Is this folder correct: /tmp/cores ? ---
**Author:** ![miwasp](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@miwasp](https://emuelec.discourse.group/u/miwasp)\ **Post date:** [April 4, 2022, 7:34am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/5 "2022-04-04T07:34:26Z")
You have to join on discord for the link to work: [https://discord.gg/cbgtJTu](https://discord.gg/cbgtJTu) You have to overwrite the core in /tmp/cores. ---
**Author:** ![worstcase](https://yyz2.discourse-cdn.com/free1/user_avatar/emuelec.discourse.group/worstcase/32/294_2.png) [@worstcase](https://emuelec.discourse.group/u/worstcase)\ **Post date:** [April 4, 2022, 10:00am UTC](https://emuelec.discourse.group/t/amstrad-emulator-caprice32-has-extreme-lag-after-update-to-4-4/1060/7 "2022-04-04T10:00:09Z")
Thank you. Replacing the old core with the updated one worked! Now it’s running smoothly again!