Ninja Ripper

[saso]

Hello everyone,
My name is Saso and I'm from a small town in Italy,
I work with a group of work that deals with a mod for Rfactor on hillclimbs,
I have a problemam,
I used ninja ripper to copy a Grid Autosport car on the game and when I imported with 3DStudio Max model of the machine I get so, it seems a puzzle,
does anyone know how to solve this problem is solvable if and can 'help me please?
Hello and thanks

saso_001.jpg

[SergeantJoe]

There's no problem here, that's just how it works. You have the put the pieces back together yourself.

[saso]

thanks for the reply, however I have already solved, thanks to a tool for simulators Sim named 3dsimed, with a bit of calm and patience I repositioned all components

[XiNAVRO]

Question regarding mesh, and orphaned edges:

Currently I'm trying to extract some resources from Dark Souls II (Steam version) to convert them for Skyrim.
Seems like the ripper has no problem acquiring the meshes, but I do have an issue where the result mesh is having odd edges connecting vertices that are not supposed to be connected to begin with.

Here's what I'm talking about:


Cleaning these up is taking more time than the actual porting process.

I have tried 3DSMax and the RIP import script, also tried using Noesis to convert the RIP files into OBJ, and port them to Blender.
Same issue pertains. I'm not really sure if anyone else is also having this problem. Any insights?

[Acewell]

Someone had a similar problem a while ago and MrAdults says use the -killdupfaces command in Noesis to clean it up.

viewtopic.php?p=80770#p80770
viewtopic.php?p=80782#p80782

viewtopic.php?p=80826#p80826

before


after

[XiNAVRO]

Someone had a similar problem a while ago and MrAdults says use the -killdupfaces command in Noesis to clean it up.

Thanks for the link; although the cleanup did work, this time it destroyed the UV mapping instead.
Any similar command or tool I could use in 3DSMax for cleaning?

[Acewell]

I'm not familiar with 3dsMax, but I think most major 3d applications have tools to transfer or copy UVs from one object to another. If messed up UVs is your only issue now, you could copy the UVs from the uncleaned model to the cleaned-up one.

[Pork Chops and Beans]

Hello guys, I'm new in 3D ripping and especially this tool! I've been trying to use Ninja Ripper to rip the L.A. Noire's police stations map, I used this wonderful tool before with Kane & Lynch: Dead Men and it worked splendidly, I used D3D9 wraper for Kane & Lynch. But I tried L.A. Noire with same wrapper and it didn't work, every time I tried to launched it, it crashed saying something about intruder error. I triedo use Intruder in the configuration and D3D11 wrapper, both allowed me to be in game, but when I pressed F10 or F9, it didn't do anything. I'm wondering what I did wrong here? Thanks!

[lionheartuk]

Is there any way to get ahold of the Source for this at all?

Or perhaps for the original creator to compile ninjaripper for 64 bit too, many games are turning to 64bit, and Ninja Ripper can't use 64bit applications.

What would be really cool though, is a way to rip via a launcher, far too many games have launchers, especially steam games, and even if the point NR at the games .exe it still launches the launcher anyway.

[Zoetropes]

I'm not sure what causes this, I use Ninja per http://souls.darknode.org/ and it works just fine.

Question regarding mesh, and orphaned edges:

Currently I'm trying to extract some resources from Dark Souls II (Steam version) to convert them for Skyrim.
Seems like the ripper has no problem acquiring the meshes, but I do have an issue where the result mesh is having odd edges connecting vertices that are not supposed to be connected to begin with.

Here's what I'm talking about:
[snip]

Cleaning these up is taking more time than the actual porting process.

I have tried 3DSMax and the RIP import script, also tried using Noesis to convert the RIP files into OBJ, and port them to Blender.
Same issue pertains. I'm not really sure if anyone else is also having this problem. Any insights?

[zookone]

My Ninja is getting smacked down...

Win7 64bit machine, using Ninja Ripper in dx11 wrapper mode. I think I have to use wrapper mode because game launcher blocks the ability to use intruder mode.

F9 texture capture is working for textures but unable to F10 capture models. Does anyone have a tip on what might be wrong? Maybe just doesn't work?

Sorry for the long log post below... Thanks

Code: Select all

Ninja Ripper v1.1.4
(c)2004-2013 black_ninja

Sat Dec 13 12:18:15 2014

LOG START

D3D11.DLL loaded
D3D11 Ripper Init
D3D11.D3D11CreateDeviceAndSwapChain() hooked
D3D11.D3D11CreateDevice() hooked
DXGI.CreateDXGIFactory() hooked
DXGI.CreateDXGIFactory1() hooked
D3D11.D3D11CreateDeviceAndSwapChain() ret: 0x00000001
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

