Forum

Hi,

Could you describe what you have tried so far and what has happened?

Hi,

When I work on HOG4 PC and Argo, in HOG vizualizer connection I see vizualizer and IP and connectiom working perfect

When I try connect Atlas in this same way HOG do not see vizualizer, there is no connection.

HOG, Atlas, Argo on this same machine

Thanks.

Im having a similar problem as well, Are you running it on a mac with boot camp? Also did you turn on "run visualizer stream" in the main settings for the Hog?

my problem is when i go to set my address in the hog its all greyed out and locked on 127.0.0.1 for the ip. This is very annoying because this all worked flawless this way before, Hog changed their software.

Hi,

PC, Yes I have turn on visualizer steam. On this same computer, in this same time, this same HOG aplication. Argo working, Atlas not working.

IP adress You can change in HOG, just turn on static IP.

Hi,

Have you checked in case you have the Windows firewall on? Atlas runs a separate 32-bit program to relay all communication with the Hog 4 (because the Hog 4 drivers are 32-bit) so it's possible that on startup of Argo you have been asked to open your firewall for Atlas, but the firewall could still be shut for the relaying program (Hog4Interop.exe in the task manager, or should you wish to add an explicit exception for the program in question).

Hi,

I have firewall off. I have not Hog4Interop.exe in task manager. :(

So this part of capture soft (connections with console) is diferent in atlas and argo?

Lars

after talking with hog they say the problem is on your end. All my setting are correct. Atlas is not being seen by the hog4pc. on the same computer, using the loop back adapter with the fire walls off. So hopefully someone can figure this out and not play the blame game of who software is not working. Please test this on your end. Hog is a free software, please test it on a single machine with both to replicate this.

Hi,

We have just released version 22.0.15, which has a good chance of resolving the problem. The clue was when you mentioned that you didn't have a Hog3InterOp process in your task manager. In the event that our new version still doesn't solve the problem:

• Check if you have Hog3InterOp in the Task Manager. If not, Capture failed to detect or load the Hog connectivity drivers.
• Check that in the Universes tab, you have a console link active for Hog 3/4. That would indicate that the Hog connectivity drivers have loaded successfully and are ready to receive DMX.
• If any of the above fail, please send the Capture Atlas.log file from your user's home folder (normally C:\users\<your user name>) to support@capturesweden.com for further investigation. We have added more diagnostic information to it in 22.0.15.