Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Inquisitor on August 12, 2002, 11:17:47 pm
-
First off, report bugs in bugzilla:
http://fs2source.warpcore.org/bugzilla/ (http://fs2source.warpcore.org/bugzilla/)
Not in this forum or this thread, I will ignore those posted in the forum ;) You will have to sign up to use bugzilla, get over it ;)
Second:
The exe can be downloaded at http://fs2source.warpcore.org/fs2_open.exe (http://fs2source.warpcore.org/fs2_open.exe)
EDIT: These links are all dead. :( A new Windows build has been uploaded at http://scp.indiegames.us/builds/WIN/fs2_open_3_2.zip
You should place this exe in your FS2 install directory. A readme is forthcoming, but you can get a sense for the changes at:
http://fs2source.warpcore.org/cgi-bin/cvsweb/cvsweb.cgi/fs2_open/code/Attic/ChangeLog?rev=1.1&content-type=text/x-cvsweb-markup (http://fs2source.warpcore.org/cgi-bin/cvsweb/cvsweb.cgi/fs2_open/code/Attic/ChangeLog?rev=1.1&content-type=text/x-cvsweb-markup)
Ok, have at it!
-edit-
actually, anything completely showstopper, email directly to me.
-
Nice beams :nod:
(http://icestar.hypermart.net/blackdove/Beams.jpg)
*this review brought to you by the stupid grunt that can't spell the word "programming" ;)*
-
I better replace my broken joystick.
-
w00t!
*runs off in a wild ebullience of downloading delight*
-
beam texture tileing is fun isn't it
remember there are also fighter beams and SSM tag missles too
(you did get all of that didn't you)
and the glow point code is in there too, but you probly won't see any effect unless you have the three altered POFs I made or alter them you're self
-
w0000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000t!
Sorry., had to get that out my system. :D
Don't you just love it when a Plan™ comes together? ;)
-
Glad everyone seems to be enjoying this :nod:
And just remember: this is only the beginning ;7
-
Ack! double-post!
-
Being an idiot in the ways of the source code, how do i use the .exe?
Edit: And Bob, how about rereleasing those models for those of us who missed them?
-
put it into your /games/freespace2 folder and run it from there =)
-
Well it sure does crash alot, anytime it encoutered a graphical change in the interface, it crashed. I disabled some of my techroom interfaces... loading up a mission with a new background... it crashed... so i loaded a dry mission... called in a support ship... it crashed.
:no:
-
Eep! Funny I've had no problems and I've got more mods installed than you can shake a beam at. This includes many added backgrounds n'stuff
-
vadar:
go to bugzilla and enter as much information as possible on that, should be plenty of fields to enter info about your setup. that way we can try to replicate it, and work with you to hunt it down and kill it :)
this is release 1 of many, and there will be bugs.
You guys are collectively the QA department :)
-
Originally posted by Inquisitor
You guys are collectively the QA department :)
Scary :)
I'll give it a look see in a bit. Have to reinstall FS2....
Edit:
Should someone put together a simple mission for each release, showing some of the changes? I would volunteer if you like.
I will be concentrating my source code work mainly on the AI, as i have many changes in mind for it.
Also, we should have someone testing each release with the various mods out, making sure nothing goes wrong with them.
-
Originally posted by BD
Nice beams :nod:
(http://icestar.hypermart.net/blackdove/Beams.jpg)
*this review brought to you by the stupid grunt that can't spell the word "programming" ;)*
No offense, but the beams in that pic look 2d. Kind of flat. But heck, its a first release.
EDIT:I kind of like the beams from the original fs2. But better graphics in other forms would be great. After all, this engine is 3 years old. We need to do some work on it. I'll help in any way possible, except coding. I regret that I don't know c++.
-
Drannon: Yes :)
-
maybe including a readme.txt/html, where the people responsible for changes explains what exactly is required to make use of theire changes / modifications. and what is a nono and a plz do.
-
DUH
I forgot to arrange for the fred2 release.
It has alot of the stuff you need to make some of these things work...
Kazan's pof tools have (I believe) been modified to let you do things light running lights.
A readme is in order, absolutely :)
-
I don't want to sound like an idiot, but pof tools? I heard about the possibility of a .pof constructer suite. Like a 3d modeling program, but nothing else. Will someone enlightne me?
-
no his new PCS crashes if it tries to load a model that it has added glow points to glow points
at the moment you can only make new models with glow points throught a lengthy procese of makeing thrusters renaming the chunk with a hex editor bla bla blah
and when the new POF editor comes out you'll probly have to redo everything
as for the beams
I am makeing improvements, it will soon be very flexable, to the point that you will be able to totaly disable the effect if you so desier (it will be disabled by default)
-
i dont know if my repair support ship got in there. if not, i can cvs that up once i get back.
thank god for free aol to be cancelled once i return!
-
I'll put together a zipfile (dunno why I didn't do this when I put the exe up there in the first place, I think by brain was fried) Sorry to force everyone to download an uncompressed EXE ;)
I will put in the zipfile:- the EXE (duh)
- a very brief README
- the ChangeLog
I should get it up there tonight, I'll post the URL here and on the warpcore page when done.
-
have a look at the changelog phreak, pretty sure that;s in there :)
-
Personally, I also would like to see the beams restored to what they were, or atleast have that be an option in tables somewhere, to disable the beam texture tiling and stretch it out...these look too pulsey and not beamy enough; if ya catch me drift ;)
-
Yeah, if you have been following the dev conversations, that is the goal.
This is the first release of many.
Don't beg for a precompiled exe and then tell me we should have waited 6 weeks for more features ;)
Sarcasm aside, this is NOT the end product, as penguin pointed out, there may NEVER be an end.
Now, the BEST way to deal with this, is to submit it as a bug in bugzilla ;)
-
Zipfile is up there, w/ a README that I slapped together and the CVS ChangeLog. It's about 1M.
http://fs2source.warpcore.org/releases/fs2_open-3.2.zip
The exe is still the same, so if you've already downloaded it, you don't need to get the zipfile, unless you can't get enough of my prose :rolleyes: ;)
-
Here's a list of changes that will likely impact the modder/player of FS2 (Coders have to look through the changelog, like me :p)
Bold text denotes a keyword that can be searched for to get more info on that change.
Added features, but have to be manually added w/o Fred2 binary:
-Toggleable ship trails
-Option to make it so the support ship repairs hull damage
To enable ship trails in a mission:
1) Open the mission file in a text editor
2) Add 32 to "+Flags:"
To have the support ship repair ships' hull:
1) Open the mission file in a text editor
2) Add 64 to "+Flags:"
Other added features:
-Basic support for ship glows
-Fighter beams
-Initial Beam tiling code added
-Geforce 4 fix (toggleable via the command line option -GF4FIX)
-Basic Linux support added
-CD checking disabled
-Wireframe target display added; toggleable with a mapped key
-Maximum subsystems upped from 128 to 200, maximum ship types to 198
-Maximum ships/ship limit bumped up to 400, maximum ship subojects to 2100
-Maximum shield icons is now 80
Bug fixes:
-Multiplayer success/failure music fixed
-Fixed secondary banks' inheriting of the reload time when a weapon runs out of ammo
-AI code revised for better primary weapon selection
-Subspace Missile code updated to work with Tag C
Command line options:
"-GF4FIX" Fixes a bug with Geforce 4 cards
"-almission (mission)" Autoloads a multiplayer mission, where (mission) is the mission filename without the filename extension
"-startgame" Goes to multiplayer mission select screen on startup
EDIT:I copied/pasted for the above Fred2 options, add 64 for support ship repairing a ship's hull; change underlined above :o
-
Originally posted by Inquisitor
Yeah, if you have been following the dev conversations, that is the goal.
This is the first release of many.
Don't beg for a precompiled exe and then tell me we should have waited 6 weeks for more features ;)
Sarcasm aside, this is NOT the end product, as penguin pointed out, there may NEVER be an end.
Now, the BEST way to deal with this, is to submit it as a bug in bugzilla ;)
Sorry your Highness, apparently the fact that I have a life (not to mention school) that doesn't revolve around the SCP has unfortunately resulted in my missing certain oh-so-important details. :rolleyes:
-
Originally posted by Inquisitor
Drannon: Yes :)
Hehe, ok i will put together a demo mission tmw. However i do need to know how to use the fighter beams. Someone have a table file set up with them or what?
-
So whats happening with the fred2 release? :)
-
why didnt u stick all the stuff in it from other ppl the enhanced explodions fighterbeams ETC ETC????
-
eh... FIghterbeams are enabled, they are just not set up in the Table files.
-
Originally posted by Ashrak
why didnt u stick all the stuff in it from other ppl the enhanced explodions fighterbeams ETC ETC????
This isn't an end user product really...this is for MOD teams to utilize and present in a format that the average player can then access.
Some upgrades like the GeForce 4 fix are definately beneficial to anyone with a GeForce 4...so thats not really mod exclusive and im sure when enhanced graphics come about, that will be part of it too. Right now, its about making the tools and opening the doors for others to walk through.
Kudos to the Source Team! We'll have you a proper website and some even more serious community support and publicity soon enough :D
-
Originally posted by Ashrak
why didnt u stick all the stuff in it from other ppl the enhanced explodions fighterbeams ETC ETC????
If you mean the Komet mods, (http://www.hard-light.net/forums/index.php/topic,8268.0.html) we can't use them because Komet never released them to us :(
-
Which doesn't mean I won't keep trying to get them :)
-
fighter beams..
make a beam weapon, type 3 (or whatever the targeting laser is)
if you want it to be a SSM targeting laser give it a tag type 3 and tag time will be the lock time
and remember to give it a SSM index
I beter give an example of the SSM stuff
tack this on to the end of the targeting laser to make it run like it used to or any other weapon to make it spawn an SSM
$Tag: 3 2.0
$SSM: 0
make damn sure you have a working SSM.tbl
$SSM:
+Weapon: Cyclops
+Count: 5
+WarpRadius: 200
+WarpTime: 5
+Radius: 1200
+Offset: 5
$SSM:
+Weapon: Harpoon
+Count: 10
+WarpRadius: 200
+WarpTime: 5
+Radius: 1200
+Offset: 5
#end
this is the SSM table I have right now
note I have two SSM entrees, this is what the
$SSM: 0
is for, this line here says this weapon will use the 0th (first) entry in the SSM table
if you wanted to use the harpoon one you'd put
$SSM: 1
you can have quite a few SSM types, but I can't remember what the actual number is
-
Thanks Bobboau.
I'll have the demo mission up tmw. Although i need somewhere to put it as i do not have a site currently.
The demo will demonstrate Fighter beams, SSM, ship trails, and support repair. Don't expect it to be complicated ;)
-
erm babau not everyone is a genius type that out to a really stupid person like me how do i get all beams working on a fighter?
-
I assume the beam weapon isnt meant to look like that?
-
Drannon: email it to me, I'll get it on the site.
-
what is there that you don't understand,
make a targeting laser type beam in you're table and put it on a fighter,
make a mission, treat it like you would any other normal primary weapon
-
Should the beam texture tiling work normally? At least they don't work with my modded beams. Do they have to be enabled somehow?
-
I think they need an extra flag or something added into the table entry. Look it up in the thread dedicated to this topic.
-
I think the version of the code they put in there tiled it by a hard coded value (it's relitive to the beam with)
try adding
+Tile Factor: 5
right after +Zadd: and see if it implodes or not
-
I'm having problems getting the Fighter beams to work. I copied the targeting laser code, and added damage to it, and changed the name, but touched nothing else, but Fs2 won't let me use it in the game. Fred2 let's me choose it as a weapon, but once in the mission, the weapon is unavailable.
Any suggestions?
-
did you add it to the alowed weapons for the ship your flying,
try useing the cheat codes just to play around with them
-
Ok, i feel stupid now. Thanks again Bobboau.
I will send in the zip file with the mission, and tables in a bit.
-
Dranon, in the events editor use the sexp (allow weapon) then choose the desired weapon... see if this will work:)
-
OOps jumped the topic a little (sorry about that).... Runs for the nearest exit:rolleyes:
-
I've got a question:
With the fighter beams, does it suffer the 'one beam firing point' problem?
-
Originally posted by Whitelight
OOps jumped the topic a little (sorry about that).... Runs for the nearest exit:rolleyes:
Didn't anyone ever tell you about the exits? :drevil:
-
Originally posted by Killfrenzy
I've got a question:
With the fighter beams, does it suffer the 'one beam firing point' problem?
that, is a silly question
:rolleyes:
no, it doesn't
-
Sorry guys, i've been having comp problems, and family problems, so the mission has been delayed. I have the outline of the mission put together, demonstrating all but the Support ship repair function, but i was wanting to turn it into a decent mission. I hope to have it done tmw.
-
Originally posted by Bobboau
that, is a silly question
:rolleyes:
no, it doesn't
I was just checking!
Now I can implement proper Beam Lasers!;7
-
Good work lads (http://www.plauder-smilies.de/happy/xyxthumbs.gif).
(http://www.plauder-smilies.de/flash.gif) / Fafner
-
Three things:
1) Fighter beam shield hits stop after a while (I made a mission with a Perseus vs a bunch of Maras, multiple waves, and after the first couple, the beams just went right through, even though the shields were up.
2) Is it possible to get rid of that pain in the ass message in the top right hand corner whenever you hit something?
3) How exactly DO you get rid of the 'beam tiling?'
:)
-
Originally posted by Killfrenzy
3) How exactly DO you get rid of the 'beam tiling?'
Good question.
-
I dont have acces to my primary machine so i cant' t verify what flag, but one way would be to have a flag already present in the weapons.tbl that is standard for all beam weapons and always has the same value and make the source read if this flag has another value other things are activated. if you use the binary system you could have infinant possibilities.
example
$someflag 1; meaning something is turned on
after source modification
$someflag 3;(option 1 + option 2) meaning that something is still turned on, but since we added 2 we turned on or off another option, like beam tileling.
so if $someflag is 3 or including the second bit in a binary system then beam tileling is off,
this should be easy, but i have no way of checking it since my machine is still being "reparied"
but if someone implement this then Beam tileling is something that should be turned on with $someflags second bit.
also; this will preserved all previous weapons as they where.
he, i hope you understand what i mean.
-
Shouldnt any change thats not a bug fix be optional and be off by default to maintain the original game?
-
I didn't think they'd keep that sheild hit debug mesage in
I'm working on the beam sheild hit bug, havn't made much progres though
the beam tileing code in this EXE is very primitive, there will be table flags to determine tileing and translation, if these optional tags are not present it will render them like it does in the origonal FS2
I am starting to think I should make a little masage that pops up at the begining of the game that reads this
-
Next release, it will be flaggable.
We could have simply left it out, but decided to put it in. The community wanted an exe, you got one.
Work in progress ;)
-
I have made parseing code for this stuff
// beam sections
while( optional_string("$Section:") ){
beam_weapon_section_info i;
char tex_name[255] = "";
// section width
required_string("+Width:");
stuff_float(&i.width);
// texture
required_string("+Texture:");
stuff_string(tex_name, F_NAME, NULL);
i.texture = -1;
if(!Fred_running){
i.texture = bm_load(tex_name);
if(i.texture >= 0){
bm_lock(i.texture, 16, BMP_TEX_OTHER);
bm_unlock(i.texture);
}
}
// rgba inner
required_string("+RGBA Inner:");
stuff_byte(&i.rgba_inner[0]);
stuff_byte(&i.rgba_inner[1]);
stuff_byte(&i.rgba_inner[2]);
stuff_byte(&i.rgba_inner[3]);
// rgba outer
required_string("+RGBA Outer:");
stuff_byte(&i.rgba_outer[0]);
stuff_byte(&i.rgba_outer[1]);
stuff_byte(&i.rgba_outer[2]);
stuff_byte(&i.rgba_outer[3]);
// flicker
required_string("+Flicker:");
stuff_float(&i.flicker);
// zadd
required_string("+Zadd:");
stuff_float(&i.z_add);
[b]if( optional_string("+Tile Factor:")){ //beam texture tileing factor -Bobboau
stuff_float(&i.tile_factor);
}else{
i.tile_factor = -1.0f;
}
if( optional_string("+Translation:")){ //beam texture moveing stuff -Bobboau
stuff_float(&i.tile_factor);
}else{
i.translation = 0.0f;
}[/b]
// maybe copy it
if(wip->b_info.beam_num_sections < MAX_BEAM_SECTIONS - 1){
wip->b_info.sections[wip->b_info.beam_num_sections++] = i;
}
}
parse_weapon
weapons.cpp
line ~ 1230
for some odd reason though it seems to damage the code that displays the weapon names in the hud
also I have been working on the tileing code
void beam_render(beam_weapon_info *bwi, vector *start, vector *shot, float shrink)
{
int idx, s_idx;
vertex h1[4]; // halves of a beam section
vertex *verts[4] = { &h1[0], &h1[1], &h1[2], &h1[3] };
vector fvec, top1, bottom1, top2, bottom2;
float scale;
float u_scale; // beam tileing -Bobboau
float length; // beam tileing -Bobboau
float U_offset; // beam texture offset -Bobboau
// bogus weapon info index
if(bwi == NULL){
return;
}
// if the beam start and endpoints are the same
if(vm_vec_same(start, shot)){
return;
}
// get beam direction
vm_vec_sub(&fvec, shot, start);
vm_vec_normalize_quick(&fvec);
// turn off backface culling
gr_set_cull(0);
// draw all sections
for(s_idx=0; s_idxbeam_num_sections; s_idx++){
// calculate the beam points
scale = frand_range(1.0f - bwi->sections[s_idx].flicker, 1.0f + bwi->sections[s_idx].flicker);
beam_calc_facing_pts(&top1, &bottom1, &fvec, start, bwi->sections[s_idx].width * scale * shrink, bwi->sections[s_idx].z_add);
beam_calc_facing_pts(&top2, &bottom2, &fvec, shot, bwi->sections[s_idx].width * scale * scale * shrink, bwi->sections[s_idx].z_add);
R_VERTICES(); // rotate and project the vertices
P_VERTICES();
STUFF_VERTICES(); // stuff the beam with creamy goodness (texture coords)
length = vm_vec_dist(start, shot); // beam tileing -Bobboau
if (bwi->sections[s_idx].tile_factor){
u_scale = length / (bwi->sections[s_idx].width /2) / bwi->sections[s_idx].tile_factor; // beam tileing, might make a tileing factor in beam index later -Bobboau
}else{
u_scale = bwi->sections[s_idx].tile_factor * -1;
}
verts[1]->u = ((verts[1]->u * u_scale) ; // beam tileing -Bobboau
verts[2]->u = ((verts[2]->u * u_scale) ; // beam tileing -Bobboau
// set the right texture with additive alpha, and draw the poly
gr_set_bitmap(bwi->sections[s_idx].texture, GR_ALPHABLEND_FILTER, GR_BITBLT_MODE_NORMAL, 0.9999f);
g3_draw_poly( 4, verts, TMAP_FLAG_TEXTURED | TMAP_FLAG_TILED | TMAP_FLAG_CORRECT); // added TMAP_FLAG_TILED flag for beam texture tileing -Bobboau
}
// turn backface culling back on
gr_set_cull(1);
}
that code will work, but I've been unable to get the translation to work,
will someone more knowlegable tell me why this code causes a crash
U_offset = 0.0f;
verts[1]->u = ((verts[1]->u * u_scale) + U_offset); // beam tileing -Bobboau
verts[2]->u = ((verts[2]->u * u_scale) + U_offset); // beam tileing -Bobboau
verts[3]->u = (verts[3]->u + U_offset);
verts[3]->u = (verts[4]->u + U_offset);
-
So if you can iron out the glitches the next release will have:
- Optional tiling of beams
- The removal of that damned message in the corner
- Consistent shield hits.
:)
EDIT:
Gripe No. 2: - You don't get kills for beam weapons.:(
-
Sorry Inq. I'm a bit confused over how the bug reporting setup works so I'll post it here.
I can't start any missions, from the main hall or the mission simulator. From the main hall it crashes back to the desktop, from the simulator it hangs before listing the available missions.
Also I have got block filled text strings on occasion.
K6-2 300MHz
3DFX Voodoo 3 2000
256megs RAM.
You need the generated error log?
Komet's build of the exe works OK with no errors.
-
Originally posted by Maeglamor
I can't start any missions, from the main hall or the mission simulator. From the main hall it crashes back to the desktop, from the simulator it hangs before listing the available missions.
Also I have got block filled text strings on occasion.
K6-2 300MHz
3DFX Voodoo 3 2000
256megs RAM.
You need the generated error log?
Komet's build of the exe works OK with no errors.
Hmm, this is the same bug sesqui reported. Apparently not a memory issue, since you seem to have a fair amount...
OK, we'll have to investigate this one in more detail...
Maeg, how much memory is on your Voodoo?
-
No problem, Maeg, it's a LITTLE obtuse a system, but it works well once you get over that first hurdleof signing up :)
we can add this detail to the current bug.
-
I notice Maeglamor and I are both running K6-2's, though mine is faster than his (500 Mhz).
-
Originally posted by Inquisitor
No problem, Maeg, it's a LITTLE obtuse a system, but it works well once you get over that first hurdleof signing up :)
we can add this detail to the current bug.
Hehe, it ran me in circles twice before I figured out that I couldn't access it. The link on bugzilla said something like 'to report FS2 source related bugs click here'; that link brought me to your page and on your page it said 'to report bugs click here'. As you know this brings me back to the bugzilla page. :lol:
I wasn't sure if I was trying to report a bug for mozilla or FSsource :) A guide to what info should be entered would also be good, perhaps on a popup window on the bug reporting page?
The voodoo card has 16 megs of ram and it is restricted to handling 256*256 sized tex. maps. The system is pretty good at handiling the game with only a few slowdowns at 1024*768.
I'd really like an .exe that doesn't have the CD check, my drive is acting up and it increasingly won't recognise disks even after a thorough cleaning.
-
Originally posted by Maeglamor
Sorry Inq. I'm a bit confused over how the bug reporting setup works so I'll post it here.
I can't start any missions, from the main hall or the mission simulator. From the main hall it crashes back to the desktop, from the simulator it hangs before listing the available missions.
Also I have got block filled text strings on occasion.
K6-2 300MHz
3DFX Voodoo 3 2000
256megs RAM.
You need the generated error log?
Komet's build of the exe works OK with no errors.
I've got the same error here...
AMD K7 1200
Nvidia Geforce 2
128mb RAM
The komet mod works fine on my PC too...
-
Originally posted by Raven2001
I've got the same error here...
AMD K7 1200
Nvidia Geforce 2
128mb RAM
The komet mod works fine on my PC too...
Hmmm, I wonder if '3Dnow!' has any part to play in this. It's the only thing I can think of anyway *shrugs*.
-
Originally posted by Maeglamor
Hmmm, I wonder if '3Dnow!' has any part to play in this. It's the only thing I can think of anyway *shrugs*.
The k6-III has 3dNow! technology, and this is what i'm running and fs2 open runs fine on my system :)
-
Jellyfish soup
-
The funny thing is, the muli-point firing means I have to adjust the Morrigan now because it's only supposed to fire beams from one point....
-
First successful test using TBP table files. Ran fairly well...although with a noticeable loss of FPS in a few cases. Otherwise very smooth. I haven't yet tried the fighter beam system however. Thats next.
-
I screwed up (oh well)
Got the new comp a little while ago
P4 (1.8)
512DDR Mem
70 GB HD (Primary)
Nvidia 32MB
anyway, I had both the Komet mod and the open-source up date and ran them. The sdf-1's gun got all screwy and looked like a ziggy wave so I deleted both of them. normally it would be no big deal but considering it is the biggest beam in the game and you can't help noticing it and I wanted it back to the original. However cause I impulsively removed them both I don't know if it was one the other or both causing the aberration, and am not willing to try either again. Just thought I'd let you know...
-
I tried the fighter beam system and I experienced some difficulties.
1) I can't get the beams to pulsate like they do in Babylon 5 (Nial beams). Is there any way to get them to end or start again?
2) No collision detection on fighters and bombers it seems (or missiles for that matter, mmm....Warlock VS Sharlin!).
3) Infinite range. How can I temper that?
-
Yeah, the "Ziggy" beams are a feature.
You'll be able to turn them off in the next release.
-
Er, I just realized that the increased table sizes that DTP put in are still there... I thought I rolled them back. Guess I forgot to commit my changes :o
In any event, I strongly suspect that's what's causing the crash-on-mission-load bug reported by several folks.
Anyhow, I am going to build a DEBUG version of this fs2_open 3.2 and post it when available. I will probably generate two executables -- one with the increased table sizes, one without. The debug versions have increased logging, so any errors will have a little more info.
The next release (3.3) will have dynamic table sizes, so we can try to track down and squash this bug once and for all...
-
I think I'll make some tag for cycling firing points, that should be usefull for you
-
And try to fix the shields and that damned message!
Oh yeah, and drop the pulsing!:D
-
Ok, I dunno if this has been said before. I can't sit through 4 pages of complaints, but aside from the normal beam stuff...
1) I like the sound of rotating firing points
2) When I use a fighter beam, thers no explosion on the enemy vessel's destruction
) I never get credit for the kill...
-
Originally posted by Raa Tor'h
Ok, I dunno if this has been said before. I can't sit through 4 pages of complaints, but aside from the normal beam stuff...
1) I like the sound of rotating firing points
2) When I use a fighter beam, thers no explosion on the enemy vessel's destruction
) I never get credit for the kill...
i'm not going to bother to read all the 4 or 5 pages of this topic,
but how can you use a fighter beam? did you hack the weapons and ships .TBLs and make it available to use?
-
did you hack the weapons and ships .TBLs and make it available to use?
Yup...thats how its done. Thats the easy part...the coding to make it work was no doubt harder :D
-
ooh... things have been moving along since the last time I checked. Anyways, so far so good, no crashes for me yet. :)
-
I heard about some wireframe targeting thing. How does that work? Every time I go to configure my key controls, and then go the miscellaneus, the game crashes.
-
Originally posted by Hades
I heard about some wireframe targeting thing. How does that work? Every time I go to configure my key controls, and then go the miscellaneus, the game crashes.
Either fill in a bug report (sorry havent got the link handy) or give us your specs.
-
Bug link in the first post of this very thread :)
-
Wireframe targeting is CTRL-ALT-Q. You can't change it, yet.
-
[edit]
should have read the previous replies. Ignore
-
Has anyone spoken to Komet about integrating his visual enhancements into the project?
Sid.
-
By email, VWBB and his forum, no response.
-
Originally posted by SadisticSid
Has anyone spoken to Komet about integrating his visual enhancements into the project?
Sid.
what kind of enhancements?
-
Originally posted by RandomTiger
what kind of enhancements?
Did some fancy graphics enhancements for the explosions and stuff - most of it was new "effects" but it was pretty impressive. His own little "forum" says he's away on another project or something like that.
-
A few people have (Inq left a message on Komet's BB) I emailed him a while ago but have recieved no response. I guess someone's going to have to redo it because Komet is either unable or unwilling to let us have the code. :blah:
-
what were the changes he made?
-
Originally posted by Bobboau
what were the changes he made?
Check out the original thread, there's screenies on it too :)
Thread (dynamic4.gamespy.com/~freespace/forums/showthread.php?threadid=8268&highlight=Komet)
-
I have a question...
Is it possible to change the code so that when your fighter reaches critical, it gets more unmaneuverable, the reactor's output is cut, and shields/afterburners can fail?
It would make the game much harder, and maybe more interesting, too.
As of now, I can't tell the difference between my fighter at 99% and at 9%...
-
Originally posted by Raa Tor'h
I have a question...
Is it possible to change the code so that when your fighter reaches critical, it gets more unmaneuverable, the reactor's output is cut, and shields/afterburners can fail?
It would make the game much harder, and maybe more interesting, too.
As of now, I can't tell the difference between my fighter at 99% and at 9%...
You really are a glutton for punishment aren't you? :p
-
Originally posted by Raa Tor'h
I have a question...
Is it possible to change the code so that when your fighter reaches critical, it gets more unmaneuverable, the reactor's output is cut, and shields/afterburners can fail?
It would make the game much harder, and maybe more interesting, too.
As of now, I can't tell the difference between my fighter at 99% and at 9%...
Lucasarts did something similar in Xwing Vs. TIE fighter - when your ship moved slowly it was less maneouverable.
You could have loads of goofy things happenening with damage effects ;)
-
I'm all for enhancing features, but priority should be given to adding things that people have wanted to do for a while, rather than altering the gameplay dynamic. It would be an interesting idea though. :)
Sid.
-
Hmm...this could be attached to the "Show Damage" TBL tag, too :nod:
-
hey any luck on the turret problem involving turrets only being able to be in one position:up that is.
-
may I suggest a little "fix" regarding the in-game video (mve?)?
I reinstalled when I heard of this project and replayed the main-campaign from the beginning using the FS2_OPEN, hence I can't see the video's in the techroom (using the original freespace2.exe of course) because they're not added there, only the intro is there.
what I'm trying to say is it would be nice if the entries would be at least added when playing the main campaign with the fs2_open so that you may view them with the original if you so desire...
By the way, what exactly is the reason interplay won't allow (?) the use of the mve player or a "hacked" in mve player?
I know I have a Fallout (another interplay game) mve-hacked player.
Also considering there are much more compressed formats now, I don't really see why one couldn't convince iply to reconsider :)
-
Originally posted by wamingo
may I suggest a little "fix" regarding the in-game video (mve?)?
I reinstalled when I heard of this project and replayed the main-campaign from the beginning using the FS2_OPEN, hence I can't see the video's in the techroom (using the original freespace2.exe of course) because they're not added there, only the intro is there.
what I'm trying to say is it would be nice if the entries would be at least added when playing the main campaign with the fs2_open so that you may view them with the original if you so desire...
By the way, what exactly is the reason interplay won't allow (?) the use of the mve player or a "hacked" in mve player?
I know I have a Fallout (another interplay game) mve-hacked player.
Also considering there are much more compressed formats now, I don't really see why one couldn't convince iply to reconsider :)
The MVE format is still thier baby, they still use it in new games. They just want to keep something thats theirs - you can't blame them. Besides, recent developments in the project, we now have cross-format support. If you've got the codec in windows, you can play it in fs2. (Correct me if I'm wrong RT)
-
I suppose but freespace2 is also theirs and they released the source code.
-
Originally posted by wamingo
I suppose but freespace2 is also theirs and they released the source code.
But the main source code isn't used by any of thier other games.
:) I know it'd be nice to get access to the old movies but this way is just as good - we can have good movies for people's mods and leave room for greater expansion.
-
Whats the current progress on 3.3?
-
Originally posted by wamingo
I suppose but freespace2 is also theirs and they released the source code.
This is an age old debate. Do a search and you'll see what I mean. The mve playing code belongs to interplay and they dont want it compromised because other games make use of it.
If we include code that plays it inside f2s_open we are inviting legal troubles. Even the suggestion of legal action would be more trouble than its worth to the providers of the hosting space and these boards.
-
Yeah, let's just leave MVE alone. MVE coding usually gets people into trouble. We've already lost two major boards (VBB, and in case you haven't heard, F2S in deep **** cause of a scandal)VWatch is practicaly inactive, so let's just keep ourselves out of trouble.
-
what did F2S do?
-
F2S didn't do anything, Hunter got scammed by some national criminal. In other words, they will probably never be back online.
Check it out in this thread.
http://www.hard-light.net/forums/index.php/topic,10076.0.html
-
Remember the bug reported by myself and also some others in this thread when fs2_open 3.2 came out? Well, it turns out is was simply a problem with the pilot (for me, at least).
When beta testing Bobboau's latest exe, it turned out that my old pilot that I had carried over was causing crashes, so I had to make a new one. I thought it might be a good idea to check if this would help with fs2_open, and lo and behold, it did.
I just thought the SCP people would want to know that, and sleep easier as a result. :)
-
Yes indeed. I will log it as closed unless penguin or phreak tell me otherwise :)
Thanks :)
-
Could it be that you never patched FS2 to 1.2 (or whatever it is).
And pilots arent compatable between the two versions, that would explain a lot.
-
Originally posted by RandomTiger
Could it be that you never patched FS2 to 1.2 (or whatever it is).
And pilots arent compatable between the two versions, that would explain a lot.
Eh? Pilots always worked between the two versions for me. Besides, I reinstalled fs2 (w/o update), created pilots, then used the fs2_open release and everything ran fine. :nod:
-
Bobbaou's exe was a debug build, and it produced an error which, when interpreted for me by bob, indicated that the problem was something to do with the pilot having been used to play a mod before. Because of that, some information stored in it was not compatible with something in his exe. This was the same pilot file I had tried with fs2_open, with similar crashing results.
It is the mod factor that created the problems. If a pilot is a mod-virgin, as it were, it can probably switch between builds without any difficulty.
-
Cool, as long as we know whats going on
-
Originally posted by Sesquipedalian
....mod-virgin...
Ooh, this could make a good catchphrase.
-
Heh, just out of curiosity, might I add a few requests/ideas in this thread? They're not stuff that everybody might find beneficial, but for those of us with older cards AND dualies... You might see where I'm going with this. I wish I could program...
I have other ideas, but I'll wait...
-
You might want to start a new thread for that.
-
Hmm, I probably should.
*smacks head*
Shows that I shouldn't post when I'm asleep:-P
-
Dont forget to actually make the post :)
I want to read it
-
bump till I get it on the page.
-
Sorry, I had a question but found the proper thread for posting it in...
-
I dislike BugZilla because of its [slowness] on my computer so I'll post bug reports here.
Bug Report(s)
==========
1. The music and briefing voice play incorrectly (repeates the same part of itself] when the CD in not in the drive.
2. When exceeding the original "ships.tbl" limit, a mission would take a lot of time to load. The status bar of the mission would reach 100% but the mission would load for another five minutes before it goes into briefing.
3. FRED 2 doesn't quite take oversized "ships.tbl" very well. Since one of the greatest improvements of FS2_Open_3.2 is that it allows bigger "ships.tbl" size and ships limit, FRED 2 shouldn't have this limitation.
General Suggestions
===============
1. The beam cannon's "jaggedness" should be adjustable by the MODder in "weapons.tbl" as a flag. If not, then please shorten the amount of bitmap overlays so that the beam would look more "real". [Make it similar to the Homeworld beams.]
2. Make a separate flag for engine trails that will be enabled "everywhere". [The Apocalypse Project people would really like that!]
3. Blinking lights
4. A color used in a texture map would be invisible.
5. POF support for background images.
6. Moving parts of given degrees (or radians) on submodel axis.
-
Have you even read this thread? At all? All this stuff has been mentioned in this forum. Except for the .pof for backgrounds, which, why would you want to do that?
That is why the SCP uses Bugzilla, so they don't get the same stuff over and over again.
-
It's a web app, there's no reason it should be slow on your computer. That's like saying HLP is slow because of your computer.
Please use it, otherwise you make us do extra work, and your bug might not get closed :(