Skip to content
View in the app

A better way to browse. Learn more.

ResHax

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Help us keep the site running.

Error: function not found - rfactor2 script error

Featured Replies

  • Author
  • Localization

regin, posted Mon Apr 20, 2015 8:52 pm (4689)


Hi,

Sorry if this is the wrong place to do this. I'm trying to learn about rFactor2 tracks and am trying to use the quickbms 0.61 tool with the rfactor2 script from the same site to extract files from a GMT MAS file.

When I run the quickbms tool with the script I get this error in the command script type box

Error: function not found

Last script line before the error:
28 calldll MEMORY_FILE4 rfactor2_00475BD0_dll stdcall ... then some digits.

I've tried across multiple OSs and different files but keep coming across this error. Is there anything anyone can do to help me?!
  • Author
  • Localization

aluigi, posted Tue Apr 21, 2015 6:46 am (4696)


Interesting, it's a bug in the latest version of quickbms where, in fact, I made a little change to that part of the code.
Nice finding.

Going to fix it in quickbms 0.6.3.
  • Author
  • Localization

regin, posted Tue Apr 21, 2015 6:57 am (4699)


Thanks and thanks! I'll watch for it.
  • Author
  • Localization

aluigi, posted Tue Apr 21, 2015 9:05 am (4700)


To anyone interested in the technical reason of the issue:
QuickBMS uses a function for splitting a string into a list of arguments and in the previous versions it enclosed these arguments between quotes, for example "ARG1", "ARG2", "ARGn".
In the latest version I removed the quotes when not necessary (for example if there are no spaces in the argument) but the problem is that this function is used also by the bms script parsing when you use encryption and comtype calldll in your scripts, so the important #INPUT# argument was handled as a comment (remember that # is a comment) and the parsing was terminated.
That's the reason :)

I think I will release the new version before the end of the week.
  • Author
  • Localization

regin, posted Tue Apr 21, 2015 8:23 pm (4721)


I don't know if it's worth mentioning but I downloaded the oldest version I could find in the old versions part of the website - 0.5.1 - and still got the same errors. Hope this is helpful.
  • Author
  • Localization

aluigi, posted Tue Apr 21, 2015 8:45 pm (4724)


That's not possible.
When I tested the old quickbms I used just one of the 0.6* versions available on the website.
So it looks like you are still using 0.6.2.
  • Author
  • Localization

regin, posted Tue Apr 21, 2015 9:37 pm (4727)


Oh yeah you're right. Sorry - I'm annoyed with myself now because I thought to try an earlier version then somehow managed to mix them up.

0.5.1 comes up with an error too - something like unknown encryption / hashing type (calldll) - is that going to be the sane in the newest version or should I just shut up, be patient and try it when it arrives?!

It happened on all MAS files for an rFactor2 track, whether they were actually encrypted or not.
  • Author
  • Localization

aluigi, posted Wed Apr 22, 2015 5:18 am (4729)


Why do you want to use a version of 4 years ago?!
Use 0.6.1d which is the latest stable one and it works perfectly.
You don't have to wait for a new version.
  • Author
  • Localization

regin, posted Wed Apr 22, 2015 8:09 am (4733)


OK thanks it appears you're a genius. I do have common sense, it just appears that I need a nudge from you in order to use it.

Got 0.6. Extracted fine. Thank you - great work.
Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.