Jump to content

Welcome to CustomsForge Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account

Learn & Play Rocksmith!

Want to play the songs you love? Registration and the use of this website is 100% free.
The only thing you need is a legal copy of Rocksmith 2014 w/ a cable. Click here to buy it.
 
Having trouble logging in or registering? Please click "Support" below.


Announcements:

We're in the middle of finishing up Ignition4 development and need your help with donations to keep our development services running. The goal also pays for our servers & other CF services we use. Any amount helps: click here to donate.

Join us on Discord | Facebook | Twitter | Patreon | Merch | Volunteer | Newsletter Issue 10 (Aug) [Special Tool Edition] w/ New Ignition Preview


NejiHyuga900

NejiHyuga900

Member Since 10 Jun 2014
OFFLINE Last Active Jul 18 2019 10:06 AM
-----

In Topic: Latest EOF releases (8-21-2019)

18 July 2019 - 08:36 AM

Could you further describe what the issue was? Would EOF not display the forced strum gems as being larger, or did the note retain the "h" or "(h)" notation below it even after you apply "Note>HOPO>Force off" on it? If you find a way to reproduce the issue, let me know. Did this happen in all non real guitar tracks? I see an issue where the 3D preview won't display forced HOPO notes with the correct smaller size in pro guitar tracks, but that didn't seem to apply to the 2D rendering.

Depending on your luck, Windows may have automatically made a backup "shadow copy" of the settings file. To check for this, right click on the EOF program folder, select properties and then select the "Previous versions" tab. If any older versions of the folder are listed there, you could open the backup copy and salvage the config file.

If I were to create a new note to Force HOPO Off away from another note, it will work the way it is placed but once I drag that note into another note's HOPO range, the Force HOPO Off status (big notes on the 2D editing plane) will turn off and revert back to an auto HOPO (normal sized notes) and it will only toggle between auto and forced on (small note) in an auto-HOPO range. And yes, I only tested this on non-Real Guitar tracks (Guitar Hero/Rock Band-styled tracks). During the "error", I noticed the notations would either be "h", "(h)", or "." (with consecutive HOPOs) but now that big notes (forced strum) show up on a new EOF.ctg, "(h)" doesn't show up any more (I think "(h)" meant auto-hopo).

I was hoping to be able to recover the "corrupted" configuration file but trying to show Previous Versions in the properties any files I wanted to revert back to but that Windows 10 feature never ever worked for me for any saved files I was hoping to recover for anything. :( Like anything else on my computer, Windows 10 didn't back up EOF.ctg's previous saved versions.


In Topic: Latest EOF releases (8-21-2019)

17 July 2019 - 08:41 PM

Is this not working in EOF (EOF won't allow you to apply forced strum status) or not working in a particular rhythm game (the MIDI from EOF isn't working as wanted)? Either way, I'd probably need the EOF project file and details about which note can't be made force strum.

Yeah, EOF (May 5 2019 revision and the latest revision) won't allow me to apply forced strum status. I'll redownload a fresh version of EOF and its latest hotfix, it worked.

The problem does not lie within the chart files but rather, the issue lied within EOF.cfg. I deleted it and while it reset all of my preferences, Forced Strums are working again. I was going to show you the settings I had in it but after I restored the file and closed EOF, my new preferences oversaved my restored old preferences (I wish I opened it in Notepad++ before that happened). =/ Can't really show you the differences in my old EOF.cfg vs a new default one since I quickly messed that up but at least I got it working again.

When in doubt when a feature isn't working for some reason, delete EOF.cfg and reconfig settings. :P


In Topic: Latest EOF releases (8-21-2019)

17 July 2019 - 06:03 PM

Forced HOPO Off isn't working for me when I have a note in the auto-HOPO range of another note. Works with chords but won't work with single notes when I press H or try to toggle Forced HOPO Off.