Jump to content
LaunchBox Community Forums

y2guru

Members
  • Posts

    1,470
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by y2guru

  1. The 2.x version does not allow Force Aspect Ratio, that feature was introduced in version 3.0 of CTC
  2. If the LB team can make this accessible I can support it
  3. 1. Noted 2. List is larger in the view versus the wheel as the View has more elements
  4. i believe the controller support section in LB is translated to Badges
  5. What controller support field ? not mentioned in the Documentation
  6. Add a custom field to LaunchBox, then populate that field for each game that indicate 4 or 8 way joysticks. that custom field can then be referenced in CTC
  7. it's a WPF XAML limitation as it does not natively support it
  8. Click the link below to add your new feature suggestions to the comments section. New Features for COMMUNITY Theme Creator 3.3 | Patreon
  9. Release year is not advisable. as I said create a text field mapped to metadata release date with date format of yyyy then set that text element to hidden now you condition against that text element
  10. no, add a hidden text field that uses release date (with a date format of Year Month Date) and then you condition against that hidden text field
  11. you havent shared a screenshot of how the animation is being triggered
  12. what version of CTC are you running?
  13. Copy/paste works, code has not been modified
  14. It doesn’t care what view / wheel item template / custom image this is called from, just make sure you type the values into the last 2 rows
  15. anything with an "A" icon in the element list, so.. Hardware Overlay, Full Screen White Background (Maybe) look at the start times for the same trigger types (During Selection, Once Selected) as when those triggers are set, the expectation is that the elements will move or react at the same time and as you know, they are not.
  16. Madheads issues are due to 2 animations starting at different times and hence will never be in sync.
  17. If you can find an example of where it’s used I’ll look at the XAML
  18. Show me the example from the standard BigBox theme
  19. yes the animation start times need to be updated to be in sync as why they match in one version and not in another i couldnt tell you, again not the software, maintained by the author.
  20. so, I figured out why the animations dont work in the main window, they only work when navigation up/down is pressed (and navigation up/down is not used in the main window), that answers the remaining issue. I see no software issues with CTC
  21. animation start values have nothing to do with the software, those values are altered by the author
  22. Yeah I can figure out the triggering issue in Ctc (looking into that now) but I looked at the movement animations and they start at 1.1 and 2.5 for the two different elements, that would why they don’t start at the same time. That’s not a Ctc thing
  23. Nah that’s not it. It’s about triggering the animations, in the editor it’s triggering, the main window isn’t and now bigbox apparently has different timings when triggers are updated. I’ll take a look tonight to resolve the Ctc side but I’ll have to reach out to the lb team to confirm any timing changes
  24. well, so far its been broken since 3.1.5
×
×
  • Create New...