VWBB Pages (14): « First ... « 2 3 4 5 [6] 7 8 9 10 » ... Last »
Show all 265 posts from this thread on one page

VWBB (http://volitionwatch.papageorgefamily/vwbb/index.php)
- FreeSpace 1/2 MODs Discussion (http://volitionwatch.papageorgefamily/vwbb/forumdisplay.php?forumid=40)
-- Suggested improvemets w/Source code (http://volitionwatch.papageorgefamily/vwbb/showthread.php?threadid=6034)


Posted by karajorma on 04-26-2002 12:20 AM:

quote:
Originally posted by Alikchi


You should set it as an option in FRED2 as to who shoots what.



The reason I suggested colours is that it's simpler that way. You set it in FRED which colours attack which. That's far simpler than defining the enemies for each individual ship.

__________________
Questions about FS3? Questions about Fred? Questions about missions? Questions about adding new ships to your games?

[URL=http://homepage.ntlworld.com/karajorma/freespace/intro.html]Karajorma's Freespace FAQ [/URL] (now with added GE goodness)

Supreme Overlord of The Mercury Affair Campaign.

FREDder, Modder, Story design and general busybody for [URL=http://www.3dap.com/hlp/hosted/mindgames/Background.html] Mind Games[/URL]


Posted by karajorma on 04-26-2002 12:20 AM:

quote:
Originally posted by Alikchi


You should set it as an option in FRED2 as to who shoots what.



The reason I suggested colours is that it's simpler that way. You set it in FRED which colours attack which. That's far simpler than defining the enemies for each individual ship.

__________________
Questions about FS3? Questions about Fred? Questions about missions? Questions about adding new ships to your games?

[URL=http://homepage.ntlworld.com/karajorma/freespace/intro.html]Karajorma's Freespace FAQ [/URL] (now with added GE goodness)

Supreme Overlord of The Mercury Affair Campaign.

FREDder, Modder, Story design and general busybody for [URL=http://www.3dap.com/hlp/hosted/mindgames/Background.html] Mind Games[/URL]


Posted by Ace on 04-26-2002 01:32 AM:

quote:
Originally posted by karajorma

That's far simpler than defining the enemies for each individual ship.



No, he meant that you should be able to select for a color how they react to other colors. (i.e. does green attack all other colors, ignore some, etc. etc.) This is more flexible then hard-coding "magenta hates all" it allows people to customize each "color faction."

__________________
Ace
There are old pilots, and there are bold pilots; but no old bold pilots.
-Chuck Yeager


Posted by Ace on 04-26-2002 01:32 AM:

quote:
Originally posted by karajorma

That's far simpler than defining the enemies for each individual ship.



No, he meant that you should be able to select for a color how they react to other colors. (i.e. does green attack all other colors, ignore some, etc. etc.) This is more flexible then hard-coding "magenta hates all" it allows people to customize each "color faction."

__________________
Ace
There are old pilots, and there are bold pilots; but no old bold pilots.
-Chuck Yeager


Posted by DTP on 04-26-2002 01:46 AM:

quote:
Originally posted by YodaSean
All I want is support for bigger resolutions! Like 1280*1024. That shouldn't be too hard too do...



hard no, time consuming yes.

all of HUD elements and ani`s would have to be rescaled to that resolution, We dont have the original MAX scene files used to render the animations in the first place, & rescaled animations would at the very least look very ugly.

and so far i can tell, that you would have to redesign 60-70% of the code to understand that resolution.

__________________
Think Big
Invade Space
---------
Staff modeller on FS1 port
http://www.3dap.com/hlp/hosted/fsport/


Posted by DTP on 04-26-2002 01:46 AM:

quote:
Originally posted by YodaSean
All I want is support for bigger resolutions! Like 1280*1024. That shouldn't be too hard too do...



hard no, time consuming yes.

all of HUD elements and ani`s would have to be rescaled to that resolution, We dont have the original MAX scene files used to render the animations in the first place, & rescaled animations would at the very least look very ugly.

and so far i can tell, that you would have to redesign 60-70% of the code to understand that resolution.

__________________
Think Big
Invade Space
---------
Staff modeller on FS1 port
http://www.3dap.com/hlp/hosted/fsport/


Posted by ZylonBane on 04-26-2002 01:55 AM:

quote:
Originally posted by Orange
In-game cutscenes as in ...
Interesting. I don't know how complex this would be from the back end, but from a FRED2 perspective it should be dead simple. I think you could get away with as few as two new SEXPs...

cutscene-attach-camera
-- ship or waypoint (if player ship, resume player control)

cutscene-point-camera
-- target ship or waypoint (if same as attached, point straight ahead)
-- panning transition speed
-- track target? (optional)

This reminds me of a minor rendering bug in FS2. When you switch viewpoints, the "space debris" sprites render in their old location for a frame. So if you switch to a ship that's looking at your previous viewpoint, you'll see a brief flash of it.

__________________
ZylonBane's opinions do not reflect those of the management.
That's [url=http://home.att.net/~clay.h/fs2/violition.htm]VOLITION[/url]!


Posted by ZylonBane on 04-26-2002 01:55 AM:

quote:
Originally posted by Orange
In-game cutscenes as in ...
Interesting. I don't know how complex this would be from the back end, but from a FRED2 perspective it should be dead simple. I think you could get away with as few as two new SEXPs...

cutscene-attach-camera
-- ship or waypoint (if player ship, resume player control)

cutscene-point-camera
-- target ship or waypoint (if same as attached, point straight ahead)
-- panning transition speed
-- track target? (optional)

This reminds me of a minor rendering bug in FS2. When you switch viewpoints, the "space debris" sprites render in their old location for a frame. So if you switch to a ship that's looking at your previous viewpoint, you'll see a brief flash of it.

__________________
ZylonBane's opinions do not reflect those of the management.
That's [url=http://home.att.net/~clay.h/fs2/violition.htm]VOLITION[/url]!


Posted by ltnarol on 04-26-2002 02:46 AM:

support for higher resolution maps would have to be done through hacking the 3d accelerator wouldnt it? Is there a way around this so it can be hardcoded into the game engine itself?

__________________
[url="http://www.3dap.com/hlp/hosted/the158th/"]158th Banshee Squadron[/url]


Posted by Ace on 04-26-2002 03:23 AM:

quote:
Originally posted by ZylonBane
Interesting. I don't know how complex this would be from the back end, but from a FRED2 perspective it should be dead simple. I think you could get away with as few as two new SEXPs...

cutscene-attach-camera
-- ship or waypoint (if player ship, resume player control)

cutscene-point-camera
-- target ship or waypoint (if same as attached, point straight ahead)
-- panning transition speed
-- track target? (optional)




Even simpler then that Zylon, for cutscenes simply have a set of cutscene waypoints.

Now in the object data in FRED, you have position, rotation, etc. the camera faces straight forward on the waypoint.

Just place these waypoints where you want them, and select what their rotation is for camera angles.

Each waypoint also has a "time" option in it's FRED entry, this is the time it takes the camera to move and rotate from the last waypoint to the current one in milliseconds (ms) (this holds true to the briefing screens which are also in ms camera switches)

Panning can be done with two waypoints in the same position, but with different rotation angles.

Ontop of this, you have sexpts to switch between camera waypoints, in these sexpts you can pick if you want the camera to fade, just cut to the next waypoint, etc.

Overall, the waypoint code for all of this is already there, it should save time from doing more complicated and convulted in-game cutscene ideas.

__________________
Ace
There are old pilots, and there are bold pilots; but no old bold pilots.
-Chuck Yeager


Posted by Ace on 04-26-2002 03:23 AM:

quote:
Originally posted by ZylonBane
Interesting. I don't know how complex this would be from the back end, but from a FRED2 perspective it should be dead simple. I think you could get away with as few as two new SEXPs...

cutscene-attach-camera
-- ship or waypoint (if player ship, resume player control)

cutscene-point-camera
-- target ship or waypoint (if same as attached, point straight ahead)
-- panning transition speed
-- track target? (optional)




Even simpler then that Zylon, for cutscenes simply have a set of cutscene waypoints.

Now in the object data in FRED, you have position, rotation, etc. the camera faces straight forward on the waypoint.

Just place these waypoints where you want them, and select what their rotation is for camera angles.

Each waypoint also has a "time" option in it's FRED entry, this is the time it takes the camera to move and rotate from the last waypoint to the current one in milliseconds (ms) (this holds true to the briefing screens which are also in ms camera switches)

Panning can be done with two waypoints in the same position, but with different rotation angles.

Ontop of this, you have sexpts to switch between camera waypoints, in these sexpts you can pick if you want the camera to fade, just cut to the next waypoint, etc.

Overall, the waypoint code for all of this is already there, it should save time from doing more complicated and convulted in-game cutscene ideas.

__________________
Ace
There are old pilots, and there are bold pilots; but no old bold pilots.
-Chuck Yeager


Posted by ZylonBane on 04-26-2002 03:39 AM:

Big problem with "cutscene waypoints"-- they can't move.

FS already supports jumping the rendering POV all over the mission area with user key commands, so why not just leverage that existing ability with SEXPs? By attaching the camera to a moving object, you could easily use existing SEXPs to trigger events as the camera approaches. You could have the camera follow a ship, break off to look at something else, even warp out.

__________________
ZylonBane's opinions do not reflect those of the management.
That's [url=http://home.att.net/~clay.h/fs2/violition.htm]VOLITION[/url]!


Posted by ZylonBane on 04-26-2002 03:39 AM:

Big problem with "cutscene waypoints"-- they can't move.

FS already supports jumping the rendering POV all over the mission area with user key commands, so why not just leverage that existing ability with SEXPs? By attaching the camera to a moving object, you could easily use existing SEXPs to trigger events as the camera approaches. You could have the camera follow a ship, break off to look at something else, even warp out.

__________________
ZylonBane's opinions do not reflect those of the management.
That's [url=http://home.att.net/~clay.h/fs2/violition.htm]VOLITION[/url]!


Posted by ltnarol on 04-26-2002 03:41 AM:

suggestion:

Being able to enter and leave subspace without ending a mission, same for nebulas

__________________
[url="http://www.3dap.com/hlp/hosted/the158th/"]158th Banshee Squadron[/url]


Posted by ltnarol on 04-26-2002 03:41 AM:

suggestion:

Being able to enter and leave subspace without ending a mission, same for nebulas

__________________
[url="http://www.3dap.com/hlp/hosted/the158th/"]158th Banshee Squadron[/url]


Posted by Bobboau on 04-26-2002 04:15 AM:

I'm sure there must be a way to preload and procese two or more mission files to have the second one start imediatly

__________________
Bobboau, bringing you products that work ......... In theory


Posted by Bobboau on 04-26-2002 04:15 AM:

I'm sure there must be a way to preload and procese two or more mission files to have the second one start imediatly

__________________
Bobboau, bringing you products that work ......... In theory


Posted by ltnarol on 04-26-2002 04:40 AM:

couldnt we find a way to do the transitions instead? it would look rather silly if a ship suddenly goes from inside nebula to somewhere far away from it. I was thinking more along the lines of making nebulas more like how they made asteriod fields, so they have a specific area, and you can enter and leave the nebula that way. Same kind of thing for subspace, only it would only be enterable and leavable at nodes.

__________________
[url="http://www.3dap.com/hlp/hosted/the158th/"]158th Banshee Squadron[/url]


Posted by Bobboau on 04-26-2002 04:42 AM:

well, yes, there would be a transition sequence of course

__________________
Bobboau, bringing you products that work ......... In theory


Posted by ZylonBane on 04-26-2002 05:26 AM:

quote:
Originally posted by Bobboau
I'm sure there must be a way to preload and procese two or more mission files to have the second one start imediatly
You'd likely have to touch a lot of routines to do this. Besides initialization, you've got campaign code, red alerts, persistent variables, and, ummm... other stuff.

__________________
ZylonBane's opinions do not reflect those of the management.
That's [url=http://home.att.net/~clay.h/fs2/violition.htm]VOLITION[/url]!


All times are EST. The time now is 12:27 PM. Pages (14): « First ... « 2 3 4 5 [6] 7 8 9 10 » ... Last »
Show all 265 posts from this thread on one page

Powered by: vBulletin Version 2.2.6
Copyright © Jelsoft Enterprises Limited 2000, 2001.