[Captain Pyro]

hello, i know there have been posts on this subject already, but i haven't seen one that brought up a definitive solution.

I'm on a 'white' IMac, C2D 2.16, X1600 256Mb graphics, 1Mb system, OS X 10.4.11

I'm running 3.6.9 currently and have tried a few 3.6.10 builds and FS2_Open_rev4689_0704.

I always get "Unrecognized command line parameter, "-jpgtga", continue?" and "Unrecognized command line parameter, "-", continue?" when starting the launcher and also when launching from the launcher.  Nothing I've tried seems to shift either of these messgages.  I can't see how to get at the command line from osx to alter the options manually... I've never needed to know how to do this on a mac.

I'm running open gl non HT & L.

I seem to get the same problems a lot of other people get, namely, the target display in the lower right doesn't show many ships, and is usually a big block of whatever colour you've set it to (especially annoying if you need to take out sussystems or turrets), and until i put the game into software mode, most of the ships themselves didn't render.  Most ships are shown semi translucently and frequently very dark.  Primary fire is invisble.  Ships coming in or out of subspace make huge blocky tiles and the nebula is ok from a distance but pretty blocky up close.

I've got a media vps folder stuffed full of things in the directory i run freespace from.

I installed a couple of days ago from Turey's java installer.

Is there any known fix yet?  I'm an FS2 player from years ago and have just rediscovered the goodness.  I do have a set of FS2 and FS2 Gold original discs kicking about from my old PC days,but the only PC left in the house is an old P3 laptop with an ATI mobility chipset that I think probably isn't up to it.  Back in the day I used to play this with no issues on an AMD XP1700+ with GF2MX or GF3Ti.

If there isn't a fix, is there anyway (without mucking about with bootcamp or parallels or whatever) I could run standard FS2 on OSx?

Finally, is it possible to get the original radar back?  I'm really not sure I like the new one... 

cheers!

[Jeff Vader]

I always get "Unrecognized command line parameter, "-jpgtga", continue?"

-jpgtga is not present as an option in 3.6.10 builds (since they're always on in those builds). If you can continue from that error report (one can in Windows by clicking OK), it should vanish.

and "Unrecognized command line parameter, "-", continue?"

Not sure about this one.

I can't see how to get at the command line from osx to alter the options manually... I've never needed to know how to do this on a mac.

I guess the manual way is pretty much the same as on Windows (right-click the executable you want to use, go to Properties and enter the command-line flags there or something).

I've got a media vps folder stuffed full of things in the directory i run freespace from.

Please specify. The \mediavps\ folder should have the MediaVPs. No more, no less.

Finally, is it possible to get the original radar back?  I'm really not sure I like the new one... 

If you mean that you don't like the 3D radar, it can be disabled (it is enabled by the -orbradar command-line option).

[Captain Pyro]

rereading some of the earlier information, i htink it says I should have had a 'straight' install before running Tuvey's installer over the top of it? Might that be some of my trouble?  How do you do a straight install of non-open original FS2 on OSx?  Or have I completely misunderstood?

Also now understand the command line thing... you remove them in the drawer...  

at the bottom of the list there was a null which would have been the '-' switch.  I took out that and the '-jpgtga' and they no longer occur on load.

Figured the 'orbradar' thing too.  I kinda like it, it's pretty, but with all the other graphic problems at the mo it's a distraction.  What I have in mediavps is this:
readme.txt
mv_textures.vp
mv_music.vp
mv_models.vp
mv_effects.vp
mv_core.vp
mv_adveffects.vp
mp-710_models.vp
mp-710_effects.vp
mp-710_adveffects.vp
and a folder called 'data' which contains fs2open_pxo.cfg

I haven't added or taken away anything from/to mediavps, it's just what Turey;s installer put there.

Should there be more?

Sorry if I'm asking lots of n00b questions!

I'm now running a 3.6.10 (FS2_Open-20080717_trunk) and it's sort of ok, the targetting area is still a problem but the weirdest thing is that mouse speed has gone right down the pan!  it  C R A W W W L S now regardless of settings... 

[Jeff Vader]

Most instructions say that it would be nice if you had FreeSpace2 prior to installing FSO. But this is solely because that way you can save bandwidth and time by not downloading the retail files. So don't worry. You should have everything. If you need further peace of mind, post what vp files you have in \freespace2\ so that we can confirm if you have all of them.

I suspected that you might have had an extra - in the command-line. If it works now, good.

The 3D radar is pretty, yes, but I too prefer the original 2D one. Mostly because of As Lightning Fall. You'll understand once you get to that point.

Your \mediavps\ folder seems to be fine. All of those files are the actual 3.6.8 Zeta MediaVPs (plus the readme and the \data\ folder).

Asking is more likely to get you results than not asking. So no worries about that.

I checked the Latest Linux and Mac builds thread and you seem to have the current stable 3.6.10 Mac build. Good. Continue using it.

Don't really know about those targetting issues and such. Hopefully some Mac people will stumble upon this thread.

[Captain Pyro]

ta!    I played all the way through the main campaign and several mods at the time, but it was a long time ago, so don't remember the mission you mention, but I'm sure it'll all come flooding back.

vp's in the main freespace directory are

warble_fs2.vp
tango3_fs2.vp
tango2_fs2.vp
tango1_fs2.vp
stu_fs2.vp
sparky_hi_fs2.vp
sparky_fs2.vp
smarty_fs.vp
root_fs2.vp
patchw32.dll
multi-voice-pack.vp
multi-mission-pack.vp
FS2OGGcutscenepack.vp

thanks for the thoughts so far.  from what I saw earlier on the forums, the underlying graphics issue seems to be something that just 'happens' with the X1600 on the IMac.  There was some thought that maybe it might have been tracked down and the offending bits sidestepped by 3.6.10 final I thought... I hope so!    

Good to see ATI are still causing grief with their drivers after all these years.  Shame that updated video drivers aren't as get-holdable of for macs and that you can't just rip the side off and stick a different card in an IMac.  Oh well, I guess the form factor was a lot of the reason i got this one. 

can anyone comment on the advisability of G4 macs (maybe a blue and white?) and fs2 open?  just thinking what other hardware i could pick up cheaply...

[Jeff Vader]

You seem to have all the retail files. Good.

And not to worry. Intel graphics chips are another pain in the arse. People often have the most peculiar problems with them. But for now I have nothing more to say. If other Mac users know of circumventions to the aforementioned graphics issues, do tell.

[colecampbell666]

[Tourettes Guy]DON'T TALK **** ABOUT ATI![/Tourettes Guy]

A G4 may run it, once again it depends on the GPU/RAM/whatever specs. You don't need much of a processor for the MVPs or FSO, but a good GPU (read: ATi 9500+) is necessary.