Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/24/2020 in all areas

  1. Heya @SrMouraSilva Im gonna be doing the base setup for the new react system for i5 and I love your questions. In regards to open sourcing it, I don't think thats a possibility at this time. The restructure to react is going to take a bit for the core staff to get used to and I want to make sure that the correct setup is done before that could ever happen. Without getting into too many specifics, there just needs to be a flow that everyone gets used to which will make participation easier for any dev to work with. If you want to participate please contact unleashed regarding that! The front end will be react and the backend will be graphql. The middle layer will be apollo-graphql. I am hoping to use a lot of the new things that React Storybook has provided for testing and CI, which can mock backend requests through apollo-graphql. This will take at least a few weeks to set up, and also my intention is to teach as many people as I can what I know, so to have a stable build that we can get started with will take a little bit.
    2 points
  2. 2 points
  3. I think Ignition 4, formatting and forum connection aside, is a welcome improvement. Now I can log in and have access to all customs on any computer, without problems. There will always be people complaining, sadly not everyone is informed about the hard work that goes into maintaining a website supported only by donations. From this side of the world, thank you for keeping this alive, even more so considering the current health situation that affects us all. Cheers!
    2 points
  4. Post all your CDLC requests here. Since we no longer have the "Popular" Request system, you can now post them in this, and only in this, topic! NOTICE. Posting a request here does not mean that someone will make it. Spamming the same song over and over will get you suspended. This is not a demand area. The Charters that post their CDLC on CF do so because they want to. You cannot force them to make your song. Do not send PM's to every single charter asking for your song to be made. Basically this is a dumping ground for your requests and nothing more.
    1 point
  5. Unfortunately, I will start this post off with some bad news and that is our lead developer has parted ways with the Ignition4 project. We wish him the best in the future and I want to thank him for helping us get Ignition4 launched. I just wanted to clarify a few things with everyone: We never intended to launch Ignition4 until the main features were completed. This included a long beta testing period where we would fix any problems that we found. We ran into an unrecoverable bug with our old website where the login cookie from the forums would not be sent to Ignition3, causing a login loop. I had all of our devs look into it, and none of them could resolve the issue. Our backups did not resolve the issue and I was forced to upgrade. That is where we are now. Ignition4 is still being developed but all future features that we had planned for Ignition 4.5 have been canceled. This is due to the lack of Laravel/Livewire developers we can find. At the moment we only have three including me. None of us know Livewire as much as our ex-developer knew so we're stuck on fixing certain things and adding new features. We will continue to fix any issues and try to improve Ignition4 to make it as smooth as possible. What does this mean for the future of CustomsForge? Ignition5 - React We plan on rewriting Ignition4 to use React instead of Laravel. Every developer I've interviewed recently knows react. It is way easier to find react developers over laravel developers. We already have a dedicated team of 7+ devs (compared to our old team of 4) that knows react over laravel. It took 2+ years to complete ignition3 to ignition4 due to major rewriting issues, but the move to ignition5 should take a quarter of that time in theory. To kickstart the Ignition5 project, I brought back our original layout designer @AshesOfOwls. She helped us design the original UI for Ignition3. We adapted that design for Ignition4, and will be updating (or even revamping) the look for Ignition5. We are very excited to get most of our staff on board to help with the Ignition5 react project === Q&A Q: Will planned features for 4.5 be included in 5? A: Our main goal will be porting all currently used features for Ignition4 with features we wanted for 4.5 in mind. This way we can get the website over to react ASAP while also improving missing or broken features. Q: When will collections come back from the old site (Ignition3)? A: At this time, collections from the old site will not be brought over. It has 20 million entries and it's just impossible to work with that amount of data at the moment. We will need to figure out the best way to store that data without making ignition slower. Q: Are there any planned features that might make it for Ignition4? A: Not at the moment. We would love to bring Artist search back, as that is highly requested but that would need to be done with extra free time not devoted to fixing ignition4 bugs or coding Ignition5. Q: Are you not looking for Laravel developers anymore? A: We would absolutely love to find another Laravel developer so we can finish some features on Ignition4 that are not completed. If you know Laravel + React that is a huge bonus. Contact Unleashed2k on our Discord if you have any of these qualifications. Q: There are tons of broken features! I don't like the new site, etc etc A: We are fully aware there are some people who do not like the current website. Like I mentioned before we never wanted to release the site in this current state, but it is an improvement overall with the new site speed and forums being upgraded. We are working on bringing all the features from Ignition3 & Ignition4 and the planned 4.5 to Ignition5 Q: Will Ignition5 still use the forums? A: Yes! We will be using a more advanced integration using the IP Board API which will allow us to use groups & more features from IP Board. === We're very excited about the future and the possibilities of Ignition5. I hope this answers some questions and we're looking forward to improving CustomsForge. Edit: I've launched the Ignition4 FAQ. We hope to create the ultimate knowledgebase of all Ignition4 questions there. https://ipb4test.customsforge.com/index.php?/faq/
    1 point
  6. Finally works! Random misses here and there, even though it's very easy 4? Most of the song is easy but those bends are so hard on my Fender Jazz! Ugh. Weird and hard to play
    1 point
  7. The backend is built using Lumen + Hasura and for the database we used PostgreSQL.
    1 point
  8. Yo Mik! Sure will do that, thats a good thing and shall stay as it was. I just forgot or was too tired
    1 point
  9. -= HOW TO BUILD A PROFESSIONAL ROCKSMITH Plug´n´Play USB / BT FLOORBOARD FOR TONECHANGE for less than 30$/€ =- Latest Update: 20.01.2015 http://i59.tinypic.com/29o51jd.jpg This video is just a proof of concept, it is gonna edit: might, with a chance of slim to none be replaced by a better one as soon as my hardware hell has vanished … sigh… Features (V2.0):KEYBOARD INTERFACE – works as standard Keyboard – no special drivers, software or hacks neededPLUG AND PLAY for Windows and MacUSB or BLUETOOTH ver. available.EASY TO BUILD - ONLY 5 Wires to SOLDERCHEAPINGAME TONESWITCH everywhere (LAS, SA, SESSION MODE, MENU….)http://i59.tinypic.com/29o51jd.jpg You want one of those – Here is the DIY HOW TO: Needed: 4 Button Floorboard of your choice (no matter what connector it has) (20€ +)A USB or BT Keyboard (use an old or get a defective one (Keys 1,2,3,4 gotta be working) (0-25€)Soldering stuff incl.5 thin wires (e.g. an old IDE Cable)Multimeter (optional but makes it easier)A screwdriverGaffer TapeA textmarker (for cd labeling)http://i62.tinypic.com/390xy.jpg Difficulty: easy If you have sucessfully soldered anything before – you´re gonna do it for sureIf you have never soldered anything before – thats a rather easy task to start offTime: A few hours or less (my second version was done from scratch in 30 mins) So here we go! Grab your Keyboard (The HP one i used has a small interface that will fit in almost any footswitch, a long enough cable and a matrix that is easy to follow – hence the used button wiring is easy to determine). -Unscrew and open it. http://i58.tinypic.com/f00ua0.jpg As in my pics below mark the buttons 1-4 (not on numpad) . When you lift the rubber layer you see the wiring matrix. Short explanation of keyboard function: 2 matrixes with wires – when pressed together = 2 pins on the interface board are connected and thats the buttons signal. So – mark the buttons you wanna use on both layers of the matrix (waterproof marker for cd labeling works good) Optional: if you have extra switches on the floorboard you might wanna use extra keys like: Enter, Esc, Up, Down – if so – mark them too! http://i57.tinypic.com/eq1htt.jpg Now for the hardest (not really) part: Go to Button 1 and follow the wires (white lines) on both matrixes to the interface board. Double check, you can follow them with different color textmarkerst to make sure, but that shouldnt be needed, and is way too professional for my way of doing stuff like that ;) Now you should have found the two pins on the interface board that handle „1“ (Alternative: search gxxgle for schematics / pinout dor your specific keyboard) To test: - I TAKE NO RESPONSIBILITY FOR DAMAGED HARDWARE OF YOURS - Connect the usb plug to your computer, open a texteditor and shortcut the two pins that you have marked on the interface board – best with a multimeter set to resistance (ohm). Alt: use a piece of cable. If everything is right – the text editor says: 1 – aint that great ! Now go on – follow the wires of button 2, 3 and 4 (and the extra buttons you might want) It is very probable that you find a common ground for 1-4, so you should have five pins marked (i call em 1-4 and 0). If there is no common ground = 8 pins determined (2 for each key) - no problem - read below! http://i57.tinypic.com/10cixk5.jpg Test all buttons the way above and if everything is ok you are ready to: OPEN THE FLOORBOARD: http://i60.tinypic.com/w7cs34.jpg The board is gonna look a bit different for you unless you have the same 1st gen line 6 fb to work on... Nevertheless - what you are searching for are the two pins for each buttons that are connected by a press on the button. The easiest way to find those is using a multimeter set to resistance (ohm) - adress 2 suspected pins - press the button and if the number on screen goes to 0 - these are the 2 pins to solder! Furthermore: Check if there is a common ground (connection) between the individual buttons with the multimeter ("0" on screen means pins are connected and hence only one of them has to be wired to the ground of the keyboard interface)... This is very probable, however if not (no "common ground" on fb board) you have 2 options: #1 (recomended) connect one of the "to solder" pins of each button by soldering with the next one so only one of them has to be wired to "0" on keyboard interface. (see schematic diag 2) #2 connect one of the "to solder" pins of each button by soldering with common ground of the keyboard interface - that way 8 wires to be soldered from kb interface to fbboard instead of 5. If there is no "common ground" on kb interface, but you find 2 different pins for each key 1-4 just solder the 2 pins to the 2 pins of the fitting button in the floorboard board - in this cas you need to solder 8 wires (no problem) If you have problems at any point pm me, post a pic of your situation, believe me - it is not gonna be so hard, i´m gonna help you. When you are done you have: - The pins on the floorboard to be wired - the according pins on the keyboard interface sending "1" - "4" WIRING Solder the according pins (there are excellent youtube vids how to solder if you never have) @@Frack 's little tips for this : >>The parallels contacts material you'll solder is copper covered with a carbon like stuff. you can remove this carbon by using the FLAT part of one screwdriver or a blade, take care to don't scratch the copper though. This carbon is a pain in the a.. to solder (try on one unused contact first) go very gently with several passes. Once the copper is visible & clean put some solder in it, the differents parallels contacts should not be short circuited, if it happends, heat the solder along the copper to minimise the quantity. put some solder on the end of the wires & heat both when in contact, blow on it to accelerate the cooler process. take care to not overheat the board or the added wires (as they are very thin) any telecom/computer wire is ok for this.<< If you look at my pics you can see that i did some scratching on the kb interface pins, put some solder on and got a nice result with that. Here a principal schematic diagram: http://i62.tinypic.com/2wlsd8n.jpg The black dots are the common ground on the fb board = they show a resistance of zero when tested against each other - hence only one of them has to be wired to common ground on keyboard interface. Schematic diagram 2 (no common ground on fb board) http://i58.tinypic.com/3008jk1.jpg connect pins 1-4 by soldering and check with multimeter(ohm): pin 1 against 4: = zero = success Schematic diagram 3 (no common ground on keyboard interface): http://i62.tinypic.com/2568gns.jpg so if you found 2 pins for each key 1-4 (instead of 1 for each and a common ground = 5) you gotta solder 8 wires instead of 5 as shown above, meaning that the pins with the same color on kb int connected = keypress. http://i62.tinypic.com/2bd0yx.jpg http://i59.tinypic.com/rqyk4w.jpg http://i60.tinypic.com/wsehg.jpg http://i59.tinypic.com/2ahytfp.jpg http://i60.tinypic.com/2po9icz.jpg finally - http://i57.tinypic.com/n133gp.jpg TESTING Plug in to USB on PC/Mac or connect with bluetooth - http://i57.tinypic.com/25yuq85.jpg start text editor, press the buttons - when you get: http://i61.tinypic.com/hvnrx0.jpg you might have to recheck :) if you get: http://i61.tinypic.com/2lw8y81.jpg it´s good If a button press results in multiple inputs (e.g. you press Button 1 and "134" is the output) This is most probably a result of the conections on the board. If you don´t want to go into detail of the wiring of your board you might have to do the following: http://i62.tinypic.com/ay1du.jpg Just cut the lines leading away from your "to solder" pins with a flat screwdriver for each button. This stops the fb from working with the amp it was designed for, but it can be rewinded by a simple solder point easily if ever needed. Test again! FINISHING !!!!!!!UNPLUG!!!!!!!!!!!!! Fit the keyboard interface into your fb, make sure there is no short circuiting (easiest way - cover whole thing with gaffer tape !!!) http://i59.tinypic.com/1fhd8p.jpg please take a little more time than i obviously did here :) http://i61.tinypic.com/35ksw0l.jpg I had to drill a hole to make the cable fit - i left the original connector on the other side as it was - so it can still be used with line 6 equipment :) http://i61.tinypic.com/214w0h2.jpg Test again! ROCK If you like it HIT THANKS If you need support pm me – i´ll assist you. YOU HAVE TO POST A PIC or VID of your FINISHED PROJECT IN THIS THREAT!!!! Regards, R
    1 point
  10. Hey guys, been an avid user here for a while now. All of a sudden the other day, I can no longer access the ignition page (or whatever it is called, where you can serch for, download, and request CDLC). Whenever I click on the link, it just takes me to the sign in page, even though I asm already signed in. Any links seems to direct me back to the sign in also. How can I acess the Ignition page again? I used it without problems for a year or more. Thanks.
    1 point
  11. Damn it, the only free evening I have nowadays and I can't even download the CDLCs...
    0 points
This leaderboard is set to Indiana - Petersburg/GMT-04:00
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy