Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: xioutlawix on October 03, 2004, 08:22:07 pm
-
I don't know if its a problem with the fs2netd install, or the media packs i downloaded, but I can't seem to see missiles fired at me, or I noticed if I pick the tornado missiles (if I recall their name correctly) I can't see myself fire them at all, but they're definitely being fired.
Does anyone know what might cause this problem, or what file I might be able to nab to replace them?
Much appreciation, thanks!
-
Sounds like a problem with the missile models...or...the textures at least...
I dunno...I'm not a coder or modder...ask some of the other guys around here.
-
I'm not sure if it's the trails or the missiles themselves that aren't being rendered in your case (screen captures help identify the problem) but in all likelyhood it's neither your fault nor something you can do much about. If you're using the "old engine build" then the first thing you need to be aware of is that any bugs either present in FS2 retail or introduced by the FS2NetD code not directly involving multiplayer will be present in that build. Though it's as close to "official" as you'll find for that demand right now, it does not include any of the SCP fixes or workarounds.
If you're using FSO proper, then I'd need to know more specifically which build you're having the problem with. It's come up before, but I don't remember the exact solution.
-
I'm actually using latest build, 3.6.
I basically went directly between all the points, shortest distance possible:
Installed Frespace 2 retail, installed patch 1.2, installed 3.6 open source, then installed the fs2netd stuff, and then did the media packs. I don't think I screwed up anywhere, as the multiplayer is in fact working, but its just those missiles puzzling me :P
-
Have you ticked the enable jpg, tga textures box in the Features>Graphics part of the launcher?
I'd have expected a lot more missing than just that but it's a possible cause.
-
Yep, I've checked all the boxes underneath there. I'm guessing its probably a missing model or texture by its nature.
Well, texture, since the model's required for it to actually be shooting, I imagine.
-
Ticked them all? That may be a problem. Just use spec, glow, jpgtga and if you dare, pcx32. Don't use the cell shading... or some of the others who's name and function escape me.
Or better yet, post your command line options, and we'll nitpick. :)
-
Hehe, ok.
My current command line options are:
-spec -glow -pcx32 -jpgtga -d3dmipmap -cell -phreak -ship_choice_3d -d3d_no_vsync -2d_poof
-
Definately turn of cell.
Try it again. It doesn't seem like it'd cause what you said is happening, but turn it off anyway, and try it again.
-
If the pof was missing the game would crash, so the problem would be elsewhere, i`d say the map or maps, i`ve had this kind of problem with models using dds maps before. Once I put the dds maps in the effects folder the problem vanished. :)
-
i wonder why cell is still in there *sigh*