D3D11.D3D11CreateDevice() ret: 0x00000001
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

D3D11.D3D11CreateDeviceAndSwapChain() ret: 0x00000000
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

ID3D11DeviceContext_DrawIndexed hooked Address: 0x67C14BB0
ID3D11DeviceContext_Draw hooked Address: 0x67C22780
ID3D11DeviceContext_DrawAuto hooked Address: 0x67C00EA0
ID3D11DeviceContext_DrawIndexedInstanced hooked Address: 0x67BFF220
ID3D11DeviceContext_DrawIndexedInstancedIndirect hooked Address: 0x67C00EC0
ID3D11DeviceContext_DrawInstanced hooked Address: 0x67BFF250
ID3D11DeviceContext_PSSetShaderResources hooked Address: 0x67BFEA80
ID3D11Device_CreateInputLayout hooked Address: 0x67B89BA6
D3D11.D3D11CreateDevice() ret: 0x00000000
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

D3D11.D3D11CreateDeviceAndSwapChain() ret: 0x00000000
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

D3D11.D3D11CreateDevice() ret: 0x00000000
DriverType  : D3D_DRIVER_TYPE_UNKNOWN
FeatureLevel: D3D_FEATURE_LEVEL_11_0

D3D11 Ripper Uninit

Loaded Modules List
0x00230000 C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\EliteDangerous32.exe
0x777F0000 C:\Windows\SysWOW64\ntdll.dll
0x76300000 C:\Windows\syswow64\kernel32.dll
0x75E70000 C:\Windows\syswow64\KERNELBASE.dll
0x75B70000 C:\Windows\syswow64\GDI32.dll
0x758E0000 C:\Windows\syswow64\USER32.dll
0x757A0000 C:\Windows\syswow64\ADVAPI32.dll
0x75AA0000 C:\Windows\syswow64\msvcrt.dll
0x75720000 C:\Windows\SysWOW64\sechost.dll
0x766A0000 C:\Windows\syswow64\RPCRT4.dll
0x75190000 C:\Windows\syswow64\SspiCli.dll
0x75180000 C:\Windows\syswow64\CRYPTBASE.dll
0x75A90000 C:\Windows\syswow64\LPK.dll
0x759E0000 C:\Windows\syswow64\USP10.dll
0x767A0000 C:\Windows\syswow64\SHELL32.dll
0x75D50000 C:\Windows\syswow64\SHLWAPI.dll
0x76150000 C:\Windows\syswow64\ole32.dll
0x75CC0000 C:\Windows\syswow64\OLEAUT32.dll
0x72DF0000 C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\d3d11.dll
0x67CF0000 C:\Windows\system32\dxgi.dll
0x750B0000 C:\Windows\system32\VERSION.dll
0x6AF70000 C:\Windows\system32\dwmapi.dll
0x74F00000 C:\Windows\system32\dbghelp.dll
0x725D0000 C:\Windows\system32\WINMM.dll
0x00070000 C:\Windows\system32\XINPUT1_3.dll
0x75420000 C:\Windows\syswow64\SETUPAPI.dll
0x75E30000 C:\Windows\syswow64\CFGMGR32.dll
0x752E0000 C:\Windows\syswow64\DEVOBJ.dll
0x72DC0000 C:\Windows\system32\DINPUT8.dll
0x758A0000 C:\Windows\syswow64\WS2_32.dll
0x75E60000 C:\Windows\syswow64\NSI.dll
0x70CA0000 C:\Windows\system32\IPHLPAPI.DLL
0x70C90000 C:\Windows\system32\WINNSI.DLL
0x67EC0000 C:\Windows\system32\OPENGL32.dll
0x67E90000 C:\Windows\system32\GLU32.dll
0x67DA0000 C:\Windows\system32\DDRAW.dll
0x69B60000 C:\Windows\system32\DCIMAN32.dll
0x70F20000 C:\Windows\system32\WINHTTP.dll
0x70ED0000 C:\Windows\system32\webio.dll
0x72DA0000 C:\Windows\system32\VCOMP110.DLL
0x75840000 C:\Windows\system32\IMM32.DLL
0x75210000 C:\Windows\syswow64\MSCTF.dll
0x72C10000 C:\Ninja\intruder.dll
0x71070000 C:\Windows\system32\mswsock.dll
0x6B7D0000 C:\Windows\System32\wship6.dll
0x76140000 C:\Windows\syswow64\profapi.dll
0x67A90000 C:\Windows\system32\credssp.dll
0x6FC80000 C:\Windows\system32\DNSAPI.dll
0x6B7A0000 C:\Program Files (x86)\Bonjour\mdnsNSP.dll
0x6B750000 C:\Windows\System32\fwpuclnt.dll
0x6B790000 C:\Windows\system32\rasadhlp.dll
0x71060000 C:\Windows\System32\wshtcpip.dll
0x69C90000 C:\Windows\system32\dhcpcsvc6.DLL
0x6A010000 C:\Windows\system32\dhcpcsvc.DLL
0x67A10000 C:\Windows\system32\NLAapi.dll
0x67A00000 C:\Windows\system32\napinsp.dll
0x679E0000 C:\Windows\system32\pnrpnsp.dll
0x679C0000 C:\Windows\System32\winrnr.dll
0x75C00000 C:\Windows\syswow64\WINTRUST.dll
0x75300000 C:\Windows\syswow64\CRYPT32.dll
0x751F0000 C:\Windows\syswow64\MSASN1.dll
0x67B70000 C:\Windows\system32\d3d11.dll
0x72D60000 C:\Ninja\d3dx11_43.dll
0x46B20000 C:\Windows\system32\nvspcap.dll
0x6AF90000 C:\Windows\system32\uxtheme.dll
0x75C30000 C:\Windows\syswow64\CLBCatQ.DLL
0x60D80000 C:\Windows\system32\nvwgf2um.dll
0x75B60000 C:\Windows\syswow64\PSAPI.DLL
0x70A20000 C:\Windows\system32\bcrypt.dll
0x709E0000 C:\Windows\SysWOW64\bcryptprimitives.dll
0x73B10000 C:\Windows\system32\HID.DLL
0x74EC0000 C:\Windows\system32\CRYPTSP.dll
0x74E80000 C:\Windows\system32\rsaenh.dll
0x74E70000 C:\Windows\system32\RpcRtRemote.dll
0x73E60000 C:\Windows\System32\MMDevApi.dll
0x67F90000 C:\Windows\System32\PROPSYS.dll
0x73E20000 C:\Windows\system32\AUDIOSES.DLL
0x72D30000 C:\Windows\system32\avrt.dll
0x6AE60000 C:\Windows\system32\wdmaud.drv
0x72D50000 C:\Windows\system32\ksuser.dll
0x72D20000 C:\Windows\system32\msacm32.drv
0x72BF0000 C:\Windows\system32\MSACM32.dll
0x72D10000 C:\Windows\system32\midimap.dll
0x73EC0000 C:\Windows\SysWOW64\schannel.dll
0x69B70000 C:\Windows\system32\secur32.dll
0x70A40000 C:\Windows\system32\ncrypt.dll
0x76650000 C:\Windows\syswow64\USERENV.dll
0x70840000 C:\Windows\system32\GPAPI.dll
0x45450000 C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\dsfVorbisDecoder.dll
0x66CA0000 C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
0x66ED0000 C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
0x755C0000 C:\Windows\syswow64\urlmon.dll
0x75A80000 C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
0x75F50000 C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
0x75710000 C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
0x75B50000 C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
0x76790000 C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
0x75200000 C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
0x777C0000 C:\Windows\syswow64\normaliz.DLL
0x76410000 C:\Windows\syswow64\iertutil.dll
0x75F60000 C:\Windows\syswow64\WININET.dll
0x6B1A0000 C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
0x454D0000 C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\vp8decoder.dll
0x45F70000 C:\Program Files (x86)\Frontier\EDLaunch\Products\FORC-FDEV-D-1002\webmsplit.dll
0x66A90000 C:\Windows\system32\d3dcompiler_43.dll


LOG END

Sat Dec 13 12:19:23 2014

[lionheartuk]

[quote="zookone"] My Ninja is getting smacked down...

Win7 64bit machine, using Ninja Ripper in dx11 wrapper mode. I think I have to use wrapper mode because game launcher blocks the ability to use intruder mode.

F9 texture capture is working for textures but unable to F10 capture models. Does anyone have a tip on what might be wrong? Maybe just doesn't work?

Sorry for the long log post below... Thanks

Are you trying to access a game thats 64bit, Ninja Ripper is 32bit and only works with 32bit applications.

However I was sent the source a few days back by the original creator as he's no longer working on it. I've taken a good look but changing everything from 32bit to 64bit functions and calls is a bit beyond my level, I understand a little of it, so if anyone thinks they're upto that challenge, I'll sent it on over.

I intended to upload it to github but I've not had the time so far.

[zookone]

No the game is 32bit.

[blackninja]

NinjaRipper is open source now. Merry Christmas

https://github.com/blackninja2/ninjaripper

[Mr.Mouse]

Excellent, thanks for letting us know!