[Kazan]

fred2_open_r -mod TBP
I have fixed -mod support for fred2 - what was breaking it makes it so im suprised fred2 _ever_ worked (it was being broken by MFC calling chdir!) -- the only reason why it woriked with retail was probably because everything was in VPs -- REMEMBER: "-mod somemod" must be the last argument right now


fred2_open_r -fred_no_warn
I also get annoyed with warning messages when i don't want to see them - so i added the command line flag "-fred_no_warn" which supresses warning messages

fred2_open_r -fredhtl
Also I was annoyed with the "Do you want to run fred in HTL? (Buggy)" popup - so i replaced it with the command line arg "-fredhtl"

(Warning: right now this flag is working BACKWARDS)

You can pick up the build here: http://www.deepbluebettas.com/fs2/fred2_open_r.exe

[karajorma]

Words fail me. I've been waiting for this for too long to say anything sensible about it

[jdjtcagle]

Yess!!!
perfect timing

[RandomTiger]

Please note people htl Fred does not work properly.
Also if you ignore fred warnings your MOD's might crash fs2_open and cause other problems.

[Kazan]

both of those are true

[karajorma]

Bug Reports.

1) Choosing to view a model by outline appears to do nothing now. The model remains invisble.

2) I'm getting an error like this - Serious error loading model (pof name), 120 normals capped to 0. What does that mean?

3) Can you make it so that when you try to open a mission it defaults to looking in moddir\data\missions? Cause at the moment it simply looks in whatever folder you were looking in last and going back up the directories and then burrowing back down again to the correct one is almost as big a pain in the arse as moving the folders around was without the mod flag

4) I'm not getting any warnings about HTL mode even though I didn't use the flag.

5) Several errors are being reported by my MindGames missions that weren't reported by previous versions of FRED2_OpenGL. One that is particularly odd is this one :-

 Null vector in vector normalise. Trace out of vecmat.cpp and find offending code.

 I have a couple of wings of ships that are placed above the plane. The lines drawing the y vector are in the wrong place (and in addition only two are drawn instead of the 6 that should be).

[Kazan]

1) weird.. probably not something i did, but it will need to be looked at by someone

2) ditto

3) not really... they used MFC and that's DIRTY

4) HTL mode only is enabled if you use "-fredhtl", so you won't get warnings (that popup) that was the point of the flag, so that annoying popup won't show it's ugly head

5) grr.. i had that null vector crap, what was your previous version of FRED2? Was it an OpenGL build because this is

the last thing is probably to do with it being an OpenGL build

[phreak]

that null vector warning shouldn't show up if its a release build.

and its a known problem that OpenGL doesn't display wireframes, but that should be easily fixed

[Kazan]

phreak: it's a release build

[karajorma]

Originally posted by Kazan
3) not really... they used MFC and that's DIRTY

Damn. That's really annoying. Oh well at least the recently used file list will help mitigate the annoyance somewhat.

Originally posted by Kazan
5) grr.. i had that null vector crap, what was your previous version of FRED2? Was it an OpenGL build because this is

the last thing is probably to do with it being an OpenGL build

I never saw it in the OGL builds until now.  I got several other errors that I'd never seen before too. I can provide more info on them if you want it or just wait and see if the next build clears them up along with this one.

[Flipside]

I've got wireframes in OpenGL Fred up to now, just downloading the new one now......

[Bobboau]

I just commited my stuff last night, will this have the fixes LS wanted in there (ie did you update just prior to posting this)

[Flipside]

Ok, the problem isn't wireframes not appearing, the problem actually looks almost similar to the old skybox problem.....





The model tends to rotate in an opposite direction to the camera, and has strange clipping on it.

[Bobboau]

... what the hell is that?

[Flipside]

I could tell you, but then I'd have to shoot you, and myself

Suffice to say the wireframe itself is correct, but it is moving incorrectly with reference to the camera If you DO need more details, let me know, and I'll do it with something more familiar

[Goober5000]

Originally posted by karajorma
3) Can you make it so that when you try to open a mission it defaults to looking in moddir\data\missions? Cause at the moment it simply looks in whatever folder you were looking in last and going back up the directories and then burrowing back down again to the correct one is almost as big a pain in the arse as moving the folders around was without the mod flag

You should be able to do this somehow.  Put it in Mantis and I'll take a look at it.

[Trivial Psychic]

Alright, I just tested this out.  From what I can tell, it seems to be defaulting to htl, and the -fredhtl flag causes it to load in NON-HTL.  I can tell partially because without the flag, its displaying all of the same problems I noticed previously when running FRED_OGL under HTL.  Paths & dockpoints are all rendered WAY away from the ship, or change their position drastically as the camera moves.  It also refuses to load any mission not created in HTL.  These are bugs from the previous version under HTL.

Next, in non-HTL mode (ie, with -fredhtl flag) it is displaying all of the ships in LOD1 or 2, never in LOD0 no matter how close you get.

I think I'll revert to the previous version for now.

Later!

[Kazan]

meh.. i inverted a logic statement because of some internal variable names... grr

[IceFire]

I didn't get a full chance to test...but having a good stable FRED build is something good and having HT&L to boot or even 3D acceleration at all is amazing.

Thank you sir(s) for putting this together....certainly when BWO gets properly underway after my exams are over this or a updated version will be a big boon!

[Kazan]

BWO isn't underway.....