[Grug]

ppl are lazy and stupid... to get that to work I have to do all that typing...

[Nico]

Originally posted by Bobboau
FS2 won't run, or FSO won't run?
and if FSO how far do you get?

FS2. Well, to be exact, it runs, won't crash, but is basically unplayable. It used to work, but I changed hardward parts, and I have no idea which one is the problem.

Originally posted by Grug
ppl are lazy and stupid...

Sorry about being lazy and stupid

[Bobboau]

so FSO works fine?

[Nico]

it works the same: very choppy sound, slow and laggy game ( when I mean slow, I DO mean slow, like some inversed time compression. weird, odd, annoying. When there's little in the mission, it runs at normal speed, when there's action, the thing slows down. Funny, innit? ).

[Bobboau]

wait, you mean it's not bad frame rates it's like the clock is running slower?

that is bezar

maybe it's a sound card driver, what are your specs?

[Gregster2k]

Definitely should allow ambient lighting to be set PER MISSION, and while at it, be able to be differently colored, too (for when a lit background sun or skybox just cant cut it)

that is how most other games do it. Freelancer is an example, for one. I can probably think of others, but they've slipped my mind for the time being.

To fix the problem of some people having fits over this,
ADD a new "ambient_ignoremsn" to make devs and debuggers happy.
INTENDED USE: tells FS2 to IGNORE all mission parameters for ambient lighting and use its default ambient light levels.

keep ambient_factor
IF user specifies a factor and it isn't 1.00,
AND IF ambient_ignoremsn is OFF,
THEN multiply mission-specified ambience by ambient_factor.
*****result: ambient_factor scales up/down mission-specified ambient light levels, so players can adjust to their taste.

OTHERWISE,
IF user specifies a factor and it isn't 1.00,
AND IF ambient_ignoremsn is ON,
THEN FSO use only default FS2 ambience levels,
AND multiply default FS2 ambience levels by ambient_factor.
*****result: ambient_factor scales up/down only standard FS2 light levels, bringing the same effect ambient_factor currently has on FSO and making developers or purists very happy.

All we need is a simple disabler for the potential mission-specified thing, and a modfication of current method of ambience scaling. Sounds good logically, but can it be done in code?

[Nico]

Originally posted by Bobboau
wait, you mean it's not bad frame rates it's like the clock is running slower?

that is bezar

maybe it's a sound card driver, what are your specs?

I thought about that too, since I did change the soundcard around the time it started messing up ( switching from a SB16 to a SB128 -no choice: ISA to PCI ). but seems it's not it.
It's been like that for a couple years, tried many things, that's a lost cause.