$$anonymous$$y company does not use WiFi connection, we all are connected trought LAN. $$anonymous$$y company has 100+ people connected to the same WiFi working on unity and we all cannot afford to fill the network by continuously debugging trought wifi.
I said obvious reasons because thinking about the possible issues related to debugging trough WiFi they seem pretty obvious to me, I apologize for that, here's a few motivations that could make the WiFi debug unsuitable: I need to debug a method that is executed on Awake of my first scene without implementing workarounds. $$anonymous$$y point is NOT to question about how good the WiFi debug works or how to get it work correctly after deploying trought USB, I'm asking how to do a USB debug, it seems a reasonable question to me and I don't think i'm asking for the moon or something. Since I cannot believe that in 2017 there's no clear explantion on how to do it on the platform considered the standard for game development I hope somehow my careful search has somehow missed the internet page where how to do that is clearly exaplained step by step. Someone from ur team (I suppose) says that android debug currently works only via WiFi adding that " USB debugging is on our list with high priority", stated on Someone suggests to do it in Eclipse, ridiculous, also I don't think it would work. No usefull answers, most people refers to the WiFi usb solution Here's some of the answers I found so far, non of them fits my senario: I already wasted a lot of time searching on the internet how to do it, looking into the official documentation as well as on answers/forums, but it seems no one actually proposes a working question.
I don't mind doing it in MonoDeveloper or Visual Studio, at this point I wouldn't mind even doing it on windows notepad (JK, of course I want to do it in Visual Studio, but if there's no alternative MonoDeveloper would be fine too.). Hello, I'm trying to debug my Unity application on an Android device, I would like to debug it trough +++USB+++ connection, because the WiFi debug is sure a fancy feature, but it is not suitable for actual working for obvious reasons (too much time to deploy in first place)
0 kommentar(er)
