Jump to content

vicocz

Eurobricks New Members
 View Profile  See their activity

  • Posts

    8

  • Joined

  • Last visited

About vicocz

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    Technic
  • Which LEGO set did you recently purchase or build?
    McLaren P1

Extra

  • Country
    Czech Republic

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. vicocz
    Hi, not sure if I understood you properly, but PF Servo is analog therfore it's maximum output of 90 degress is given by its construction and the app control just percent of this angle. It worked for me if I set "Max output" value for given servo action to e.g. 75% which gave me circa +- 67 degress on servo for full joystick move. The same should be applicable for button base action as well. Regards Vico
  2. vicocz
    Related to the original BrickController2 application there is no support for them at all. My fork currently supports the following list of modules, mostly due to the contribution from J0EK3R: Mould King DIY Module Mould King 3.8 Powered Module Mould King 4.0 Powered Module Mould King 5.0 Powered Module Mould King 6.0 Powered Module I guess he is working on support of another ones, but you can try to reach him and discuss the support. My personal attitude related to Mould King is reserved as they IMHO do not respect intelectual property, especially of MOC authors. But just my opinion :)
  3. vicocz
    Hi, I maintain my own fork of BC2 and ocasionally contribute to the original app, but it's maintained and released by Istvan, therefore I cannot fix anything there, just to suggest changes as pull requests. Based on your information I guess you are facing issue with the recent BuWizz 2 firmware as described e.g. here: https://github.com/imurvai/brickcontroller2/issues/142 AFAIK there are 2 options for you: * use the official BC2 and workaround based on the previous firmware (you need to downgrade the officail BuWizz app, have a look at some previous post here, somebody has published the guidelines for that) * use APK from my forked app, but it 's not distributed via any store. In case you accept all the risks, have a look here: https://github.com/vicocz/brickcontroller2/releases Possibly you can ping Istvan, he promised to release the app (hopefully) soon. Regards Vit
  4. vicocz
    The forked app has already option to share a creation / sequence as json payload: via QR code via Share feature of Android / IOS / WinUI - e.g. it work to me to save / load it from Google Drive clipboard AFAIK MK4, Mk6 do not advertise any data. They just listen to specific advertisment data. The other questions are more to be answered by J0EK3R as he is the author of supported MK and CADA devices.
  5. vicocz
    Sorry to hear something might have been broken in my fork. Without physical device to test, it's quite hard to tell what the issue could be. Obviously, when mupltiple controller support was introduced, device filtering was added in Android. This might be the reason for that. At least I hope. Here is the suspected filtering part: https://github.com/vicocz/brickcontroller2/blob/default/BrickController2/BrickController2.Android/PlatformServices/GameController/InputEventExtensions.cs Just wanna highlight that multi controller support is not part of the original app but my fork only, added with contribution of J0EK3R. Feel free to report any issue of the fork here: https://github.com/vicocz/brickcontroller2/issues
  6. vicocz
    Hi, I maintain personal fork of BC2 and as it looks the original repository is somehow out of maintanence right now, I'm having my own builds and releases. Recently I've added base support for PFX for my own as my PRs to the original reporitories are not getting merged. There are additional features from other contributors as well. E.g. MouldKing support. Have a look here, if you are interested: https://github.com/vicocz/brickcontroller2/releases Regards Vit
  7. vicocz
    Yeah, detection of a device based on advertisment name is possible as BuWizz 2 has immutable name. However it might not be safe in case e.g. BuWizz3 device is renamed to `BuWizz` , BC2 app detect it as BuWizz2 device type but not BuWizz 3. Therefore manufacturer data might be more stable and safe. Btw I've adjusted that fix to use BuWizz manufacturer data, well described by the officail API for both V2 and V3, to detect BuWizz devices instead of the advertised local name.
  8. vicocz
    Have you upgraded the firmware? There is a known issue that BC2 app cannot connect to BuWizz 2 having the latest firmware. https://github.com/imurvai/brickcontroller2/issues/142
×
×
  • Create New...