Hard Light Productions Forums
Hosted Projects - FS2 Required => Inferno => Topic started by: Goober5000 on November 09, 2017, 12:40:43 am
-
(http://staff.hard-light.net/goober5000/images/inferno-banner.png)
The Inferno campaign continues many decades after the events in FS2. A massive mod with 140 new models ranging from the smallest of fighters to the largest capital ships ever seen in FS2 so far.
Project lead:
Senior Staff:
Other Staff:
- Alikchi
- Knight Templar
- Phreak
- RoachKoach
- Roy Fokker
- Sesquipedalian
- Si|eNt(\/)inion
- Spicious
- Stealth
- StratComm
- Tiara
- Untouchable
Original release threads: Inferno board (http://www.hard-light.net/forums/index.php?topic=16169.0) | FreeSpace Modding board (http://www.hard-light.net/forums/index.php?topic=16171.0)
I decided to go through and patch all the mod warnings in Inferno R1, as well as add a checkpoint to the climactic battle. (Back in my day, if you got shot down while disarming the Nemesis's beams, you had to start the mission over from the beginning!)
Here's a summary of the changes:
Added a mod.ini
Fixed all debug messages
Null MOIs on many models
Invalid radii on the Stinger and Vortex models - replaced these with the Tempest model
Invalid shields on a few models - I either used approximate substitutes or (in the case of the Ancient models) deleted the shields
Various minor errors: number of LODs, subsystem mismatches, paths, invalid docking points
Standardized the length of the civil war at 8 months
Formalhaut -> Fomalhaut and other spelling fixes
Mission fixes
Title capitalization
One Step At a Time: properly fail directives when transports destroyed
Old Enemies: Show/hide jumpnode, use turret/beam-lock instead of play-dead, fix Argo docking, fix Special Ship bug
Showdown: Add Kismat to escort list, fix the Olemus/Diablo beam-fire sequence
Taking the Gate: fix beams firing on weapon modules
The Only Possible Outcome: standardize on Edward Kelly
Nemesis: Added checkpoint, added more ships to escort list
Gigas: Made comm nodes self-destruct if crystal destroyed (like in Into the Lion's Den), added more ships to escort list
Both the FSO Installer (http://www.fsoinstaller.com) and Knossos (https://github.com/ngld/knossos/releases) have been updated. If you prefer to install it manually, download it here (https://porphyrion.feralhosting.com/datacorder/files/installer_files/campaigns/inferno.7z).
-
The classic returns! Awesome! :yes:
-
Yeach i renember the firsf mission
You need to disable fighter wing the whole
-
You really have way too much free time :P.
Thank you!
-
Thank you Goober!
However, would it be possible to put the new model Warlock in there? Also, the Scorpions looked like their old selves and not 2014 MediaVPs.
-
Y'all are welcome. :)
It's not possible to use the new Warlock model because of the different number and arrangement of turrets. This would entail rebalancing. I didn't want to make actual gameplay changes; I just fixed bugs.
The Scorpion model is not part of the regular MVPs since it does not appear in FS2. It would require the model from the FSPort MVPs. But I didn't think it was worth adding any HTL models because they would look out of place next to the standard-poly models that make up the rest of the Inferno ship set.
-
Is this version still playable with Retail? ;)
AFAIK both old Infernos had the same infamous doctrin like the FSPort... it still have to be playable with Retail :D
-
Considering that I wanted to add a checkpoint and checkpoints aren't supported in Retail, I did not retain Retail compatibility. :p
-
AFAIK both old Infernos had the same infamous doctrin like the FSPort... it still have to be playable with Retail :D
R1 was from before the source code was released so it was originally built only for retail. The SCP patch was made to fix bugs that could only be found using SCP debug builds that didn't really stop it running fine on retail.
-
hey thanks :-)
-
a day later and here I am, trying to launch it and getting the following error:
mv_mus.tbm (line 72): Missing required token: [#Soundtrack End]. Found [#Name: FS2_Amb_B01.ogg and so on
Seems to me like the config is not in order.
-
hey thanks :-)
You're welcome! Happy to breathe new life into an old classic. :D
a day later and here I am, trying to launch it and getting the following error:
mv_mus.tbm (line 72): Missing required token: [#Soundtrack End]. Found [#Name: FS2_Amb_B01.ogg and so on
Seems to me like the config is not in order.
This is a SCP bug. (https://github.com/scp-fs2open/fs2open.github.com/pull/1506) Either disable MV_Music.vp, or use a recent nightly build.
-
Is there any other way around this bug, anything newer than Oct. 31st gives me graphical anomalies. BTW, I get a slightly different error message. Mine says: "mv_mus.tbm (line 86): Missing required token: [#Soundtrack End]. Found [#SoundTrack Start] instead"
-
Is there any other way around this bug, anything newer than Oct. 31st gives me graphical anomalies.
Define "graphical anomalies".
-
I've mentioned them in other threads, such as in the support forum. Unfortunately, they sometimes don't manifest with one mod, but will with another. With this mod however, builds such as March 7th looks proper, but the radar is completely empty... no dots at all. Also, in the lab, there's no grid around the titles & shipnames. New builds such as the June 6th however, all models are being rendered in the lab, but in the loadout screen and in mission, they come up blank. Oddly enough however, in the first mission as the Carolina warps in, it is initially visible, but then almost completely vanishes as soon as the jump is complete. All that is visible is the engine plumes and a couple of submodel details on the ventral. I also saw some bombs fly by that were being rendered. Radar is empty in this build as well.
-
Is there any other way around this bug
Disabling MV_Music.vp doesn't work?
-
I was hoping to not lose the enhanced music qualities. It's odd how the thing its complaining about doesn't exist.
-
Crash on the last mission when destroying a comm node crystal:
Error: Model 22568 ('commnode.pof') must have at least one point from submodel_get_points_internal!
File: modelinterp.cpp
Line: 1342
ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 162 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 2410971 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 3845724 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 3048897 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 3052061 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 1057114 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 672348 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 176368 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 188040 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 26400 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 23013 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 946276 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 7161 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! SDL_main + 140 bytes
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20180506_a90e480_x64_SSE2.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
-
Crash on the last mission when destroying a comm node crystal:
Error: Model 22568 ('commnode.pof') must have at least one point from submodel_get_points_internal!
File: modelinterp.cpp
Line: 1342
This is a known issue (https://github.com/scp-fs2open/fs2open.github.com/issues/1708) that has been fixed (https://github.com/scp-fs2open/fs2open.github.com/pull/1733). A more recent nightly build should work.
-
So I may have found a solution to my graphical issues... for this campaign anyway. First, to recap:
Build - 2017-10-31 - Last build I knew without any graphical problems, but complain about the music thing.
Builds just after 10-31 - Often work initially, but subsequent restarts of the build result in zero ambient lighting. Light sources are glowmaps & points, weapons, engines, & background.
Somewhere after 10-31 and before 2018-03-07 this lighting issue appears to have been fixed, but radar is empty.
New builds - no radar, & (with a few random exceptions) no model rendering. It should be noted however, that these graphical issues are NOT present in debug builds, but they're too slow to play on.
It appears however that the Jan 4th build has the lighting issue fixed but the radar is still working. Now, with my track record, I might load it up tonight only to have the lighting issue show up again. Also, this build isn't new enough for Nostos.
I should also mention that I went through and squashed more model & table bugs, imported some higher-detailed models & effects, added afterburner trails, radar icons, muzzle flashes, turret initial positioning & movement sounds & replaced rendered stars with the starfield skybox. Some of the models I imported were simple drop-in replacements, while others needed careful comparing between old & new models, and the table to make sure everything is as close as possible to the original. Some of the models are openly available, while others... I must admit, were extracted from Nostos or from what I have of my last version of R1 prior to my... drifting away.
-
So... that thing I was worried would happen... happened. After several plays on the Jan 4th build, it has suddenly refused to render ambient lighting. I managed to get one play on the next build (Jan 8th) but it lost lighting the next time I loaded up the build. The next one, Jan. 12th, gave me no lighting from the get-go, so I decided to load up the March 7th build again and noticed that I had a radar again. It would seem however, that this is due to my adding radar icons for every ship. It would appear that the default dots aren't rendered in this build. I also noted that grid lines in the briefing screen are missing, as well as subsystem targeting brackets in the target window aren't displayed, as well as the bank-identifier lines in the loadout screen. I also found that lighting is ONLY being rendered from suns. A ship will appear completely lit on the sun-side, but completely dark on the other. I'll try a few later builds and see if there are some other interesting differences.