I have attempted several times to use Ninjaripper with Chrome as instructed in Destiny WebGL Model Rips, however I have encountered several repeating issues, which have prevented me from managing any success, and the official Ninjaripper resources have either no answer, or too limited experience to help.
To explain, thus far my efforts at launching Ninjaripper with Chrome have failed due to the basic launch not working at all. Ninjaripper itself will start, however when selecting 'Intruder Inject' and then 'Run' to initiate Chrome, nothing happens. The program greys for a moment to indicate another process taking priority, and then it does nothing at all. Having believed this as a fault of my own, or simply an incompatibility, I instead switched to D3D11, however doing so and then attempting to run instead results in an error of "could not create dir(ectory)" with a code of 0x000005.
The original thread with the steps for obtaining Destiny models is quite old, so I am hoping to avoid Necroposting, however we do not have any private messaging systems, so I cannot ask the person directly. At this point, this is my last resort, as I do not know what else to do. Can anyone assist?
It took me a long time to find any information on this, but apparently WebGL very recently got an update that breaks current iterations of Ninja Ripper. Like, "somewhere around October" recently.
I've heard that if you use legacy versions of browsers, you can get Ninja Ripper to work. But I've not tested it.
Legacy versions? I apologize for not understanding, as I am quite very new to this. How might I obtain a legacy version?
Legacy versions just mean older versions. In this case, you'll want a version of Chrome that's a few versions out of date, preferably from before October, if not maybe even before maybe June. Far enough back as to not have the latest WebGL update.
How you get such an older version is a different story. You'll have to figure that out yourself.
Ah, many thanks! Fortunately, it is as easy as googling 'older versions of chrome', however I was distinctly unaware that it would be as easy as searching for a version only a few months out of date. I will attempt this, and let you know of the results.
This "cannot create dir" is a system protection. You don't want any unregistered program to write things to your harddrive. You may have to relocate the application and/or rip folder on a not system drive and/or run ninjaripper as admin and/or change it's permission thingies manually. Plus, it doesn't actually matter which technique (intruder or wrapper) you use, as long as you get an output from atleast one of them. And the thing that makes it not render is exactly a result of the browser fixes. The rippers code insertion. If a detour into the code is detected it may not execute. Actually a security thing.
Just for testing. I dunno when chrome patched the ninja, but firefox, kinda. Assuming you rip from the lowlidev gear viewer. I ripped a thing with ninja 1.7.1 x86 intruder, firefox 50 - 52 (~latest working). Depending on the 'size' of the model, you may get away with just 1 second rip interval without wasting your harddrive. This 5 seconds ripped pretty clean and constant ~9 loops of a obviously stacked mesh rendered model.
https://i.imgur.com/Ys3dL8K.jpg
Thank you for the advice, however the situation, while improved, still seems to be one enduring various errors. When attempting to launch the recommended program with Intruder Inject, I receive a message (finally something more than nothing at all!) stating that "The application was unable to start correctly (0x0000005). Click OK to close the application."
So, I opted instead for the D3D options, and reliably Firefox crashed completely prior to the models themselves loading.
Yep. Is possible it crashes. Iirc firefox at some point refused to load from the second partition, where i plain copied it. Since i moved the (re-)install(s) back into the program files folders it works again. It could also be you using an ninja version? i think some of them are not really working correct anymore. And i dunno if AV software can interfere. I live dangerous. If they did interfere, they would potentially throw a notification of some sort. About that noesis thing, are you certain you copied the plugin into the correct noesis script folder? All the importers (max, blender and noesis to choose) are only delivered since 1.6.3, i think, in case you use an older version of the ninja. Might wanna upgrade.
Ah! There is a script folder specifically for noesis? I am curious now, which folder I should deposit the files into.
https://i.imgur.com/6hzmfxb.jpg
Your progress has inspired me to try this myself.
I am running Firefox 59 64-bit, and the D3D9 causes the relevant Firefox tabs to crash for me. How did you get around this?
Close everything else. All windows that are not Firefox should be closed, with the exception of Ninjaripper when launching.
If that does not work, consider using the Firefox 52 version that dlight has linked at the bottom of his post, and open it using the x86 version of Ninjaripper (unless you have only a x64 computer).
So what I did to finally get it working is this:
0.) If you have any versions of Mozilla Firefox installed, uninstall them via Add or Remove Programs, and then go into regedit and delete everything related to Mozilla Firefox in the HKEY_LOCAL_MACHINE/Software folder.
1.) Go here and download Mozilla Firefox 47.0 EME-free 32-bit: Directory Listing . Then install it. When prompted, run Mozilla after installing to verify that it works. Then close out of Firefox.
2.) Go here and download Ninja Ripper 1.7.1: Скачать Ninja Ripper . Then extract it, ideally to a hard-drive other than the one Mozilla Firefox is installed to, if you can afford it.
3.) Inside the main Ninja Ripper extract, there are two folders: "x86" and "x64". You want to run as administrator the Ninja Ripper executable in the "x86" folder.
4.) In the Ninja Ripper program that's now launched, set your output folder. I put it on an "out/" folder inside the main Ninja Ripper extract. Click Settings, and set the bindings up as such:
All: F4
Textures: F8
Forced: F9
Forced Rip Interval: 10 sec
No checkboxes checked.
5.) Press Okay to save your settings. Press the "..." next to the "Exe:" line, and choose the Mozilla Firefox you just installed. Default path is "C:/Program Files (x86)/Mozilla Firefox/firefox.exe"
6.) Set the drop-down to D3D9 Wrapper, and press Run. Firefox will launch.
7.) Browse to the page with the WebGL you want to rip from. Load up the 3D model window, click into it to get focus, and if possible, pan around a few times to see all parts of the model. This is to verify everything is loaded.
8.) Press, one after the other, F4, F8, and F9. Your browser / computer might freeze after each hit - this is not only normal, but is exactly what you want.
9.) Once you have hit all three keys, go to your output folder. There should be a folder there, and within that folder and a few other folders there should be some textures (I believe they will always be DDS files) and a bunch of .RIP files. Congratulations, you have successfully ripped your WebGL model.
You should run x86 anyway, since firefox 52 is a x86 application. Iirc, loading it with x64 won't rip anything.
@Gmod4ever looks a lil complicated. I dunno anymore if win7 could run 2 different versions simultaneously. Fair. mmh
I have had some time to extract the models, however I have since encountered a unique and unusual issue - the models do not seem to retain their texture mapping when exported in .obj format. I have loaded them into blender, only to realize that the textures no longer apply as they should, one example being a set of shotgun shells being instead grey, rather than matching the colors or patterns intended.
After a less than expected automatic update, Firefox 52 will no longer function. When loading the model, a 'can't create directory' error will appear and the page will crash. Several attempts to reinstall the Firefox 52 browser have been made. Might you know what is wrong?
Ehh. No. How would i know? I don't autoupgrade. My version will never change. You shoulda set that up, perhaps. Ofc you could uninstall. I don't think you may be able to install a downgrade on top of the upgraded program. You may be able to reinstall in another path, as a 'seperate' program. You could wipe all the mozilla appdata, profile data and registry data, to make sure the machine doesn't know anything about any prior installed version. Far from that i have no idea. Maybe keep the uptodate version. On my setup the registry data only exists for the current version. All versions work tho and run the same appdata and profiles. Sure consistent profile data storage. mmhmmh
Alas, it was not intentional. I had disabled the update mechanism during installation, however that evidently did not disable autoupdate in general, so much as it simply disabled the ability to do so silently. I suspect that whatever has resulted from the update has since contaminated the software, as it no longer suggests an automatic update being needed, and the error persists despite several wipes of the Mozilla folders via regedit.
I am at a loss as to what it may be, as Firefox is somehow retaining the data regardless of reinstallation/deletion of the entire folder and regedit data.
Just wipe all of it. The appdata folders contain your profile, cache and settings. Also 52 and later x64 versions don't share the same registry data. x86 is in the wownode. I'm not sure which one you removed or how relevant those should be to run 52. As it works for me, it may not read alot of the later key data. There's nothing valuable in there anyway.
https://i.imgur.com/EmFjBdj.jpg
After you have wiped it you should be able to reinstall 52 and disable the autoupgrade so it will never update. It should also create a factory default profile. All other compatitbility issues are perhaps OS relevant. I should have asked before, but what are you using? Win10 or something older? I can't tell how the compatility is on that old stuff. The basic software installation and program data should be the same tho.
I am currently using the latest iteration of windows eight, on a laptop no less. Another had pointed out that Ninjaripper may be experiencing issues due to hardware. Fortunately, the issues persisted even on a(n older) desktop, so I suspected it to be more.
After the software equivalent of percussive maintenance, I downgraded to Firefox 51, and managed a workable but unstable alternative. It works now, though there are occasional hiccups that result in tab crashing. Still, it is better than before, in which there was no progress at all.
However, something odd occurred during the use of Firefox 51, that being another automatic update. Keep in mind, this was with the autoupdate function in the settings turned off. It still performed an automatic update regardless, and I cannot yet determine if it has taken effect, or if it has done nothing. Either way, I am still thankful for your guide thus far, and will use it to correct Firefox 52 if there is any sudden and consistent failure with 51.
I may ask of your help in the future. You both (dlight and GMod4ever) have helped me along much further than I would have managed alone. Without you both, all of this would have been impossible.
Sorry, you need to Log In to post a reply to this thread.
