RHFB Crash

Setup Information
1x Road Hog Full Boar 3.2.3 b3367
1x USB Keyboard

I recently upgraded my Road Hog Full Boar to 3.2.3 from 3.1.5 going through a clean install. When I recreated the show I started with a blank show in 3.2.3 and merged in the information from the old show. Yesterday while programming the desk crashed twice and the only thing that would fix it was a hard reset.

At the time of the crashes the playback had some basic lists running and effects were either being driven by the playback lists or in the programmer. I would select a group of fixtures and then Highlight the group, put the cursor in ball mode, and scroll through the fixtures one by one using next/back (left click/right click). The crash occurred if I did all these steps in quick succession.

I didn't check if a dump file was created but the show file can be provided if necessary.
Parents
  • So I got a chance to play around with my board tonight and I have not come up with an exact 100% way to recreate this. I have found out though that when the board "locks up" the console is actually still functioning except that the front panel is no longer responsive. I can put my keyboard in map mode and execute commands and move the cursor around the screen with the touch screen but none of the physical buttons or faders respond to input or feedback. (ie. choose buttons stop following selected faders ect.) I was able to open the task manager and restart the fpdriver process and this would semi-work, meaning that the keypad was opening different views and the choose/IPCB buttons were directly opening their masters/directories.

    The few times I was able to lock up the front panel occurred when I had the lists on masters 6&7 running effects, the programmer fronted, and typed 11
Reply
  • So I got a chance to play around with my board tonight and I have not come up with an exact 100% way to recreate this. I have found out though that when the board "locks up" the console is actually still functioning except that the front panel is no longer responsive. I can put my keyboard in map mode and execute commands and move the cursor around the screen with the touch screen but none of the physical buttons or faders respond to input or feedback. (ie. choose buttons stop following selected faders ect.) I was able to open the task manager and restart the fpdriver process and this would semi-work, meaning that the keypad was opening different views and the choose/IPCB buttons were directly opening their masters/directories.

    The few times I was able to lock up the front panel occurred when I had the lists on masters 6&7 running effects, the programmer fronted, and typed 11
Children
No Data
Related