CG in Games tosyk's blog


Ho to use Ninja Ripper

Русский / English

Official support page on

The article describes how to "rip" models and textures of the games using as an API directx 8, 9, 11 versions, and import ripped models/textures into 3ds max. Important: if you're an experienced PC user, then your problem may be only getting properly uv. The rest is easy. However, I specifically "chewed" ripping process for all users.

Note: The article is designed for users familiar with working in 3ds Max and does not cover detail things such as, for example, texturing objects, setting up materials, etc.

For the conversion process, we need the following tools:

  • 3ds Max (i'm using 2009 х86) should work on versions: 2009-2013
  • Ninja Ripper v1.1.0 (ripper) Author: blackninja [page]
  • ninja_importer v1.3 (3ds max import script) Author: blackninja [download]

1. Ripper setting. Unpack the archive to any folder. Run the program.

Show all ripper features »

Extracting all available vertex information of the models (position, all the texture coordinates, normals, weights, BLENDWEIGHT, BLENDINDICES, BINORMAL, TANGENT), indices, textures, shaders. Theoretically all extracted information could be import into the 3D editor!
Support for D3D11, D3D9, D3D8 (processed, however not all methods/techniques, but should work for 95% of all games).

Show all ripper function description »

  • Target (DX8, DX9, DX11 application):
    • Exe - field for a direct path for the executable file of the application/game
    • Arg - field for additional settings for an executable file
    • Dir - field for a direct path to the folder containing the executable file (entered automatically when you select .exe, no need to change by the default)
  • No Wrapper - mode in which the ripper will try to run .exe of the application/game directly, using for ripping only intruder.dll, if this mode does not work (do not rip) then you need to select one of the wrapper modes!
  • wrapper modes - a modes in which ripper will copy d3dX.dll in to a folder containing the executable file of the application/game, after this ripper windows can be closed, then you can start the game from any location, copied d3dX.dll will automatically clinging into the game. Thus no longer need to run the ripper himself for this game.
    • D3D8 Wrapper - for directx8 games only
    • D3D9 Wrapper - for directx9 games only
    • D3D11 Wrapper - for directx11 games only

    Note: you need to delete .dll from the game folder manually (if necessary), ripper configurations is stored in the registry from now on!

  • RUN - button to start the application/game
  • Output Directory:
    • Dir - field for output folder (automatically entered), this folder can be selected manually, be sure that checkbox "Don't overwrite by EXE" is cheked
    • Browse - button to explore folder with selected .exe file
    • Don't overwrite by EXE - by activating this function, the choice of the executable file does not overwrite the output folder
  • Settings:
    • RIP - you can change rip button
    • Forced to save (Textures) - activating this will forced saving only texture

Select the game you want to "rip". In the Ripper window click the button '...' to select .exe of the game.

Note: You can add game's .exe by drag-and-drop from explorer window to the ripper window

Choose the mode in which will produce ripring process of the games. Mode depends on which directx game is running. Modes description:

• No Wrapper - mode in which the ripper will try to run .exe of the application/game directly, using for ripping only intruder.dll, if this mode does not work (do not rip) then you need to select one of the wrapper modes!

• wrapper modes - a modes in which ripper will copy d3dX.dll in to a folder containing the executable file of the application/game, after this ripper windows can be closed, then you can start the game from any location, copied d3dX.dll will automatically clinging into the game. Thus no longer need to run the ripper himself for this game.

• D3D8 Wrapper - for directx8 games only
• D3D9 Wrapper - for directx9 games only
• D3D11 Wrapper - for directx11 games only

Note: you need to delete .dll from the game folder manually (if necessary), ripper configurations is stored in the registry from now on! (the old version of ripper's settings are stored in the folder with the ripper)

Start the game by pressing the Run button:

2. Game rip process. After starting the game and choose the desired location click on the "rip" button, the default key is F10. After pressing F10 game will "freeze" for a second, then will run a little and then "freeze" again for about 5-25 seconds. Duration of ripping process depends on "quality" of the game and the computer capacity. During the ripping process in the game folder (where game .exe is located) will be created folder with models (.rip format) and textures (.dds format).

Pressing the rip textures button (default F9) will rip only the textures that will be stored in the same folder with the game's .exe.
You will know when ripping is finished by the continue of the game.
It should also be borne in mind that in some games, ripping process "hangs" the whole game, ie after ripping and "hangs out" of the game, you can continue from the same point at which the game "freezes". However, there are some games that continue running even during ripping and after the process is finished, you can run into SUV, and your rivals will be far ahead.

3. Importing models into 3ds max. Open 3ds max. Menu MAXScript > Run Script... choose a script, window opens:

Show all importer function description »

  • Source select (source selection and the import mode):
    • Group - import group files
    • Single - import single files
    • List File - import files from list (not implemented yet)
    • Input Dir/File - import source, the file or folder (depending on the selected mode)
    • RIP File Nums - field to enter the file numbers to import (Group mode only), the input format is: 0-15, 589, 67
  • Vertex Format (selecting the model building settings):
    • Auto - mode to automatically identify groups of data (vertices, normals, uv-coordinates), will work for most games
    • Manual - mode for manual definition of groups of data, you needed to import the models of the new games (mostly directx11)
    • Position (x,y,z) - fields for enter data defining the position of the vertices of the model, even in manual mode these parameters in 99% of games will not change
    • Normal (x,y,z) - fields for enter data defining the normals at each vertex of the model (not implemented yet)
    • TexCoord (u,v) - fields for enter data defining texture coordinates of the model, one of the most important parameters. For games, wich model imports without a proper uv-coordinates, a pair of UV always choosing by search. At the time is Identified that pairs can not exceed number 50, that is can be 6-7 or 18-19 or 24-25 or 39-40 etc. In very rare cases, a pair of uv can be 3-4 or 4-5 or 5-6, which is within the "normal field of definition", as well as 8-6 or 12-11, which is at odds with common sense, but may still be.
  • Transformations:
    • Scale - the scale of the imported model
    • Rotate - turn imported model on the selected axis
  • Tex.0 File Level - choice of a number of the texture, which applies to the model after import
  • Flip UV Vertical - will flip vertical texture coordinates
  • IMPORT - button to start the import process

To import a model click Browse button:

Choose .rip the file and click Open button. Model will load into 3ds max. If you do not like the result, change the Vertex Layout import mode from Auto to Manual, an additional options will be available:

Will attach an image for a visual understanding of what kind of numbers and what they are accountable (color/area in the image below correspond to the colors in the image above):

This picture shows the data template of the .rip file. From the template follows: green zone (model), blue zone (normal), orange zone (uv, texture coordinates), details:

  • vertex data (the model) is based on the first three values ​​(00=x, 01=y, 02=z), also the numbers correspond to what is in the importer, thus 00=0=x, 01=1=y, 02=2=z. These values ​​can be changed in the importer to accept any numbers, but in 99.99% of the games these values ​​remain unchanged, and it is better not to touch them at all
  • normal data (for smoothing groups models corresponding to the 03, 04, 05) - in the current version is not complete, changing the values not yield results
  • uv, texture coordinates - represented by two numbers (06, 07, or 07, 08 or 24, 25), not three as in the case of vertices or normals - in 80% of the games are the same, but there are games (eg: Battlefield : Bad Company 2 or NFS: Run) where you need to change these values to get proper uv​​, and sometimes even go in the values of "normal zone" (ie, they can be 03, 04), but they are never go into "verte zone". These values ​​need to change simple by search the numbers. In the picture below - an example.

Thus selecting the model by setting the import (uv, scale, rotation, etc.) then press the IMPORT button. The model will load into 3ds max.

You can also import models massively. To do this, instead of Single in Source Select choose Group and write the numbers corresponding to the .rip file's name this way: 15,489,0, 50-85 into RIP File Nums

After setting up import process press IMPORT button, all files that match the written numbers will be imported into 3ds max.

Note: If files imoported into 3ds max (models/textures) will be to many than 3ds max will crash. So choose and import exactly what ever you wanna work with by looking in textures.

4. About textures. Textures are always .dds files. They are automatically loaded into 3ds max. It should be noted that each model corresponds several textures, for example a model, it can have multiple textures with names,, etc. But you can only load one of these textures in 3ds max. What is the texture will be loaded is selecting in the importer by changing number in Tex.Num function.

Note: If you use a programs for generating "preview" for .dds files in Windows explorer (I use Mystic Thumbs) then when ripping dx11 games the mini-preview for such .dds will not be shown, because they have wrong file header, the problem is not solved yet. However you can edit/view those dx11 .dds files in photoshop/irfanview/etc.

5. Results. The results of some of the game's rips Battlefield: Bad Company 2, Battlefield 3, NFS: Run, Expendables 2:

Comments (227) Trackbacks (0)
  1. Hello :P I’m actually in no means familiar with the actual intention of this ripper, I would like to use it to rip Google Earth Pro. Now, I tried downloading many things that actually are intended for that, but they are either discontinued and not available anymore, or they are not available for my system.

    I actually got Google Earth to open and all in the ripper, but I guess that since nothing is happening, it is not the right software for the data I’m trying to collect?

    [quote][F038] Ninja Ripper 1.3.3 x86
    [F038] © 2004 – 2015 black_ninja

    [F038] LOG START
    [F038] Date/Time: 2015/10/27 22:02:27

    [F038] Inject mode: “intruder”

    [F038] Texture downscale max width : 4096
    [F038] Texture downscale max height: 4096
    [F038] Texture downscale value: 2

    [F038] D3D9.DLL loaded
    [F038] D3D9 ripper init
    [F038] Direct3DCreate9 hooked. Target: 0x68355B30
    [F038] D3D9 ripper uninit

    [F038] Loaded Modules List
    [F038] 0x00CF0000 C:\Program Files (x86)\Google\Google Earth Pro\client\googleearth.exe
    [F038] 0x77B90000 C:\WINDOWS\SYSTEM32\ntdll.dll
    [F038] 0x76C30000 C:\WINDOWS\SYSTEM32\KERNEL32.DLL
    [F038] 0x76A60000 C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    [F038] 0x686E0000 C:\WINDOWS\system32\apphelp.dll
    [F038] 0x627E0000 C:\Program Files (x86)\Google\Google Earth Pro\client\QtCore4.dll
    [F038] 0×69430000 C:\Program Files (x86)\Google\Google Earth Pro\client\MSVCP100.dll
    [F038] 0x690B0000 C:\Program Files (x86)\Google\Google Earth Pro\client\MSVCR100.dll
    [F038] 0×77160000 C:\WINDOWS\SYSTEM32\ADVAPI32.dll
    [F038] 0×75540000 C:\WINDOWS\SYSTEM32\SHELL32.dll
    [F038] 0x774B0000 C:\WINDOWS\SYSTEM32\PSAPI.DLL
    [F038] 0x626B0000 C:\Program Files (x86)\Google\Google Earth Pro\client\IGCore.dll
    [F038] 0×77960000 C:\WINDOWS\SYSTEM32\USER32.dll
    [F038] 0×77830000 C:\WINDOWS\SYSTEM32\ole32.dll
    [F038] 0x76F40000 C:\WINDOWS\SYSTEM32\WS2_32.dll
    [F038] 0×77710000 C:\WINDOWS\SYSTEM32\msvcrt.dll
    [F038] 0x76B40000 C:\WINDOWS\SYSTEM32\sechost.dll
    [F038] 0x773B0000 C:\WINDOWS\SYSTEM32\RPCRT4.dll
    [F038] 0x767F0000 C:\WINDOWS\SYSTEM32\combase.dll
    [F038] 0×77630000 C:\WINDOWS\SYSTEM32\SHLWAPI.dll
    [F038] 0x76F90000 C:\WINDOWS\SYSTEM32\GDI32.dll
    [F038] 0×77820000 C:\WINDOWS\SYSTEM32\NSI.dll
    [F038] 0×75390000 C:\WINDOWS\SYSTEM32\SspiCli.dll
    [F038] 0×75380000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
    [F038] 0×75320000 C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
    [F038] 0×77470000 C:\WINDOWS\system32\IMM32.DLL
    [F038] 0x76E20000 C:\WINDOWS\SYSTEM32\MSCTF.dll
    [F038] 0x693B0000 C:\Users\Ellen\Downloads\DeviceDoctor.7ZipOpener_mkdtfchztkfbm!App\ninjaripper1.3.3\ninjaripper1.3.3\x86\intruder.dll
    [F038] 0×70210000 C:\WINDOWS\SYSTEM32\winmm.DLL
    [F038] 0x701E0000 C:\WINDOWS\SYSTEM32\WINMMBASE.dll
    [F038] 0x777E0000 C:\WINDOWS\SYSTEM32\cfgmgr32.dll
    [F038] 0×75260000 C:\WINDOWS\SYSTEM32\DEVOBJ.dll
    [F038] 0x688C0000 C:\Program Files (x86)\Google\Google Earth Pro\client\IGUtils.DLL
    [F038] 0×68570000 C:\Program Files (x86)\Google\Google Earth Pro\client\IGMath.dll
    [F038] 0×62550000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\IGSg.dll
    [F038] 0×62490000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\IGAttrs.dll
    [F038] 0×62190000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\IGGfx.dll
    [F038] 0x6AC20000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\libEGL.dll
    [F038] 0x67F70000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\libGLESv2.dll
    [F038] 0×68320000 C:\WINDOWS\SYSTEM32\d3d9.dll
    [F038] 0x61F80000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\D3DCOMPILER_43.dll
    [F038] 0x61D80000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\ogles20\d3dx9_43.dll
    [F038] 0x6F250000 C:\WINDOWS\SYSTEM32\VERSION.dll
    [F038] 0x6FC50000 C:\WINDOWS\SYSTEM32\dwmapi.dll
    [F038] 0x60C40000 C:\Program Files (x86)\Google\Google Earth Pro\client\googleearth_pro.dll
    [F038] 0x6F3F0000 C:\WINDOWS\SYSTEM32\WININET.dll
    [F038] 0x60B80000 C:\Program Files (x86)\Google\Google Earth Pro\client\IGExportCommon.dll
    [F038] 0x70AE0000 C:\WINDOWS\SYSTEM32\WINHTTP.dll
    [F038] 0x6FAD0000 C:\WINDOWS\SYSTEM32\USP10.dll
    [F038] 0x6E5B0000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemyext.dll
    [F038] 0x603F0000 C:\Program Files (x86)\Google\Google Earth Pro\client\QtWebKit4.dll
    [F038] 0x770A0000 C:\WINDOWS\SYSTEM32\OLEAUT32.dll
    [F038] 0x5FE00000 C:\Program Files (x86)\Google\Google Earth Pro\client\QtGui4.dll
    [F038] 0x5FD70000 C:\Program Files (x86)\Google\Google Earth Pro\client\QtNetwork4.dll
    [F038] 0x5FC10000 C:\Program Files (x86)\Google\Google Earth Pro\client\Leap.dll
    [F038] 0x5FB80000 C:\WINDOWS\SYSTEM32\CRYPTUI.dll
    [F038] 0x69DB0000 C:\Program Files (x86)\Google\Google Earth Pro\client\ge_expat.dll
    [F038] 0×69240000 C:\WINDOWS\SYSTEM32\GLU32.dll
    [F038] 0x6A040000 C:\WINDOWS\SYSTEM32\SHFOLDER.dll
    [F038] 0x6CDC0000 C:\WINDOWS\SYSTEM32\urlmon.dll
    [F038] 0x5F5E0000 C:\Program Files (x86)\Google\Google Earth Pro\client\gdal17.dll
    [F038] 0x753B0000 C:\WINDOWS\SYSTEM32\CRYPT32.dll
    [F038] 0x5F4D0000 C:\Program Files (x86)\Google\Google Earth Pro\client\IGOpt.dll
    [F038] 0×69090000 C:\WINDOWS\SYSTEM32\AVIFIL32.dll
    [F038] 0x70B80000 C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
    [F038] 0x6FCA0000 C:\WINDOWS\SYSTEM32\Secur32.dll
    [F038] 0x6E350000 C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
    [F038] 0x6ECC0000 C:\WINDOWS\SYSTEM32\iertutil.dll
    [F038] 0×75300000 C:\WINDOWS\SYSTEM32\USERENV.dll
    [F038] 0x76B90000 C:\WINDOWS\SYSTEM32\COMDLG32.dll
    [F038] 0x750A0000 C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
    [F038] 0x5EBC0000 C:\WINDOWS\SYSTEM32\OPENGL32.dll
    [F038] 0x5EB10000 C:\WINDOWS\SYSTEM32\ODBC32.dll
    [F038] 0x774A0000 C:\WINDOWS\SYSTEM32\MSASN1.dll
    [F038] 0x689B0000 C:\WINDOWS\SYSTEM32\MSACM32.dll
    [F038] 0×68540000 C:\WINDOWS\SYSTEM32\MSVFW32.dll
    [F038] 0x70A80000 C:\WINDOWS\SYSTEM32\WINNSI.DLL
    [F038] 0x752E0000 C:\WINDOWS\SYSTEM32\profapi.dll
    [F038] 0x6F850000 C:\WINDOWS\WinSxS\\COMCTL32.dll
    [F038] 0x5EA20000 C:\WINDOWS\SYSTEM32\DDRAW.dll
    [F038] 0x693A0000 C:\WINDOWS\SYSTEM32\DCIMAN32.dll
    [F038] 0x709F0000 C:\WINDOWS\SYSTEM32\SHCORE.DLL
    [F038] 0x751A0000 C:\WINDOWS\SYSTEM32\kernel.appcore.dll
    [F038] 0x6FDD0000 C:\WINDOWS\system32\uxtheme.dll
    [F038] 0×76970000 C:\WINDOWS\SYSTEM32\clbcatq.dll
    [F038] 0x709A0000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll
    [F038] 0×70970000 C:\WINDOWS\system32\rsaenh.dll
    [F038] 0×70950000 C:\WINDOWS\SYSTEM32\bcrypt.dll
    [F038] 0×69230000 C:\Program Files (x86)\Google\Google Earth Pro\client\imageformats\qgif4.dll
    [F038] 0×68510000 C:\Program Files (x86)\Google\Google Earth Pro\client\imageformats\qjpeg4.dll
    [F038] 0x5A0F0000 C:\Program Files (x86)\Google\Google Earth Pro\client\icudt.dll
    [F038] 0x5E930000 C:\Program Files (x86)\Google\Google Earth Pro\client\Plugins\npgeinprocessplugin.dll
    [F038] 0x6E370000 C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
    [F038] 0x70A90000 C:\WINDOWS\system32\mswsock.dll
    [F038] 0x6E720000 C:\WINDOWS\SYSTEM32\DNSAPI.dll
    [F038] 0x6E4A0000 C:\Windows\System32\rasadhlp.dll
    [F038] 0x6B9C0000 C:\WINDOWS\SYSTEM32\nvumdshim.dll
    [F038] 0x771E0000 C:\WINDOWS\SYSTEM32\SETUPAPI.dll
    [F038] 0x6CC70000 C:\WINDOWS\system32\nvinit.dll
    [F038] 0x0F000000 C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\detoured.dll
    [F038] 0x6CA00000 C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvd3d9wrap.dll
    [F038] 0x6D7C0000 C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvdxgiwrap.dll
    [F038] 0x76DE0000 C:\WINDOWS\SYSTEM32\WINTRUST.dll
    [F038] 0×10000000 C:\WINDOWS\system32\nvspcap.dll
    [F038] 0×68160000 C:\Program Files (x86)\Google\Google Earth Pro\client\alchemy\optimizations\IGOptExtension.dll
    [F038] 0x6F7A0000 C:\WINDOWS\SYSTEM32\gpapi.dll
    [F038] 0x6E4B0000 C:\WINDOWS\System32\fwpuclnt.dll
    [F038] 0x6CF40000 C:\WINDOWS\SYSTEM32\ncrypt.dll
    [F038] 0x6CF10000 C:\WINDOWS\SYSTEM32\NTASN1.dll
    [F038] 0x687A0000 C:\Windows\SYSTEM32\cryptnet.dll
    [F038] 0x76D70000 C:\WINDOWS\SYSTEM32\WLDAP32.dll
    [F038] 0x69F00000 C:\WINDOWS\system32\propsys.dll
    [F038] 0x6F040000 C:\WINDOWS\WinSxS\\comctl32.dll
    [F038] 0×69710000 C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
    [F038] 0x69DD0000 C:\Windows\SYSTEM32\thumbcache.dll
    [F038] 0×68910000 C:\Users\Ellen\AppData\Roaming\Dropbox\bin\DropboxExt.28.dll
    [F038] 0×69000000 C:\WINDOWS\system32\mssprxy.dll
    [F038] LOG END[/quote]

  2. Sara (or Ellen), google earth probably uses openGL. If so it’s not supported.

  3. Sara, in google earth options you have to change rendering to Open Gl to DirectX and it works.

  4. Hi:

    is there any news on the problem with DCS 1.5 ModelViewer ???

  5. Hello Sara, (or others)

    Did it work with Google Earth?

    I’m trying to do the same thing but I can’t seem to get a rip when pressing F10 inside Google Earth.

    Also no folder is created in the Google Earth folder with the 3D data.

    I did get it to start up through NinjaRipper and yes, I did change the openGL towards DirectX but still no results.

    Any help from anyone would be appreciated, thank you!

  6. For those looking to rip Google Earth (also works on Mac):
    It requires a (virtual) directx 9c environment and tedious post processing, but then works as of today (Nov 8th 2015) with the latest Google Earth version (using it with 7.0 pro and successfully tested 7.2 standard- nb that Google Earth pro comes with a free license now directly from Google and gives you higher texture resolution).
    All tools apart from a max11 install (required) available for free on the web:
    - install oracle virtualbox (free) – pick version right for your OS
    - get a microsoft ie developer image “ie8 – winXP” from the Microsoft Dev site ( – free
    - check the virtual machine has directx 9 – nothing higher! (Run “dxdiag” using the “run…” command in the start menu)
    - ensure to install the hardware graphics support extension from the virtualbox guest additions cd image (menu “devices”)
    - set virtualbox to 2048mb ram and 128mb graphics, ensure 3D acceleration is on
    - update the virtual machine to directx 9c (Microsoft site)
    - install Google Earth/ pro 7.x on virtual box and ensure its set to Directx
    - start Google Earth through ninja ripper and rip
    - install an old max11 on the virtual machine and bulk import the ripped files (hundreds) using the script above with manual uv coord settings “7″/ “8″
    - save as max file for further processing in max or fbx for maya and export from the virtual machine (set up a shared folder to exchange files to host system)

    Then open on host machine in the 3D editing environment of your choice- you will notice hundreds of mesh blocks overlaid in the same space, but nicely textured. They come in 3-4 different LODs and require grouping and then matching in plan (that’s literally a puzzle game), but the task can be scripted as repetitive. should give you a decent chunk of city in about a day’s worth of working time.

  7. Hi Trum,
    thanks for the detailed instruction! I tried the same, in a virtual box WinXp Sp3 DirectX 9c machine, with Google Earth and Ninja Ripper 1.3.3, but had no success. Which Ninja setting do you use? Inruder or wrapper?
    In intruder mode, I get a logfile, in wrapper mode nothing happens at all.
    Is there something I’ve forgotten?

  8. Hi Dermi, i use intruder settings.
    Try running ninja ripper as administrator (runas…) – the password is the one on the desktop wallpaper in case you use the microsoft ie dev image. Also note that ninja ripper writes the files to the respective program directory, so you should find your frames in a ninja ripper folder wherever your google earth sits (with a non admin account or UAC ninja ripper cannot write to the program dir).
    make sure fn keys are mapped correctly – if you use a laptop, typically fn+f10 does the trick.
    also check again whether your virtualbox confirms that 3d graphics acceleration is active (otherwise check your guest additions CD), that you have assigned enough graphics ram and verify google earth is running in directx mode – that’s all i can think of as for error sources, really…

  9. the “runas” was the missing hint – although the other user also has admin rights and the logfile was written to the output directory, it seems to work only as admin user …
    Thanks a lot!

  10. Hi still no news about ripping from DCS in DX 11

Leave a comment


No trackbacks yet.