After eating dinner, writing some posts here, and doing some reading, nothing works the same anymore, if at all. Right now vixen crashes everytime I try to start it after showing a little pop-up that says 'waiting to start next show', or something to that effect. I'm going stop for now and try again tomorrow.
I'm just using windows command line functions and .bat files. I did find in the Scheduler - Launcher the command will function line it should. Within a sequence Effect-Launcher I sometimes have to stretch the effect to allow the command to fully execute. I do not know why.
After a hiatus I'm back to trying to get this working.
Right now my test program is a small command-line Win32 .exe program written in c++. It doesn't need any command line parameters, and runs for about 12 seconds transmitting a short multicast ipv4 packet every two seconds or so. The recipient of these packets is an ESP-01 that outputs an indication that it has received a packet on an Arduino serial monitor, and responds with a packet of it's own (which is ignored by the program on the PC). This program works fine (i.e. the ESP32 reports that it has received the expected packets) when invoked from a Developer Powershell window (which itseof seems to need to be invoked by the administrator), as well as the Startup program from the Vixen 3.10u1 scheduler.
However, there is no indication that anything happens when it's supposedly launched from by a sequence, either when the sequence is run from the scheduler or from the sequence editor. I took Aurbo's suggestion and extended the launcher effect to an entire 13-second sequence, with no results. One other thing of note is that the sequence had one group with 750 patch-point elements patched to a 750-output generic serial controller (although it wasn't attached to any serial port).
Silly question, are you running V3 in Administrator mode?
I seem to recall Ledtriks (LTC11.exe) did not execute within the Launcher unless it was in a .bat file
example;
12Days.bat contained the following command line
C:\LTC\LTC_11.exe C:\LTC\12Days.txt
and
12Days.txt contained the following command line parameters
C:\LTC\12Days2p.led
#FDL50
#FRM
#CLS
C:\LTC\snow(2p).led
#FDL50
#FRM
#CLS
It seems illogical but try wrapping your in a .batch file and try it as shown in the attached image
create a text file = PhilTest.bat
add the executable command = Win32 .exe program name on line 1
save .txt as .bat
Thanks, but:
Calling the .exe file from a .bat file had no effect (with or without the 'Win32.exe' at the start of the line. It did, however, work when the .bat file was invoked from a Developer Powershell.
I hadn't been running V3 as administrator, but doing so had no effect.
At this point I'm going to set this aside and plan to run from either a Linux or FreeBSD system. I'll see about running from a WSL2 box in a windows machine and directly accessing the systemConfig and sequence files from there. If that doesn't work because I can't get the packets out from there, I'll switch to a standalone Linux/FreeBSD box and access the Vixen files in the Windows box using ftp or some such program.
By chance are you storing your project files deep in a directory tree like "%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\PhilTest.exe"
Launcher does not like long directory trees from my experience. That is why I use short and shallow directory trees like C:\LTC\LTC_11.exe
No - it's one level down in my home directory. Thinking about it on my walk home, I'm going to defer the decision to use a different OS. I have most of the code needed for a custom scheduler that can be tailored to any of the three operating systems that I use, with the only downside to doing it on windows is it's oddly-chosen 64 Hz default system timer.
Related question - is there an easy way to change the default timer frequency from 64 Hz to something much higher - perhaps 200 Hz (5 mS period) or even higher? This would be for an msvc command-line program, no gui involved. TIA.
Hopefully someone can answer that, It's well over my head Phil

