Error Hog3PC 'The Playback has not closed down'

:1zhelp:

Hi, for the first time i programmed on Hog3pc, after quick a backup i shutdown the program.

After 6 second i get the error:
------------------------
Playback Shutdown

The playback has not closed down.
Press Wait to wait for 6 seconds.
Press Kill to terminate it now.
Terminating a process may result in loss of data and can cause corruption of the show stored on disk.
------------------------

When i press wait or kill the popup shows up after 6 seconds, again...

Do somebody knows what to do???

0 xop15 over 15 years ago

I am getting the same errors on 2 different IPC's
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bradpepe - Former HES Forum Member over 15 years ago

Usually pressing KILL will suffice. Some process is not closing down properly and that is why you are seeing this error. What version software are you running?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jc lights and design - Former HES Forum Member over 15 years ago

I'm running version V3.0.1 Release (Build 2425)
On a mac OSX, running VMWare Fusion with Windows Xp

Pressing KILL totaly not working, it comes back after 6 seconds.
I have to hard reboot my machine, otherwise it doesnt close down.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 woodj32177 - Former HES Forum Member over 15 years ago

Have you tried bootcamp?
This easily could be a problem with running Hog PC through VMware fusion.
Good Luck!
Joshua Wood
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bradpepe - Former HES Forum Member over 15 years ago

Joury,

As Joshua said, the problem well could be that you are running on a Mac. This is not tested nor supported and results could vary.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 andris - Former HES Forum Member over 15 years ago

You have to use Bootcamp if you are going to run hog3pc on a mac.
I have had lots of random unexpected behavior running inside a virtualization environment, but very good results under Bootcamp.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jxgriffi - Former HES Forum Member over 15 years ago

Actually, I run Hog3PC in Parallels all the time. I use it as a remote focus unit for my full size H3 on a weekly basis with a programming wing connected. I have never had any issues connecting or using it whatsoever.

I have also used it for one-offs with a playback, programming wings and a single widget. Again...no issues.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jc lights and design - Former HES Forum Member over 15 years ago

Still I get the error.. So i look for Bootcamp now.

Thanks for your reply!!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 loebus - Former HES Forum Member over 14 years ago

I'm still getting this every time I log off or quit H3PC running in XP/VMWare Fusion on my Mac. Currently on V. 3.1.1, same issue with 3.0.5.
I don't want to use Bootcamp, I need to switch back and forth while drawing in Vectorworks.
How hard could it be to fix this? I know there are lots of users using VMWare, would be a nice gesture to fix for them rather than invoking "we do not support VMWare"
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jxgriffi - Former HES Forum Member over 14 years ago

Loebus,

I'm not sure what's different, but I don't have this issue at all with Parallels so I can switch back and forth between OSX and Wyg.

To me, that sounds like it's a VMware issue and not an Hog3PC issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 loebus - Former HES Forum Member over 14 years ago

Doubtless it is an issue with the way H3PC works in VMWare specifically, I agree. But would VMWare address an issue with one tiny little ultra specific PC application, or would it be more likely for HES to tweak their app so that it might work in that environment? I'm guessing it'd be a relatively simple fix. If it were investigated and that was found not to be the case, I would understand.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 loebus - Former HES Forum Member over 14 years ago

BTW, it was not always a problem, but one that surfaced only after 3.0
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 andris - Former HES Forum Member over 14 years ago

What version of VMware are you using and are you on Snow Leopard?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 loebus - Former HES Forum Member over 14 years ago

On Leopard 10.5.8, VMWare 1.1.3, which is a slightly older version. Tried to update recently, but as far as I can tell there is no way to update VMWare without buying a whole new license.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 andris - Former HES Forum Member over 14 years ago

I have noticed a lot of improvements across the board with the latest version of VMware. I'm willing to bet that is the issue since Fusion is up to version 3.0 now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel