Hello there everyone.
I decided to give this forum a chance, since theres tons of forums. Never really been bothered to go on forums for anything special..
To start with, idk if this is the right forum for / subforum to ask for this help im gonna ask for..
Okay to the point... ATM i''m working with Counter-Strike Source models (since i found my liking in it)..
i do not have any experience with Quake C (.qc) Files..
My .qc file keep giving me errors on compiling and making my model be max 50kb (which is way little for a player model)..
Any there could help me making a functionally .qc script which would be used for player models for counter-strike source (like a ct/t model, which can run around with guns and whatsoever)
IF YOU DO NOT UNDERSTAND THIS. TELL ME!...
This is the kind of models im trying to get working (NOTE : ITS NOT MINE THIS MODEL. ITS SIMPLY A EXAMPLE) :
[video=youtube;jkOdKT6Ux9U]http://www.youtube.com/watch?v=jkOdKT6Ux9U[/video]
[quote]
$modelname "Japser\miku_test1v1.mdl"
$cdmaterials "models\Japser"
$scale 3
$surfaceprop "flesh"
$sequence idle "miku_test1v1.smd" fps 15
$body mybody "miku_test1v1.smd"
$collisionmodel "miku_test1v1.smd" {
$concave
$maxconvexpieces 100
$mass 100.0
$inertia 1.00
$damping 0.00
$rotdamping 0.00
}
[/quote]
any help?
wonder if this forum is active <.<.... or just ignoring this 1..
either who. any there could help T.T?
Yea, you might wanna actually ask a question. You've just told us a story and posted a snippet.
[QUOTE=Busymonkey;31331385]Yea, you might wanna actually ask a question. You've just told us a story and posted a snippet.[/QUOTE]
Touche.... i will remake my main post then <.<.. if its that hard to understand
[editline]25th July 2011[/editline]
done. re-read top post now..
bump... any there could help?
Can you post the output of the compiler (error text, all of it) , or a screenshot of it? I can possibly troubleshoot it if I have that info.
[QUOTE=CAS303;31351720]Can you post the output of the compiler (error text, all of it) , or a screenshot of it? I can possibly troubleshoot it if I have that info.[/QUOTE]
i could do that... but wouldnt fix my low file size of my .mdl file (most likely not)
it wont let me upload a pic +_+...
[CODE]
D:\KerjaSampingan>"d:\steam\steamapps\acc-name\sourcesdk/bin/orangebox/bin/stu
diomdl" -nop4 D:\KerjaSampingan\miku_script.qc
qdir: "d:\kerjasampingan\"
gamedir: "d:\steam\steamapps\acc-name\counter-strike source\cstrike\"
g_path: "D:\KerjaSampingan\miku_script.qc"
Building binary model files...
Working on "miku_script.qc"
SMD MODEL miku_test1v1.smd
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Model has 2-dimensional geometry (less than 0.500 inches thick on any a
xis)!!!
WARNING: Error with convex elements of miku_test1v1.smd, building single convex!
!!!
Model has 37 convex sub-parts
Collision model completed.
---------------------
writing d:\steam\steamapps\acc-name\counter-strike source\cstrike\models/Japse
r\miku_test1v1.mdl:
bones 29396 bytes (101)
animations 132 bytes (1 anims) (1 frames) [0:00]
sequences 620 bytes (1 seq)
ik/pose 164 bytes
eyeballs 0 bytes (0 eyeballs)
flexes 0 bytes (0 flexes)
textures 72 bytes
keyvalues 0 bytes
bone transforms 18100 bytes
Collision model volume 2286710.00 in^3
collision 0 bytes
total 50384
---------------------
writing d:\steam\steamapps\acc-name\counter-strike source\cstrike\models/Japse
r\miku_test1v1.vvd:
vertices 305088 bytes (6356 vertices)
tangents 101696 bytes (6356 vertices)
total 406848 bytes
---------------------
Generating optimized mesh "d:\steam\steamapps\acc-name\counter-strike source\c
strike\models/Japser\miku_test1v1.sw.vtx":
body parts: 8 bytes
models: 20 bytes
model LODs: 12 bytes
meshes: 9 bytes
strip groups: 25 bytes
strips: 27 bytes
verts: 57204 bytes
indices: 56796 bytes
bone changes: 8 bytes
everything: 114133 bytes
---------------------
Generating optimized mesh "d:\steam\steamapps\acc-name\counter-strike source\c
strike\models/Japser\miku_test1v1.dx80.vtx":
body parts: 8 bytes
models: 20 bytes
model LODs: 12 bytes
meshes: 9 bytes
strip groups: 25 bytes
strips: 243 bytes
verts: 60453 bytes
indices: 56796 bytes
bone changes: 1088 bytes
everything: 118678 bytes
---------------------
Generating optimized mesh "d:\steam\steamapps\acc-name\counter-strike source\c
strike\models/Japser\miku_test1v1.dx90.vtx":
body parts: 8 bytes
models: 20 bytes
model LODs: 12 bytes
meshes: 9 bytes
strip groups: 25 bytes
strips: 81 bytes
verts: 58014 bytes
indices: 56796 bytes
bone changes: 920 bytes
everything: 115909 bytes
Completed "miku_script.qc"
D:\KerjaSampingan>pause
Press any key to continue . . .
[/CODE]
any help o.o?
Looking the .qc, looks like your phymodel model is wrong. Make a new one. (and make sure your mesh and ragdoll files are exported correctly)
[QUOTE=Maestro Fenix;31368431]Looking the .qc, looks like your phymodel model is wrong. Make a new one. (and make sure your mesh and ragdoll files are exported correctly)[/QUOTE]
i give up... nobody really read the first post. as its the .QC file i want.. which makes it possible for the purpose of being used for player models (which can move around)...i only took that model as an example due to i never done .qc files before...
ok so you want CSS player model ...
1. Your model must be rigged to CSS player model skeleton
2. If you want player model you cant use reference model as phy model (you can use phy model decompiled CSS model)
3. Decompile CSS player model and you have got good .QC for editing
[QUOTE=Jano952;31369840]ok so you want CSS player model ...
1. Your model must be rigged to CSS player model skeleton
2. If you want player model you cant use reference model as phy model (you can use phy model decompiled CSS model)
3. Decompile CSS player model and you have got good .QC for editing[/QUOTE]
well lets ignore the errors of my model atm and whatsoever and focus on the .qc file... anything around the model shouldnt be hard to fix really. its more the damned .qc file which i have no idea what to do with lol.. beside it gives instructions on the compilation.. so i wanted 1 there fitted to moveable models (player models, which can move around, use guns and whatsoever)...
Look in:
C:\Program Files (x86)\Steam\steamapps\*yourname*\sourcesdk_content\cstrike\modelsrc\urban
And you will find a series of .qc & .qci resources including a proper phymodel (urban_ragdoll.smd). It appears that you are using your reference mesh as your phymodel, hence why you are getting all of those compiler errors.
so in other words. i should just replace urban > with my model name / directory ?.. in those files
[QUOTE=MikuHatsune;31370435]so in other words. i should just replace urban > with my model name / directory ?.. in those files[/QUOTE]
Thats probably the quickest way to do it, but Id make a copy of the urban.qc file, rename it and edit that, so you still have a backup in case. Double check the paths when editing. Also if you don't have LOD refs remove the $lod and $shadowlod lines since the urban.qc uses those.
ah okay. helps me alot. since i got the .qc file stuff now :)
ill go by that for now
Sorry, you need to Log In to post a reply to this thread.