Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Lightspeed on March 20, 2004, 07:42:49 pm

Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 20, 2004, 07:42:49 pm
Okay, first the good news:

I have completed the fourth set of my nebula backgrounds.

Now... the bad ones.

When putting everything together I ran into several things that shouldn't be happening:


(1) Although I had been told the limit in stars.tbl had been bumped to ~150, I found out that FRED2open will still only show as much background images as were permitted in standard FS2.
 


"Well," I thought "they prolly only forgot to compile that into FRED, i'll just use NotePad to do the job..."


(2) Now, I had re-included the standard FS2 backgrounds. I started the game only to find out that if any background image that will not show up in FRED is used, the game will crash after loading the mission.


Now, I thought the bumping just wouldnt have been done, but I found out later, that the game will display any of the first background images (the ones that still show up in FRED) okay, and only crashes on those that come after the stars.tbl limit (which is still the same as in FSretail). Older builds simply do not show up ANY background images, if the stars.tbl limit is exceeded. So - the bumping has been (at least partially) done, but doesn't work.


(3) So, I tossed out all my other sets to at least test it in-game once. I then discovered that the lighting in the new build (with diffuse in again) is indeed odd, as the actual background nebula  images are rendered too bright and look a bit odd - as well as the ships (see my post in the recent builds forum). I think the problem is that 'diffuse light' and ambient light add together, and so the general light factor is way too strong. The solution probably would be to get rid of diffuse lighting again, and have ambient as the replacement (as it will look better with in-game effects (sun lighting, beam hits, etc) ).

 

(4) Then, I wanted to test with the new env_2 build, to get some nice screenies even *with* the odd brightness, but when I hit the run button on the launcher, FS2open immediately dumped me back to desktop with an illegal operation. (before even opening it's screen)


So ~ as a summary of the day:

- The limit in stars.tbl needs fixing, so we need a new version of FRED as well as FS2 that will handle the new limit okay.

- Something has to be done with the lighting

And to encourage you to fix things:

(http://www.penguinbomb.com/lightspeed/orionne.jpg)
(I know it's a bad screenie, but I was too frustrated to come up with anything better)
Title: BUGS: It is a bad day for me & FS2open
Post by: Sticks on March 20, 2004, 07:51:24 pm
This out of control limits bumping is what is making FSOpen go crazy with mem usage in the first place. And when did anyone disable diffuse lighting?
Title: BUGS: It is a bad day for me & FS2open
Post by: Bobboau on March 20, 2004, 07:55:18 pm
there was a bug, it got killed acedentaly when I fixed the way shockwaves are rendered
Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 20, 2004, 07:59:49 pm
Quote
Originally posted by Sticks
This out of control limits bumping is what is making FSOpen go crazy with mem usage in the first place.


It shouldnt be. Stars.tbl is only holding name references (almost no memory needed) - And FS2 loads only the nebulae that are used anyway (I hope).

So from this point of view, there shouldn't be any visible difference in mem usage.

On things that do take up loads of memory (weapons / ships tables, because they store loads of values and stuff) I 100% agree with you.
Title: BUGS: It is a bad day for me & FS2open
Post by: Bobboau on March 21, 2004, 02:33:38 am
well it isn't the valuses that (generaly) cause huge memory useage, it's textures and the like (each background immage has a texture assosiated with it)
Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 21, 2004, 05:27:50 am
exactly. But where you had ~14 different background textures with FSretail, you still have 14 different background textures now.

The only thing is, the way of using those 14 backgrounds has changes drastically :)

(Using the same 14 for all missions --> Different Sets à 14 backgrounds)
Title: BUGS: It is a bad day for me & FS2open
Post by: Setekh on March 22, 2004, 04:47:54 am
Sweet background, LS. :)
Title: BUGS: It is a bad day for me & FS2open
Post by: IPAndrews on March 22, 2004, 07:03:49 am
Quote
Originally posted by Sticks
This out of control limits bumping is what is making FSOpen go crazy with mem usage in the first place. And when did anyone disable diffuse lighting?


Someone should have introduced Volition to the miracle of dynamic memory allocation.
Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 22, 2004, 07:15:41 am
Quote
Originally posted by Setekh
Sweet background, LS. :)


I can release the very second the bugs are fixed :)
Title: BUGS: It is a bad day for me & FS2open
Post by: Inquisitor on March 22, 2004, 09:22:28 am
Bob are you on this one?
Title: BUGS: It is a bad day for me & FS2open
Post by: Bobboau on March 22, 2004, 11:43:40 am
bumping the background limit?
sure I guess
Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 22, 2004, 11:44:35 am
How about another command line thingy to turn diffuse off? :)
Title: BUGS: It is a bad day for me & FS2open
Post by: Inquisitor on March 22, 2004, 11:54:06 am
Wasn't sure if you were or not, didn't rememebr covering it in IRC, is it in Mantis?
Title: BUGS: It is a bad day for me & FS2open
Post by: Lightspeed on March 22, 2004, 04:09:48 pm
no, it's not in mantis - technically it's not bugs :rolleyes:
Title: BUGS: It is a bad day for me & FS2open
Post by: Sticks on March 22, 2004, 05:10:58 pm
That's why there's the "Feature" option in Mantis. :sigh: