• Extracting models from Insurgency
    11 replies, posted
Hello, does anyone know how to extract models and possibly workshop content from insurgency? Thanks.
gcfscape should work with insurgency vpks like normal, even workshop vpks (that should be located in steamapps/workshop/content/222880/<addon's workshop id> iirc)
I have tried opening up the workshop content with GCFscape and decompiling the mdl files with crowbar. However when I try to open it up in Blender after extracting the file I get an error. https://files.facepunch.com/forum/upload/174694/7f63714d-f3dd-4f9e-8cb6-d1a6393531cf/error.png
that seems like a problem specific to the qc/smd import plugins you have. i have never used blender at all so i definitely dont know anything about source engine specific plugins. you tried importing a qc file and not an smd file, right?
Yes, that is correct. But only because Crowbar extracted it in such format, no smd files were extracted in the decompiling process.
Did you try to decompile an anim file or something?
I'm not sure, I'll tell you my process to see if it helps in finding the problem. So the first thing I did was find the location of the workshop content. It is found in Local Disk > Program Files x86 > Steam > Steamapps > Workshop > Content > 22880 > 877100197. The numbers on the last two specify the game and the specific workshop content. In this case I'm trying to extract the C7E. https://steamcommunity.com/sharedfiles/filedetails/?id=877100197 The next thing I do is double click on the VPK file and it is opened up through GCFscape. From here I have two folders, models and materials. I click on models because I want the 3D object of the gun. I open the next and only folder in the models folder, "weapons." After that I have multiple files, a folder named "upgrades" (I assume these are attachments which I am not interested in), v_m16a3dx90.vtx, v_m16a3.mdl, v_m16a3.vvd, w_m16dx90.vtx, w_m16.mdl, and w_m16.vvd. Afterward, I tried decompiling both mdl files with Crowbar, of which gave me a single .qc file each. I tried importing both on blender but I get the error as shown above on both.
What version of crowbar are you using?
Newest one, .56. I had already successfully decompiled a few addons from Garry's Mod yesterday. It is much easier to do it on there as that one has a built in extractor and doesn't require GCFscape. Unfortunately it only works on addons specific to that game.
What's your decompile log?
Here it is:  Decompiling ".\v_m16a3.mdl" ...     Model version 49 detected.     Reading MDL file header ...     ... Reading MDL file header finished.     Checking for required files ...       WARNING: VTX file not found.       WARNING: VVD file not found.     ... Not all required files found, but decompiling available files.     Reading data ...       Reading MDL file ...       ... Reading MDL file finished.     ... Reading data finished.     Writing data ...       QC file:          v_m16a3.qc       Bone animation files:          menu.smd         idle.smd         glsetup.smd         delta_foregrip.smd         delta_iron.smd         delta_eotech.smd         delta_kobra.smd         delta_aimp.smd         delta_aimp2x.smd         delta_elcan.smd         delta_po.smd         delta_scope.smd         delta_gl.smd         delta_glsetup.smd         delta_glsetup_iron.smd         delta_deployed.smd         base_idle.smd         base_ready.smd         base_draw.smd         base_holster.smd         base_crawl.smd         base_down.smd         base_fire.smd         base_dryfire.smd         base_fireselect.smd         base_reload.smd         base_reloadempty.smd         base_sprint.smd         iron_down.smd         iron_fire.smd         iron_fire_a.smd         iron_fire_b.smd         iron_fire_c.smd         iron_fire_d.smd         iron_fire_e.smd         iron_fire_f.smd         iron_dryfire.smd         iron_fireselect.smd         foregrip_ready.smd         foregrip_draw.smd         foregrip_holster.smd         foregrip_down.smd         foregrip_crawl.smd         foregrip_fire.smd         foregrip_dryfire.smd         foregrip_fireselect.smd         foregrip_iron_down.smd         foregrip_iron_fire.smd         foregrip_iron_fire_a.smd         foregrip_iron_fire_b.smd         foregrip_iron_fire_c.smd         foregrip_iron_fire_d.smd         foregrip_iron_fire_e.smd         foregrip_iron_fire_f.smd         foregrip_iron_dryfire.smd         foregrip_iron_fireselect.smd         foregrip_reload.smd         foregrip_reloadempty.smd         foregrip_sprint.smd         gl_ready.smd         gl_draw.smd         gl_holster.smd         gl_down.smd         gl_crawl.smd         gl_fire.smd         gl_dryfire.smd         gl_fireselect.smd         gl_reload.smd         gl_reloadempty.smd         gl_sprint.smd         gl_iron_down.smd         gl_iron_fire.smd         gl_iron_fire_a.smd         gl_iron_fire_b.smd         gl_iron_fire_c.smd         gl_iron_fire_d.smd         gl_iron_fire_e.smd         gl_iron_fire_f.smd         gl_iron_dryfire.smd         gl_iron_fireselect.smd         glsetup_in.smd         glsetup_out.smd         glsetup_ready.smd         glsetup_draw.smd         glsetup_holster.smd         glsetup_down.smd         glsetup_crawl.smd         glsetup_fire.smd         glsetup_dryfire.smd         glsetup_reload.smd         glsetup_sprint.smd         glsetup_iron_down.smd         glsetup_iron_fire.smd         glsetup_iron_dryfire.smd         deployed_idle.smd         deployed_in.smd         deployed_out.smd         deployed_fire.smd         deployed_dryfire.smd         deployed_fireselect.smd         deployed_reload_half.smd         deployed_reload_empty.smd         deployed_iron.smd         deployed_iron_fire_1.smd         deployed_iron_fire_2.smd         deployed_iron_dryfire.smd         deployed_iron_fireselect.smd     ... Writing data finished.   ... Decompiling ".\v_m16a3.mdl" finished. ... Decompiling with Crowbar 0.56: "C:\Users\Zak\Desktop\Gmad\v_m16a3.mdl" finished. Although the smds are showing up on the log, they don't appear anywhere on the folder I specified it to extract to. Only the .qc file is visible.
" WARNING: VTX file not found. WARNING: VVD file not found." the problem is in the log make sure you have those in the same folder as your .mdl, with the same name
Sorry, you need to Log In to post a reply to this thread.