Dear Readers:

I am getting the following error code in the console:

Warning: invalid .mplay_lock file detected
Warning: invalid .mplay_lock file detected
mantra: Could not open imager

The mantra OP turned red but then when I tried to rerender it never turned red but Mantra MPlay still didn't come up. Is there something wrong with my installation?

Sincerely,
markerline

Maybe this thread might help?

http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=15788&highlight=mplay_lock [sidefx.com]

I have responded in the above thread. I cannot achieve a render at all, in spite of following the thread's suggestions.

Sincerely,
markerline

Does file get deleted afterwards? What does the contents of the file look like?

The .mplay_lock.blah file is a file where “blah” is the name of the server. The contents are (at least in my case) two number strings XXXX YYYY where each set of X's and Y's represents a 4-digit number (not all the same digits, obviously). The file is temporary and only exists for the life of the mplay window. I couldn't tell whether it exists from the moment that I trigger the render, but I do know it sticks around until the mplay window is closed.

Sincerely,
markerline

What operating system are you running on? Also, what specific build of 10.0 are you running?

markerline
The mantra OP turned red but then when I tried to rerender it never turned red but Mantra MPlay still didn't come up.

After the Mantra ROP turns red, what if you close the mplay that comes up and then try re-rendering?

After the Mantra ROP turns red, what if you close the mplay that comes up and then try re-rendering?

I tried that, but Houdini enters an inoperable state and must be closed and restarted.


-markerline

What operating system are you running on? XP or Vista? Also, what specific build of 10.0 are you running?

I am running H10.0.295 on Windows XP Pro SP2 (32-bit)

I got rid of the no-render issue but then it mysteriously resurfaced when I tried a render from H9.1.179 . Don't ask why, but I have to use both versions because of a serious bug in H10 that I've reported. They told me they would try and get it resolved.

Sincerely,
markerline

Which no render issue are you talking about? Are we still talking about the same thing? I assume that you can always still render to disk.

I guess you can always render to disk, provided you render with the right camera, which I accidentally didn't do and it proceeded to render 200-something non-existent frames before I realized the camera didn't exist. Duh.

Anyway, we were speaking of the mplay rendering issue with mplay_lock . The problem appears and disappears like allergies.

-markerline