[RandomTiger]

As I hope you are aware Fred2_open is being ported to OGL. After this is finished we will want to stop developement on *software* Fred_open as soon as possible and no more versions of it will be released.

If you are a Fred_open user or intend to be in the future could you please test that the OGL version works OK with your system *now*.

Fred2 OGL works perfectly on my system but might not on yours. And if it doesnt you will find it a lot easier to get me to fix it now rather than later when I'll probably be up to my eyeballs in something else.

Please sticky this post.

[Taristin]

Does this mean there'll be Fred2_open HT&L?

I would test, but my PC isn't finished yet.

[Zarax]

Can you make a non debug version?

Warning: weapons.tbl(992):
Error: Required token = [@Laser Color:], found [@Laser Glow: 2_laserglow03]
in weapon: GTVA Rapid Laser.

File:H:\projects\Freespace\scp\fred_upgrade\code\Parse\PARSELO.CPP
Line: 372

Call stack:
------------------------------------------------------------------
    fred2_open_ogl_d.exe 0053a9b9()
    fred2_open_ogl_d.exe 005430f0()
    fred2_open_ogl_d.exe 005457ce()
    fred2_open_ogl_d.exe 00545bd6()
    fred2_open_ogl_d.exe 0044bb4d()
    fred2_open_ogl_d.exe 00443fb9()
    fred2_open_ogl_d.exe 0088dc82()
    fred2_open_ogl_d.exe 0088d5e4()
    fred2_open_ogl_d.exe 0088b189()
    fred2_open_ogl_d.exe 0088b625()
    USER32.dll 77d37b17()
    USER32.dll 77d3cd68()
    USER32.dll 77d1459d()
    USER32.dll 77d1bc56()
    ntdll.dll 77f6589f()
------------------------------------------------------------------

[RandomTiger]

If you can get that to happen with the release build its my problem if it only happens in debug its a problem with your table.

[diamondgeezer]

Originally posted by Zarax
Can you make a non debug version?

[jdjtcagle]

Works good here!!;)

[Zarax]

Originally posted by RandomTiger
If you can get that to happen with the release build its my problem if it only happens in debug its a problem with your table.

Well, i always had problems with debug releases...
Non debug ones are ok...
BTW, i'm using Inferno tables so i don't know what could be wrong...

[phreak]

inferno tables are bugged out the ass.  we're working on fixing any errors in future releases.

[Zarax]

Yes, but the fact they works means that the debugger is a bit to picky on them...

[karajorma]

Originally posted by Zarax
Yes, but the fact they works means that the debugger is a bit to picky on them...

As was explained on the other thread what you think is just FRED being picky could actually be responsible for mysterious crashes in FS2_open.

[Bobboau]

actualy more likely than not, it is the explaination for a ship haveing incompatability with things you specificly made them compatable with, or weapons renering wrong, or other little things missing that you don't understand why becase the tales look fine, debug builds do ***** a lot more, but that's judt becase relese builds don't tell you about a whole ****loa of errors that may be going on breakeing ships, it's a realy realy good idea to spend fifteen minutes fixing the problems debug build give you.

[Omniscaper]

When the debugger rports problems with a Table, is it supposed to freeze? Once I hit ok for all the problems, Fred just sits there, with my desktop visible where stuff is supposed to be. I'm using the new ATI Catalyst 4.1 and has something new with OGL but I'm not sure if that is the cause.

Another question, is the OGL Fred hardware assisted OGL? Or is OGL always utilizes HT&L? I know of programs that use software OGL.

[karajorma]

Try it with unmodded FS2 and see what happens Omniscaper.

[Black Wolf]

Before I dive into attempting to fix these Operation Ragnarok tables, two things...

1 - These aren't going to fire if I put one too many returns in between entries are they? IE When it says it expects to find operator A on Line X, but is finding Operator Y, this is because they're out of order?

2 - It's not going to whinge if I don't have weapons like the flail on every fighter is  it?

[Goober5000]

Originally posted by Black Wolf
Before I dive into attempting to fix these Operation Ragnarok tables, two things...

1 - These aren't going to fire if I put one too many returns in between entries are they? IE When it says it expects to find operator A on Line X, but is finding Operator Y, this is because they're out of order?

Correct.

2 - It's not going to whinge if I don't have weapons like the flail on every fighter is  it?

The reason it didn't like the Flail is that IIRC the Flail wasn't listed in the weapons table.  If you specify a weapon that you don't have, it's not going to like that.  If you don't specify a weapon that you do have, it shouldn't matter.

[CP5670]

It would be nice if each of the debug error messages also showed something about how critical the bug is. Some bugs prevent the game from even loading up (e.g. using laserglows for a secondary weapon) while others do not have any noticeable effects (like the lack of subsystems at the end of a ship entry), but they are all given the same "priority."