Pretty major network bug in HogPC

Hey chaps, upgraded to 3.3.0 and I've come across what I think is a pretty major problem.

Unless I'm being a massive idiot and missing something HogPC won't let me configure or use any network interface that isn't active (i.e plugged in and negotiated) and defaults the console to a local loopback address.

this is a pretty shocking problem as even once an ethernet cable is plugged in it won't recognise it so you need to exit HogPC and go back in for it to work.

I've tested this on three PCs now and they are all the same, previously this did not happen.

Parents
  • Both Nics are configured in windows correctly but unless the connections are active when hogpc starts they are unavailable to hog4pc and all interfaces are greyed out.

    HES seem to think this is the correct behavior however it causes some real problems in the real world, for example HogPC can no longer be used as a backup console using artnet.

    Assuming you have two NICs the artnet NIC will not become active until it is switched to therefore HogPC cannot use that NIC without being exited and restarted, obviously you could add another netwrk switch but again you are adding a level of complexity which was previously not there.

Reply
  • Both Nics are configured in windows correctly but unless the connections are active when hogpc starts they are unavailable to hog4pc and all interfaces are greyed out.

    HES seem to think this is the correct behavior however it causes some real problems in the real world, for example HogPC can no longer be used as a backup console using artnet.

    Assuming you have two NICs the artnet NIC will not become active until it is switched to therefore HogPC cannot use that NIC without being exited and restarted, obviously you could add another netwrk switch but again you are adding a level of complexity which was previously not there.

Children
No Data