| Graphics Starts to Draw Really Slow | |
|---|
|
|---|
| | 
Martin Soerensen
Posts 232
13 May 2016 10:11
| Am running with DIGITAL-VIDEO in 1024x768x32.
Whenever I start SMBMounter (http://aminet.net/package/comm/net/SMBMounter), graphics start drawing really slow. I do not have to mount anything, and even if I close the program again, everything is slow until I reboot. Anyone else can reproduce this?
| |
| | 
Philippe Flype
(Apollo Team Member)
Posts 299
13 May 2016 10:51
| Hi,
Can you run a system/cpu monitor before launching SMBMounter ?
Use this one : EXTERNAL LINK
If your graphics comes very slow, there is many chances that your CPU is at 100%. Is so, the faulty program (SMBMounter) seems to falls in a infinite loop. Then of course, system becomes slow.
Can you confirms this ?If confirmed, then it means that the APOLLO core might have disfunction when executing SMBMount.
| |
| |
Martin Soerensen
Posts 232
13 May 2016 11:13
| I have encountered this issue with slow drawing several times where the only way to resolve it was a reboot, and running SMBMounter was a simple way to reproduce it, but there must be some other underlying cause.
I tried running the system monitor and it showed that the CPU is not at 100% while it is drawing slowly.
After starting SMBMounter, I tried opening an LHA file using 3.9 unarc and while the window was drawing (which took maybe 10s), the system load was around 2%.
| |
| | 
Marcus Gerards
Posts 58
13 May 2016 12:05
| I also have this issue. It vanishes as soon as you quit SMBMounter via CXExchange, no need to dismount the Samba-shares. It has nothing to do with smbfs itself. SMBMounter is a BlitzBasic program and might still depend on an FPU. I didn't report this issue, yet, because I wanted to see if it'd vanish with a newer (FPU enabled) version of the core.
| |
| |
Martin Soerensen
Posts 232
13 May 2016 12:23
| Ah, I wasn't aware that the program was still running. I can confirm that if I close SMBMounter with Exchange, the slowdown disappears again.
| |
| |
Philippe Flype
(Apollo Team Member)
Posts 299
17 May 2016 08:48
| Hi, I, for first time, also encountered this type of slowdown. It was when testing SwazBlanker 2.40
EXTERNAL LINK
This nice tool is also written in BlitzBasic, coincidence or not. I founded - that **sometimes** the (RTG) screen is **not** closed in background when exiting the effect (the running blanker itself) and this then leads to intensive slowdowns in Workbench that looks like much as you described, guys.
| |
| |
Martin Soerensen
Posts 232
17 May 2016 13:52
| I had the same problem when I added ClickToFront to the WBStartup folder. Everything would draw really slow. But running ClickToFront manually after WB has started does not seem to cause any problems. I think it should also work when starting it through the WBStartup folder, right?
| |
|
Documentation about the Vampire hardware