Lavish Software

Issue went away after fresh install

update fixed it, thanks

After the patch 1.05, I can't get IS to launch a second window successfully.

The second attempt just stops and takes up my processor. First window is running smooth, but that's all I can get to run.

I'm using windows GetAsyncKeyState but when I hit the hotkey inside a session it does not pick up the key press. Is there any special commands I'm not seeing to turn this off?

You can always drop the command into the main thread's queue by using timedcommand, and this would avoid any relay-specific deadlocks. e.g. timedcommand 0 relay is1 xyz This will execute on the next frame (0 is the shortest delay possible for this command) This works. Also found that executecommand...

The function runs fine on anything else (Run, echo, Relay All) but when I try Relay to a specific name it causes the freeze.

Does it matter that I'm sending it to the relay console instead of the session console?

Are you always using the -echo flag in your tests that crash? Have you tried using the echo command instead of this flag? What kind of crash is it? Do you get a Lavish crash reporter? If I had the crash information I might be able to interpret it ;) I've tried echo, dotnet and both resulted in the ...

Are you always using the -echo flag in your tests that crash? Have you tried using the echo command instead of this flag? What kind of crash is it? Do you get a Lavish crash reporter? If I had the crash information I might be able to interpret it ;) I've tried echo, dotnet and both resulted in the ...

hello,

using the following causes innerspace crash:
LavishScriptAPI.LavishScript.ExecuteCommand("relay is1 -echo test")

can't seem to get executemethod to not crash when using relay on a specific target. it's only with the specific target it crashes because ALL as a target works fine.