Hard Light Productions Forums
Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: Axel Wers on June 29, 2011, 03:38:28 am
-
The newest release it seems is useless for my PC. I still use an older release (I don't know its version number but file has size 136 MB and was released with FSPort 3.1.1), only this release brings me smooth graphic. Newer release which came with FSPort 3.2. gave me problems with big ships, for example when I got an Orion to view on my HUD graphics and FPS drastically slowed down. And the newest release which came with FSPort 3.3. is totally useless for my PC. I am unable put Hades with textures to FRED. Loading of object takes very long time and finally FRED crashes down with an error message. It seems that some object (like Hades) are "too poly". I have nVidia 7300 GT 256 MB, but I don't think that graphic card is really poor for those objects.
Any ideas?
-
There have been reported issues with various models contained in MV_FSPORT.vp. These issues were caused by a build error and have been fixed. If you downloaded mv_fsport before this was posted, please redownload it from the release thread or right here. (http://www.lunardigitalproductions.com/downloads/fs1/fsport/fsport-mediavps.7z)
Sorry for the inconvenience and thanks for your understanding. ~ Mjn
-
I HAVE that file already downloaded. Error still appears after I enable ship models Hades or Typhon#Hulk
(http://i51.tinypic.com/n2lwzl.jpg)
-
K, then. Log?
-
Do you mean this log?:
...
-
Preferrably this log (http://www.hard-light.net/forums/index.php?topic=56279.msg1180359#msg1180359).
-
Last I heard (Given a few years back) the 7300 was rather poor compared to some of its predecessor models. If that is true then I wouldn't really be surprised if the new HTLs are ganking FRED (By the way, having ship outlines enabled bogs down the response time quite a bit, if that's the case turn them off).
-
Maybe yes, but because too much hi-poly Hades I won't buy a new graphic card :D
OK I attached logs from FRED FSO and FSO, because in both cases it crashed down.
I use Launcher 5.5g
Ran fred2_open_3_6_12d_INF.exe and fs2_open_3_6_12d_INF.exe
Used FSPort 3.3 + mediaVPS (probably this makes all problems) and active mod is ST:Reborn 1.2
I created simple mission with Ulysses (Alpha 1) and Hades.
Mission had very low FPS (about 4-5) and after as I warped out game crashed
Here is clip what I saw in mission: http://www.youtube.com/watch?v=vg0iNxF2aN8
[attachment deleted by ninja]
-
-mod fsport-mediavps,mediavps,fsport-mediavps,fsport-str,fsport,mediavps_3612I... but... that is... how did... que
How have you managed to cook up this -mod flag? The game engine loads FSPort MediaVPs, (3.6.10) MediaVPs, FSPort MediaVPs again, ST:R, FSPort and the 3.6.12 MediaVPs.
And your \mediavps_3612\ directory is empty, so you don't even have the 3.6.12 MediaVPs, even though they are required by the FSPort MediaVPs.
Edit: If you still have
-mod fsport-mediavps,fsport,mediavpsas a custom flag in the Launcher, remove it. You don't need to have it anymore.
-
Hmm, but when I remove
-mod fsport-mediavps,fsport,mediavps
from Launcher it won't load hi-poly models, but standard from FS game. Tested now.
:wtf:
-
Well, like I said, according to your log
Searching root 'C:\Games\FreeSpace2\mediavps_3612\' ... 0 filesYou don't have the 3.6.12 MediaVPs (or at least they are not in \freespace2\mediavps_3612\ ). You need them if you want to use the FSPort MediaVPs.
-
OK I downloaded 3.6.12 and installed (without MV_Advanced.vp). Now I have hi-poly ships without that custom flag.
However problems with Hades are still there.
FRED si better. Now when I load Ship Models from menu, FRED doesn't crash but Hades disappeared.
The game is the same as above. Hades is "invisible" and when I jumping out game crashed down.
New logs attached.
[attachment deleted by ninja]
-
Now it would appear that you do not have the FSPort files in \freespace2\fsport\ .
-
Impossible. I have there that directory with all files.
This is my launcher, it's right?
(http://i55.tinypic.com/2cn9gn7.jpg)
C:\Games\FreeSpace2\fs2_open_3_6_12d_INF.exe -mod fsport-mediavps,fsport-str,fsport,mediavps_3612
-spec -glow -env -mipmap -missile_lighting -3dshockwave -cache_bitmaps -dualscanlines -targetinfo -orbradar -rearm_timer -3dwarp -warp_flash -window
And a new log. Now I cancelled mission with Hades, game didn't crash.
[attachment deleted by ninja]
-
You are missing the actual FSPort. Have you installed it in a folder named "fsport"?
-
Whoops, it's fs-port, not fsport.
fs-port probably is obsolete directory.
I am going to change it and send new log.
-
Was the FSPort folder ever named fs-port? :confused:
-
No, it was not. It has always been named 'FSPort' since I have been around.
-
Yes, it was fs-port. Probably some obsolete title, I am not sure.
But I have still the same issues.
OK, now FSPort and ST:Reborn should be correctly installed with mediaVPS 3.6.12.
New logs attached. Check fred log too, there is few interesting errors. Hades has some issues with engines.
[attachment deleted by ninja]
-
You say you still have problems with the Hades? 1) you're using a 7300, 2) the Hades has like 80,000 polygons the last time I saw a polycount. If it was dumbed down it's still probably 60k or something... Which is a LOT for your 7300 to handle.
And you're gonna find errors with the engines because FSO doesn't like how we did the engine subsystems, IIRC. Probably not, I haven't looked at fsport for 6 months due to being in security forces training, but that's what I remember before I left.
Edit: Whoah, font size changes on my iPod.
-
You say you still have problems with the Hades? 1) you're using a 7300, 2) the Hades has like 80,000 polygons the last time I saw a polycount. If it was dumbed down it's still probably 60k or something... Which is a LOT for your 7300 to handle.
Yes, there is a problem. Too much polygons. 80 000 polygons? Why so much? All other hi-poly models goes smoothly. Original Hades has less details than original Orion, hi-poly Orion goes perfectly. Hades at all. The same with the newest Typhon. Both are from the newest fsport-mediaVPS release. Other models are OK.
I don't know how many polygons has Karnak, but Karnak goes without problems too.
-
Yes, it was fs-port. Probably some obsolete title, I am not sure.
But I have still the same issues.
OK, now FSPort and ST:Reborn should be correctly installed with mediaVPS 3.6.12.
New logs attached. Check fred log too, there is few interesting errors. Hades has some issues with engines.
Sorry, but it has not been 'fs-port' since at least the 3.2 release and the install instructions clearly state to name the folder 'fsport'. I'm still trying to figure out what your issue is.
And you're gonna find errors with the engines because FSO doesn't like how we did the engine subsystems, IIRC. Probably not, I haven't looked at fsport for 6 months due to being in security forces training, but that's what I remember before I left.
Cobra, you're awesome.. but try not to troubleshoot when you are 6 months out of the loop...
Yes, there is a problem. Too much polygons. 80 000 polygons? Why so much? All other hi-poly models goes smoothly. Original Hades has less details than original Orion, hi-poly Orion goes perfectly. Hades at all. The same with the newest Typhon. Both are from the newest fsport-mediaVPS release. Other models are OK.
I don't know how many polygons has Karnak, but Karnak goes without problems too.
Calm yourself... I am not in the mood to try an help someone who is demanding fixes with an attitude.
Now, would you be so kind as to try to run with a nightly build? Download the latest one here. (http://www.hard-light.net/forums/index.php?board=173.0)
-
As far as I can tell, using the latest FSPort and STR release, as well as a nightly build, everything goes without a hitch. No debug warnings, nothing, everything juuuust fine.
Yes, there is a problem. Too much polygons. 80 000 polygons? Why so much? All other hi-poly models goes smoothly. Original Hades has less details than original Orion, hi-poly Orion goes perfectly. Hades at all. The same with the newest Typhon. Both are from the newest fsport-mediaVPS release. Other models are OK.
I don't know how many polygons has Karnak, but Karnak goes without problems too.
There's a simple solution for you. Do not play with the mediavps. See? It's easy. VA spent a whole lot of effort on getting the Hades as pretty as it can be. The fact that it needs a halfway modern system to run shouldn't be a surprise.
-
OK, I tried that fs2_open_3_6_13r_INF-20110629_r7290.exe and it seems that FRED and FSO are going without any problems. Mission with Hades goes smoothly and I could warp without ANY game issues or crashes.
I would recommend run FSPort 3.3 and ST:R 1.2 under 3.6.13_INF.exe.
Thanks.
-
You say you still have problems with the Hades? 1) you're using a 7300, 2) the Hades has like 80,000 polygons the last time I saw a polycount. If it was dumbed down it's still probably 60k or something... Which is a LOT for your 7300 to handle.
Yes, there is a problem. Too much polygons. 80 000 polygons? Why so much? All other hi-poly models goes smoothly. Original Hades has less details than original Orion, hi-poly Orion goes perfectly. Hades at all. The same with the newest Typhon. Both are from the newest fsport-mediaVPS release. Other models are OK.
I don't know how many polygons has Karnak, but Karnak goes without problems too.
Given their age the Orion and Karnak would have less detail compared to the Hades and Typhon, even though the Typhon has a lot of detail it's not quite as much overall, except near the engines. The new Hades however has many small details strewn across the entire length of the ship, particuarlly in the trenches. As I mentioned before going off of memory the 7300 didn't turn out to be as good of a card as it was expected to, and take the other specs of the system into effect, in the end it's likely that what you're using is simply out-of-date for these newer MVP releases.
-
Yes I saw already that Hades has lot of details, it looks really pretty. So it doesn't seem problems with my 7300 because under 3.6.13_INF it goes without any problems with all details and effects.
-
It's a good thing you're original topic title is incorrect then isn't it? :rolleyes:
-
And you're gonna find errors with the engines because FSO doesn't like how we did the engine subsystems, IIRC. Probably not, I haven't looked at fsport for 6 months due to being in security forces training, but that's what I remember before I left.
Cobra, you're awesome.. but try not to troubleshoot when you are 6 months out of the loop...
That's why I covered my bases and said I wasn't too sure. It was only a possible explanation. :P
-
That's why I covered my bases and said I wasn't too sure. It was only a possible explanation. :P
When I tested some earlier FSO releases (it could be sometimes between 2003-2005) it has more bugs than WindowsME :D But each newer release was better and better.
-
You say you still have problems with the Hades? 1) you're using a 7300, 2) the Hades has like 80,000 polygons the last time I saw a polycount. If it was dumbed down it's still probably 60k or something... Which is a LOT for your 7300 to handle.
Actually, last time I looked at the pof, it had about 104,000 polygons.
-
Yep, LOD0 with all turret subobjects etc counted in is around that.
-
You say you still have problems with the Hades? 1) you're using a 7300, 2) the Hades has like 80,000 polygons the last time I saw a polycount. If it was dumbed down it's still probably 60k or something... Which is a LOT for your 7300 to handle.
Actually, last time I looked at the pof, it had about 104,000 polygons.
Dayumn.