Ulver
|
Okay, Ive done all the reading and I cant get VERGE.EXE to open up my blank map. heh. im an artist this stuff is weird to me... i got Cs in programming class in high school :oP Anyway, this is what I got in my folder:
console.gif
maped.cfg
maped.exe
system.fnt
test.map
test.vsp
trans.tbl
system.vc
vcc.exe
verge.exe
user.cfg
When I drop system.vc over vcc.exe I get "preproc error unable to open system.vc". writting in vcc system in dos gets same results. just double clicking on vcc.exe says no input files. At this point I couldnt think of any other mindless thing to try. I made my system.cv file by making a txt file, leaving it blank, and naming it system.vc I think i did this part right... dunno whats going on. When I tried to just run verge it said "could not open user.cfg" which is just a renamed txt file with the word "end" written in there. Am I creating these files wrong or something? Please help get me started....
Posted on 2001-06-20 19:48:58
|
grenideer
|
Well, you're supposed to run vcc from a command prompt. First off, check your vc files. Right-click on them and go to properties. Check where it lists the MS-DOS name of the file. It should be file.vc, not file.vc.txt or anything else like that. If you don't have the correct ending file extension, then the easiet way to fix this is through a Dos Prompt. (ren file.vc.txt file.vc [that renames it]). Once you have one valid vc file, you can make copies of it to create more (or use someone elses'). Ass far as vcc, the easiest way to use it is to 'vcc all' so it compiles ALL of your vcs. The best way to do this is to right-click/properties vcc.exe, then go the the PROGRAM tab, and erase the last few characters '.exe' and replace them with ' all' [don't forget the space). Now you can just double-click that vcc.exe file from windows and it will compile everything for you. Need more help? Just ask.
Posted on 2001-06-22 13:59:14
|
invicticide
|
I'm assuming your test.map has been made properly, BTW :)
Set the contents of user.cfg to the following:
log
vidmode 320 240
sound_device 0
end
Now I'll explain each of those lines for future reference:
log
This tells Verge to write a verge.log of whatever it does every time you run it. Useful when you get into scripting cuz you can find your bugs and stuff. No real disadvantage to just leaving it on.
vidmode 320 240
This sets the video mode. This line is setting it to 320x240 resolution (that's pretty standard.) You could do vidmode 640 480 for hi-res.
sound_device 0
This sets up your sound. Probably not a biggie if you just have a test map, since there's probably not any sound yet (unless you gave it music already.) 0 is like auto-detect. If this doesn't work, try 1, 2, or 3. (But I think 3 is no sound, hmm, still worth a shot :)
end
Must have at the end of the user.cfg. Don't ask me why.
Okay, that's user.cfg. Now go to your system.vc and put in the following:
function void autoexec()
{
map("test.map");
}
The autoexec() function is the FIRST THING that Verge runs when you start it up. You can put anything in here eventually... intros and crap like that, maybe some init functions to load up game content. For now it just switches to test.map.
I notice you don't have a test.vc. In case you don't know, you have to have a VC file for every map. So, test.map needs a test.vc. The map VC file holds all the events, that is, what happens when you activate zones and talk to entities and stuff.
So create a test.vc (same process as creating system.vc) and put in it the following:
event // autoexec
{
setplayer(entityspawn(5,5,"player.chr"));
}
The // on the event line specifies a comment. I always use // to number my events, but you don't need it. setplayer sets an entity for the player to control. It usually needs a number for that entity, but entityspawn returns a number for the entity it creates, so that gets around that.
For this, you will need a player.chr. Find someone's Verge game (or go to the verge source) and rip off a CHR file, and rename it player.chr, and put it in your verge folder.
Now go to DOS and VCC ALL and you should be good! You can even wander around your little test map.
You might want to check the coordinates 5,5 on your map in case there's obstructions and what-not, and adjust those accordingly.
Hope I could help.
That is all.
--Invicticide
Posted on 2001-06-26 13:00:44
|
