Hard Light Productions Forums
Community Projects => The FreeSpace Upgrade Project => Topic started by: mjn.mixael on August 13, 2018, 02:12:42 pm
-
Discussion goes here.
-
Yay DL'ing. :)
-
Well, some small notes.
I thought the version scheme was changed from version numbers to years in 2014, because it is more independent from builds this way?
I actually dislike the inclusion of Voice Files in the general MVPs that replace retail ones and so replace voice files from another language release.
Such language specific files should be in a own optional VP, imo.
The inclusion of the 2_HUD can cause problems in the same way, too, because French and German FS2 has some different HUD gauges with own sizes and the Retail 2_ ones of them are actually not very good usuable by normal means, because there are several times larger than the english 2_ ones.
But apart from that, it was about time. Thank you for the effort :)
-
Well you could've said that before release?
Shouldn't cause any new problems at least. The HUD never displayed things such as Abschüsse properly anyway.
Also, if we're already at that, I tried to get INF (and MVPs) to run on Diaspora (making it standalone), but it always crashed on the briefing screen due to interface tiles shipped with them, so the experiments failed. Not that it would be any sort of relevant though.
-
Well you could've said that before release?
Shouldn't cause any new problems at least. The HUD never displayed things such as Abschüsse properly anyway.
Also, if we're already at that, I tried to get INF (and MVPs) to run on Diaspora (making it standalone), but it always crashed on the briefing screen due to interface tiles shipped with them, so the experiments failed. Not that it would be any sort of relevant though.
Well, at least the voice files are an old problem that was surely discussed in the MediaVP2014 years ago. So it is only a problem that is still present in the new version too... but well, i hoped that i do not have to write VP extracting manuals anymore, so that people are able to extract the german voice files to use them with MVPs :D
And for the HUD thing, actually it would not be a problem if they would includes the 2_ hud from the english sparky_hi from the CDs too. Because in my DVD version, it is not only the kill gauge that is larger, the Radar goes over half my screen in this one.
-
(UT2004 Voice) D-D-D-Downloaded!
Effort is much appreciated.
-
Something strange is happening...I ran 2 mods with the new MVP update and I see 2 HUDs stuck close together in the cockpit. It is very disorienting...is there a way to fix that?
Update: here is a screen of the issue. I ran this on knossos as well. Apologies for the quality, took it from my mobile. I have no clue which key it is to take screens in-game
[attachment stolen by Russian hackers]
-
Mods may need to update their HUD table to ensure compatibility depending on how they implemented their own HUD upgrades.
-
Mods may need to update their HUD table to ensure compatibility depending on how they implemented their own HUD upgrades.
I see. Thanks for that
-
I thought the version scheme was changed from version numbers to years in 2014, because it is more independent from builds this way?
I believe this was changed because mods uploaded to Knossos are supposed to use semantic versioning.
Update: here is a screen of the issue. I ran this on knossos as well. Apologies for the quality, took it from my mobile. I have no clue which key it is to take screens in-game
Print Screen and the screenshot is saved in %appdata%\HardLightProductions\FreeSpaceOpen\screenshots.
-
MediaVPs switched to the "year" name scheme for the same reasons that mods may currently be having HUD issues. FSU cannot be responsible for maintaining backwards compatibility with every mod ever. We upgrade the core FS2 experience by releasing a standardized modpack that mods can add as a dependency. I know Knossos has an "allow new versions" options for dependencies. Mods should not use this for the MediaVPs. Knossos makes it very easy for a mod released in 2015 to always work because Knossos always has MediaVPs 2014 (3.7.2) available. Knossos also makes it very, very easy for mods to update and distribute. Any mod author can increase the mod version, switch to MediaVPs 3.8 and check for issues. Then fix anything and release the update.
Additionally, users really shouldn't be forcing mods to run on a newer version of the MediaVPs that they aren't designed for. Even more so, users should not be editing Knossos installations for force unsupported dependencies for mods. This can cause other issues down the line. Give mods a few days/weeks to update and include the new MediaVPs. I know PIe and I own many of the older mods on Knossos. We'll do what we can to update them as necessary.
FSU has switched back to the semantic versioning system because that just makes sense with Knossos and, in general, Knossos discourages players from arbitrarily updating mod.inis (mod.jsons) to the new MediaVps and then posting when things go wrong. (This resolves the whole reason we switched naming schemes in the first place.)
-
My game crashes if a Leviathan shows up.
It is reproduceable if i look at it in the Tech Room, too.
WARNING: "Not all subsystems in model "leviathan.pof" have a record in ships.tbl. This can cause game to crash. List of subsystems not found from table is in log file.
Log file says this:
Subsystem 'armour01a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour02a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour03a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour04a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour05a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour06a' on ship leviathan.pof is not recognized as a common subsystem type
Subsystem 'armour07a' on ship leviathan.pof is not recognized as a common subsystem type
But even if i delete them from the mv_assets_t-shp.tbm the game still crashes.
Well i can not even load this one in POFCS2 :(
-
Leviathan as well: Several of the LOD-subsystems have subsystem properties as well, should be removed.
turret03-destroyed of LOD1 should be named turret03b-destroyed.
Is the mass correct? It's lower than that of a Poseidon.
No Cross Sections from retail (whatever they are used for).
-
Something strange is happening...I ran 2 mods with the new MVP update and I see 2 HUDs stuck close together in the cockpit. It is very disorienting...is there a way to fix that?
Update: here is a screen of the issue. I ran this on knossos as well. Apologies for the quality, took it from my mobile. I have no clue which key it is to take screens in-game
It's a problem that will affect every mod that uses Axems HUD. I think it's good that it is part of the MVPs now, for it enhances all mods (including those which aren't updated anymore), but those that have this feature built-in are now in need of a update.
-
Subsystem turret01b in model leviathan.pof was not found in ships.tbl!
Subsystem turret02b in model leviathan.pof was not found in ships.tbl!
Subsystem turret03b in model leviathan.pof was not found in ships.tbl!
Subsystem turret04b in model leviathan.pof was not found in ships.tbl!
Subsystem turret05b in model leviathan.pof was not found in ships.tbl!
Subsystem turret06b in model leviathan.pof was not found in ships.tbl!
Subsystem turret07b in model leviathan.pof was not found in ships.tbl!
Subsystem turret08b in model leviathan.pof was not found in ships.tbl!For Leviathan problematic are these subsystems.
In pcs clear properties for them.
-
Bah. Must've committed the wrong Levi data. I'll fix it this evening
-
Quote from the final post in the HTL Leviathan Release Thread (https://www.hard-light.net/forums/index.php?topic=92587.40).
Debug builds have been complaining to me about subsystems on the model not being in the table. At first I thought it had to do with the armour submodels, or a rogue subsystem entry in a arm or destroyed submodel. When I looked a little deeper, I found that the lod1 turret submodels have subsystem, fov, and name data. Is that supposed to be like that or is it an oversight?
[Edit]
That solved it. I can speculate that Lod1 was previously lod0 of the original file and retained the submodel info from the turrets. This should probably be fixed before the next MVP release.
-
I noticed few small things more.
Hippo has null MoI.
Nephilim still has offseted thruster.
Ptah has no Sensors subsystem but there is Communication_001 in the same place in model. Rename should fix this.
Isis -> detail1 -> Turret02b -> Turret01b-arm should be Turret02b-arm,
and in section Turrets - Turret01b should be deleted.
VAC5 has detail1 to 3 but they are not assigned in LOD.
Edjo has 4 lods but in table only 3 used.
-
Hippocrates is centered wrong. It also has a much higher mass than the retail one (unless the retail one was unbalanced). And it still has 3 damage tiles.
-
Hipoo have damage tiles is not a bug.
-
Hipoo have damage tiles is not a bug.
Correct. I only thought if it needs to be touched a little anyway, this could be reduced from 3 to 1 as well. :)
-
3.8.1 will be up tonight.
-
Thank you all for trying the MediaVPs 3.8 Early Access. We've just released a new version addressing your concerns.
-
Thank you all for trying the MediaVPs 3.8 Early Access. We've just released a new version addressing your concerns.
You just could've said that you needed testers! :D
-
Thank you, mjn.mixael, for hard work on releasing MediaVPS and quick update :yes:
btw
Is there any chance to include better radar icons from BirdofPrey (https://www.hard-light.net/forums/index.php?topic=89098.0)?
-
This should probably be highlighted.
-
It looks like outstanding work.
And yet, it is of course, missing that new HD Demon Destroyer model... ;)
Have the MediaVPs for FSPort been updated to include the new HD Apollo model? It wasn't the last time I looked a year ago.
-
Hi guys,
great work, thumbsup
One question: Assets alone or all assets are required?
-
Hi!
Unfortunately I don't know, where this belongs to (Knossos, HLP Mantis, elsewhere), but I think some optional files in mediavp 3.8.1 mod.json are written UPPER CASE, while they're lower case in 7z archive... And so, 7z downloads but fails to unpack:
WARNING:Thread-13:repo.query: Repo.query(): Expected Spec but got Version instead! (Version('3.8.1-20180814', partial=True))
INFO:Thread-4:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/ec/cc/0bf23e028c26d5175ff52d003bff85b0a17b0ddfc1130d65bdf6d36f6324.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/72/a5/316d08a743a35dc144284b9fb9a466ee259e0b22756cd2a032986951527e.png"...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
INFO:Thread-4:util.download: Downloading "https://fsnebula.org/storage/0d/e7/bf64bcdea9a9c115969cfb784e1ca457d24a7c2da4fc6f213521c3bb6abb.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.global.ssl.fastly.net/storage/20/cf/205ecefff5f8b9da7420d795b208d679207ee75917ebbfd74182eec0137e.png"...
INFO:Thread-3:util.download: Downloading "https://fsnebula.org/storage/78/dd/a5d1ae22742614e88cee2599f3684c0888e726d689c60748a534723144bd"...
INFO:Thread-7:util.download: Downloading "https://cf.fsnebula.org/storage/b4/02/12622e5cd8f061f5365cd0078c17c12a350a3a1b00280f4ba7321728fa87"...
INFO:Thread-9:util.download: Downloading "https://cf.fsnebula.org/storage/b8/da/e9e90a83825ab4108f991ff4db324a31ae235e071aa93d73964cec3a5ea7"...
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
INFO:Thread-1:util.download: Downloading "https://fsnebula.org/storage/be/56/2663c3b5a709104404a30ce7268c72332e564526708865123c7b63104357"...
WARNING:Thread-7:tasks.work2: Missing file "MV_Compatibility.vp" from archive "MV_Compatibility.7z" for package "MV_Compatibility" (MediaVPs)!
ERROR:Thread-7:tasks.work2: Failed to unpack archive "MV_Compatibility.7z" for package "MV_Compatibility" (MediaVPs)!
INFO:Thread-4:util.download: Downloading "https://fsnebula.org/storage/22/bc/7d8aae0b2ac245ae23722e4db39ba8e8444005a953b2ecfe78f372b59aaf"...
INFO:Thread-5:util.download: Downloading "https://cf.fsnebula.org/storage/48/44/5a4fd4ccbe90307c4fa8dcd5fee49a396965fddbf3dc1a129531e1843fa4"...
INFO:Thread-6:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/d1/ad/d1f801000b14927aee31fa3cdf444b8f2c9610fc36be158cc77efe086ad4"...
INFO:Thread-10:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/4f/a1/a715801439cbc66cb627b90adf169c07e412311c389e538e79ee5d05ecf4"...
WARNING:Thread-9:tasks.work2: Missing file "MV_Advanced.vp" from archive "MV_Advanced.7z" for package "MV_Advanced" (MediaVPs)!
ERROR:Thread-9:tasks.work2: Failed to unpack archive "MV_Advanced.7z" for package "MV_Advanced" (MediaVPs)!
INFO:Thread-8:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/e6/65/35092355da5b2e67ff7977633f2c743e6c809993f29c48916c77388056ec"...
INFO:Thread-2:util.download: Downloading "https://cf.fsnebula.org/storage/da/10/d33322f3dd57710383fe8684ed803d4ea16a5e54bfd0df1aa415dad37536"...
INFO:Thread-7:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/f0/d6/189e936752e4afffe910f4ff8aa90022fe5ff7b6309f4eb76834a7150c11"...
INFO:Thread-5:util.download: Downloading "https://cf.fsnebula.org/storage/c7/97/47a2d793044fe811e13b8cc243b426b64967d335f39f6e4a3ef21411e31e"...
WARNING:Thread-1:tasks.work2: Missing file "MV_CB_ANI_2.vp" from archive "MV_CB_ANI_2.7z" for package "MV_CB_ANI_2" (MediaVPs)!
ERROR:Thread-1:tasks.work2: Failed to unpack archive "MV_CB_ANI_2.7z" for package "MV_CB_ANI_2" (MediaVPs)!
INFO:Thread-4:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/da/c2/6b9ebd9f82334c523ef32dcb5aed7780d70374dd3df3d8739c17bccdc326"...
WARNING:Thread-5:tasks.work2: Missing file "MV_Assets.vp" from archive "MV_Assets.7z" for package "MV_Assets" (MediaVPs)!
ERROR:Thread-5:tasks.work2: Failed to unpack archive "MV_Assets.7z" for package "MV_Assets" (MediaVPs)!
INFO:Thread-3:util.download: Downloading "https://porphyrion.feralhosting.com/datacorder/nebula/93/04/c6c9f16680fc2d14a8e330bb907d9488d78bbf4640f7fbc4629248de6c39"...
INFO:Thread-9:util.download: Downloading "http://swc.fs2downloads.com/builds/nightly/20180814_1307636/nightly_20180814_1307636-builds-Linux.tar.gz"...
WARNING:Thread-7:tasks.work2: Missing file "MV_CB_ANI_1.vp" from archive "MV_CB_ANI_1.7z" for package "MV_CB_ANI_1" (MediaVPs)!
ERROR:Thread-7:tasks.work2: Failed to unpack archive "MV_CB_ANI_1.7z" for package "MV_CB_ANI_1" (MediaVPs)!
WARNING:Thread-2:tasks.work2: Missing file "MV_CB_ANI_3.vp" from archive "MV_CB_ANI_3.7z" for package "MV_CB_ANI_3" (MediaVPs)!
ERROR:Thread-2:tasks.work2: Failed to unpack archive "MV_CB_ANI_3.7z" for package "MV_CB_ANI_3" (MediaVPs)!
Oh, and where can I get help in bringing my "MOD" to work in Knossos (just a bunch of tables I want to load when selecting mod)? The mod shows up but it doesn't load anything...
-
That's a Knossos bug. Should be fixed in 0.12.3 which I'll release tomorrow.
Regarding the other problem: You can either post on the Knossos thread (https://www.hard-light.net/forums/index.php?topic=94068.0) or join us in #knossos on HLP's Discord (https://discord.gg/YNVP3WR).
Make sure you placed your files in the correct folder and if it still doesn't work, post a debug log either in the Knossos thread or on Discord.
-
I posted this on Discord already but having a better record of it here seems prudent. There's now a crash that I assume is related to the new Levi model with FSPort. I've only tried this with the tech room since I don't remember which missions feature it but when the tech room tries to load the model it crashes on the regular build. On the debug version it manages to load the old one.
Here's the debug log:
https://fsnebula.org/log/5b747ab1cb0d3306d3e3ff69 (https://fsnebula.org/log/5b747ab1cb0d3306d3e3ff69)
Again awesome job on this stuff so far!
Update: It only happens on the 3.8 nightly from 8/14
-
Just finished the FS2 campaign and have some issues.
(Using nightly 2018-08-14 SSE2 64-bit build)
1. In mission "Endgame", the Iceni stuck in front of the Knossos about 2-3mins. But I can't reproduce the situation.
https://www.youtube.com/watch?v=_0dmHRjsJJU (https://www.youtube.com/watch?v=_0dmHRjsJJU)
2. Sathanas's AAA beam can shoot through its hull.
3. No debriefing message in mission "Into the Lion's Den".
4. In mission "Exodus", "Destroy Gibborim Beams" can't be completed even the Gibborim destroyed.
And... great job SCP/FSU team.
[attachment stolen by Russian hackers]
-
I was already working on #1 and has to do with the High-Poly Colossus' wrong size.
#2; I think there's a table flag for that. I'll look into it. EDIT: On the other hand, changing this might affect retail balance...
#3 & #4, I can't fix without more info. Those are also mission (FREDing) bugs that were probably present in retail. I'm not sure what FSU's policy has been in the past on fixing those bugs.
-
I see. :)
About #2, I always played VE or Easy when I was kid.
I played Insane this time so maybe just my problem. :D
-
What I mean is that turrets on new high-poly ships get the same FOV and turn rates as the retail versions. If that causes hull clipping, then it's technically an issue with the design of the model and we just need to think through if effectively changing the turret's FOV will affect retail mission balance or not.
-
#2 could break not only the retail campaign (not sure about how precise :v-old: was about that), but also a ton of custom campaigns that were made/last updated before that flag was invented.
-
Can someone tell me if this is a 3.7.4. with more stuff (so additional ships/weapon effects etc...) or does it also include changes to tables/models/effects that were previously used?
-
The GVG Anuket is centered wrong. The "auto-centering" in PCS isn't 0,0,0 as usual.
-
Will be fixed in 3.8.2
-
First I want to say I REALLY REALLY appreciate this work you guys are doing! Do not feel like it's unappreciated. I'd be lavishing more praise but since I'm not a developer I don't really have much of substance to add.
But a question: Media VPs 3.6.12 still required the 2014 media VPs with the multimod tag in the mod.ini for some older assets. Is this still the case with this new release, or does this package include everything?
-
Uh, the 2014 release AKA 3.7.2 is newer than 3.6.12. I'm not sure what you mean by older models. In any case, you should only use one MediaVPs release at a time.
-
Amazing work. It's good to see the Hippocrates with a hi-poly model. The new Leviathan model looks good too.
The new planets also look really good.
Are there any plans to update the asteroid base model on the second mission of the FS2 campaign ?
-
The Boadicea has been started quite a while ago, but it's still missing textures and other things.
-
Mods may need to update their HUD table to ensure compatibility depending on how they implemented their own HUD upgrades.
What's the best way to do this?
Let's say I have a mod with its own custom hud_gauges.tbl, and I'm using the mediaVPs in my secondary mod list.
The mv_root-hdg.tbm gets parsed and all its HUD gauges are added on top of whatever is defined in hud_gauges.tbl, leading to a lot of duplicates.
One way around that I've found, is to add a $Ships entry to my hud_gauges.tbl, where I list all the flyable ships of my mod.
But is there a more "proper" way to override the mv_root-hdg.tbm ?
-
The other way is to include an empty mv_root-hdg.tbm in your mod.
-
The other way is to include an empty mv_root-hdg.tbm in your mod.
Ah yes, that's much simpler. Thanks :yes:
-
How does one go about incorporating these new assets into older campaigns? Is that feasible for an average FS2 modder?
-
I really wouldn't advise using MediaVPs 3.8.x with mods that haven't been updated by the author or someone who really knows what they are doing.
Is there a specific mod you are wanting to play with the new assets?
-
How does one go about incorporating these new assets into older campaigns? Is that feasible for an average FS2 modder?
That depends on what you want to do. According to the Changelog (in case it is complete), there shouldn't be something that breaks them compared to 2014 version. If you want to fix double HUD issues that could be here and there, you only have to remove the files for Axems HUD, what shouldn't be difficult either.
-
I really wouldn't advise using MediaVPs 3.8.x with mods that haven't been updated by the author or someone who really knows what they are doing.
Is there a specific mod you are wanting to play with the new assets?
It'd be nice to see how Freespace 2 Blue looks with the new assets, but I'm not in any rush.
-
Actually i have to ask, if this an oversight or is there a reason why the MVP 3.8.1 nebula.tbl got rid of the nbackblack entry?
I mean, orange nebula is also a nice color, pink would be even nicer as shown here <3
(https://abload.de/img/nbackpink4dcr1.png)
But i would still prefer to have the option of a black dark dust cloud like in Retail, too ;)
-
I didn't touch the nebula stuff in 3.8 as far as I know.
edit: confirmed. nebula.tbl hasn't been modified since 2013.
-
edit: confirmed. nebula.tbl hasn't been modified since 2013.
:lol:
Actually that is really funny. Then it seems that i played mods with their own nebula.tbl or it was still with the MediaVPs_3612 as i played a mission with such nebula. Not sure.
As i remember a black nebula i actually searched through the forums for hours... and then i stumped on the wiki entry, that it should be already part of the retail files... and it is :D
-
Try it with the latest nightly, apparently it was an issue with FSO and not the mediavps.
-
Just made an account to say the new update looks FANTASTIC! I absolutely love it.
-
Fantastic work guys, much appreciated! I thought Retail FS2 looked bloody amazing when I first played it back in 2000, but this is some next gen stuff right here :-) The new leviathan is superb, since it is no longer a re-skinned Fenris, and can now be easily identified from a distance. Perhaps doing likewise with the Cain / Lilith next? ;)
I'm getting the double hud bug on some mods. As such, I have a few questions about what to do about it. I suspect other players would also benefit from knowing this.
1 - Is there a completely noob friendly way to fix it, with an idiot proof step by step guide instructions for FRED virgins like me? ;-)
2 - In lieu of that, can the new VPs be added without the updated hud, if so how?
3 - Would uninstalling the new vps completely solve the problem for the time being?
4 - I have been told that each mod will need to be fixed individually by it's devs to make them compatible with the new VPs. Is there a list/thread etc showing which mods have been updated? If not, how would we go about creating one?
Many thanks in advance :-)
-
The problem is for mods that have their own custom hud elements in a table named something other than mv_root-hdg.tbm. In that case, the custom HUD gets loaded instead of the retail HUD and then the MVPs hud is added onto the custom HUD, resulting in double HUD gauges.
The fix is trivial but the bigger problem is that many mods which haven't received a proper MVPS 3.8 update are automatically set up to use the newest version of the MVPs. So even if it's easy to fix the HUD error you might run into some harder to fix errors later resulting from table-pof discrepancies or other MVPS 3.8 updates that the mod didn't account for.
If you're sure you want the manual fix anyway here's what you need to do. Create a new text file, leave it empty and rename it mv_root-hdg.tbm
BE EXACT. Then take that empty table and put it into a mod's data/tables folder. If you're on Knossos put it inside any package's data/tables folder but NOT the main data/tables folder. Actually, don't put anything in the "main" mod folder, ever. on Knossos. ALL of the stuff goes inside the individual package subfolders.
If data/tables doesn't exist just create new folders and rename them.
-
If you're sure you want the manual fix anyway here's what you need to do. Create a new text file, leave it empty and rename it mv_root-hdg.tbm
BE EXACT. Then take that empty table and put it into a mod's data/tables folder. If you're on Knossos put it inside any package's data/tables folder but NOT the main data/tables folder. Actually, don't put anything in the "main" mod folder, ever. on Knossos. ALL of the stuff goes inside the individual package subfolders.
If data/tables doesn't exist just create new folders and rename them.
For any mod developers who are reading this, the "empty" mv_root-hdg.tbm file can't really be empty. It needs at least a single space or something else that FSO won't interpret as game data. If you create a completely empty file, when packed into a VP file, it will be treated as a folder.
-
That really only applies if you're a dev since Knossos automatically packages .vps. For a 'personal' fix you can leave it as a loose file.
-
I just heard about the new MediaVP release and decided to install these new MediaVPs using the traditional Folder/mod.ini method instead of Knossos.
1) I performed a fresh installation of FreeSpace2 from my retail disks and then patched it to 1.02 using the Volition-provided patch. (I already have OpenAL installed)
2) I downloaded the MediaVPs_38x/mod.ini from the main page, placed it in my Freespace2 folder and then downloaded and unpacked the actual MediaVP .7z files into that MediaVPs_38x folder as per the instructions.
3) I downloaded and unpacked the FSO 3.8.0 x64 build with AVX support into my Freespace2 directory.
4) I installed the WCX Launcher 0.12.4 and pointed it to the FS2Open files I unpacked into my Freespace2 directory, and selected MediaVPs_38x as my mod.
Launching the game produces the following error:
Error: game_settings.tbl(line 2):
Error: Missing required token: [#END], Found [$Target.Version] instead.
File: parselo.cpp
Line: 290
This error occurred regardless of which Advanced Features were selected. To test the FreeSpace2 Open installation, I unpacked my prior MediaVPs_2014 folder and selected it as the current mod in the launcher, and the game started just fine using the older MediaVP pack. I don't believe this to be a hardware issue, but...
Running Hardware: AMD Ryzen 2700X (stock clock) on Asus Crosshair VI using UEFI 6201, 2x8G RAM @3200, AMD Radeon RX480 8G (stock clock)
Running Software: Windows 10 Pro 1803 x64 (all Windows Updates applied), OpenAL 2.07, AMD Adrenaline 18.8.2
-
IIRC you need a recent nightly (like this (https://www.hard-light.net/forums/index.php?topic=95066.0)) for the latest MVPs release.
-
Thanks, that did indeed fix it.
-
Is there a list anywhere of which mods have been updated to be compatible with the new VPs, and have had any 'Double Hud Bug' or similar issues fixed? If not, we should probably start one.
-
While doing that somebody should also keep in mind that not every mod has the most recent MVP version specified as dependency on Knossos.
INFN - had HUD issue, fixed by changing Knossos dependency (so no problem for now), team is informed.
BWO Demo - HUD issue, posted the info on the board.
Don't know about anything else.
-
While doing that somebody should also keep in mind that not every mod has the most recent MVP version specified as dependency on Knossos.
INFN - had HUD issue, fixed by changing Knossos dependency (so no problem for now), team is informed.
BWO Demo - HUD issue, posted the info on the board.
Don't know about anything else.
Exile has the dual hud bug too. Hopefully Nyc knows about it
-
Hi there!
I have gone through every FS mod currently publicly available on Knossos. There were a few that had errors on start, so I cannot vouch for them until I get them fixed, but for now, at the time of writing, the mods I found with the 'Double Hud Bug' are;
BWO Demo
Exile: Into Dark Waters
Inferno Nostos
Which is less than I thought it would be tbh :-)
NB - I have not yet tried out the Wing Commander and BSG mods.
-
I have compiled a spreadsheet showing this, and which mods are using the new VPs, which are using the 3.6.12 / 3.7.2 / 2014 era MPVs, and even the holdouts that are still using the retail FS2 graphics. I have attached it here in case it is of use to anyone. I'll update it when I get the broken mods working, when new mods are added and when existing ones are updated.
[attachment stolen by Russian hackers]
-
The authors of those mods will need to update them. That's outside of the scope of FSU's role.
-
I know, I'll get onto that tomorrow - it's 'late O'Clock' here atm ;) . I put it here for now for general interest.
-
The
Quiznos Knossos forum link for MediaVPs defaults to the 2014 thread instead of here.
-
Inferno Nostos
That's already been fixed. If you still have the problem, delete the mod.json file from Inferno-1.0.0 and redownload. Knossos will detect that all the other files are there and won't redownload them.
NB - I have not yet tried out the Wing Commander and BSG mods.
Considering they're TCs that don't use the MVPs, they won't have any problems.
-
Thanks for the advice. Unfortunately m going to have to ask a very noob question. "Where can I find the 'mod.json file' I need to delete"?
And thanks for the heads up about WC and BSG. A few less things to have to worry about :-)
-
Find the data folder you chose for Knossos (by default it's C:\Games\FreespaceOpen) and go to FS2\Inferno-1.0.0.
-
Worked like a charm, thank you :)
-
I decided to try this with the campaign "FS2 Blue." I changed the mod.ini of that campaign from "MediaVPs_2014" to "MediaVPs_38X."
So far I haven't found any gamebreaking errors. However, I have a minor question: was there a change in the Command Briefing picture with Bosch in it? It now no longer says "Not blaming Axem".
-
No change that I'm aware of. Check with MVPs 38X and not FSBlue. If it's the right anim there, then FSBlue may have done something.
-
Minor bug report:
-The SSG Rahu has turret03 and backb as LOD1 and LOD2; debris-backa00 and debris-backa01 would AFAIK have to be part of the debris LOD to work as live debris. Also I'm not sure whether all paths properly link to subsystem - in particular turret01 and 02 are named differently.
-I noticed that mv_assets_s-shp.tbm tries to add several missile turrets as primary turrets ($Default PBanks: ( "Piranha#Shivan" )). Viewing the tbl entry, it appears that this bug was already carried over from retail. The turrets instead all contain various primary weapons. :confused:
-
You beautiful bastards! you did it again! thanks a bunch!
:v:
-
There appears to be a problem with the Leviathan model. The table included is for the new one, but the VP file contains the older model that is just the re-textured Fenris model with the added armor panels. The table references some other armor panels on the new model and the maneuvering thrusters. Now I just checked the latest downloadable version of the terran assets vp file, and confirmed that the problem exists in that version. Since I don't use Knossos, I can't confirm if its been fixed there or not. If yes, than I'd advise someone to update the separate download.
-
If yes, than I'd advise someone to update the separate download.
Even if you don't use the program, you can simply go to the Knossos website and redownload the file in question (assets_t).
-
I DID, and confirmed that the Leviathan in that pack is NOT the new one, though the table file is expecting it.
-
My bad; but the files Knossos provides are identical to those in the separate downloads.
-
I do not see this issue here. Please post a debug log after loading the Leviathan in the F3 Lab.
-
-Rahu related things
-I noticed that mv_assets_s-shp.tbm tries to add several missile turrets as primary turrets ($Default PBanks: ( "Piranha#Shivan" )). Viewing the tbl entry, it appears that this bug was already carried over from retail. The turrets instead all contain various primary weapons.
Forgot to mention that this only affects the Sathanas. :banghead:
-
I figured it out. The new Leviathan IS in there, but so is the Fenris-based one. The new one is named leviathan.pof, while the older one is cruiser01x.pof. SAH was looking for new one as cruiser01x.pof, and the submodel subsystem references for the new one were in the tables expecting it to be cruiser01x.pof. So, it turns out that its more SAH's fault than MVP3.8. I'm not sure if retaining the older Fenris-based model in the 3.8 MVPs was an oversight or just for backwards compatibility.
Sorry.
-
Okay hold up hold up. I know this is kind of a dick complaint, but I really liked the '[year] MVPS' format for MVP names, I think it was much easier for users to understand. Are these officially and forever the 3.8 MVPs, or can we do 2018 MVPs?
The reason I ask is a reddit user trying to figure out whether '3.8' or '2014' is newer.
-
I think part of it is that Knossos needs version numbers, which led to the 2014 mediavps needing to get redesignated as 3.7.2 for Knossos, hence the return. Maybe we could do something like 2018 MediaVps 3.8, since version numbers only ever go up.
-
Which kind of version numbers does Knossos support? Or is it impossible to name them 2018.1, 2018.2 and so on?
-
I don't really care that much about 2018 vs. 3.8.x except that it be consistent. When I first started playing FS, I was confused whether 3.6.12 or 2014 was newer. As long as the version numbers are comparable, it's pretty easy to figure out that higher is better/newer. If I had to pick, I'd pick the 3.8.x scheme because it's already compatible with semantic versioning, which has some nice advantages like letting you know at a glance how major of an update a new version is.
You could rename the MVPs 2018.1.0, 2018.2.0, etc. in Knossos, but that would just confuse everyone who already has it figured out.
Honestly, if you're just using Knossos, which everyone who can't figure this out should be, it's not a problem. If you want to play FS2 with upgraded visuals, you just install the MVPs and Knossos will give you the latest ones automatically. If a certain mod requires an older version, Knossos should pretty much take care of that seamlessly.
-
Okay hold up hold up. I know this is kind of a dick complaint, but I really liked the '[year] MVPS' format for MVP names, I think it was much easier for users to understand. Are these officially and forever the 3.8 MVPs, or can we do 2018 MVPs?
The reason I ask is a reddit user trying to figure out whether '3.8' or '2014' is newer.
Which kind of version numbers does Knossos support? Or is it impossible to name them 2018.1, 2018.2 and so on?
Oh heck, can we just do 2018_3.8? Year, version, done. Knossos can either ignore the year or use it; shouldn't matter.
-
And what if patch 3 is released in 2019? It would be called 2019_3.8.3 then, what would be confusing as hell IMO. Maybe create a voting/discussion thread whether 2018.2 or 3.8.2?
Plus this:
Honestly, if you're just using Knossos, which everyone who can't figure this out should be, it's not a problem. If you want to play FS2 with upgraded visuals, you just install the MVPs and Knossos will give you the latest ones automatically. If a certain mod requires an older version, Knossos should pretty much take care of that seamlessly.
-
This is something that may confuse newbies if they are trying out older mods, so this probably needs sorting. Going forward it will be less of an issue since almost all new mods / updated mods will use 3.8.X or later. That will make it easier after that since everyone will be on the numbering scheme.
A very simple work-around is to simply create a list showing the order they were created and put it somewhere very easily accessible - perhaps as text in knossos itself or in the upcoming noob's guide. This should also point out that Knossos will use the most up-to-date MVP a particular campaign/mod is compatible with, and that trying to force a mod to use more recent MVPs than it was designed for may cause glitches/crashes etc.
"MVP order, oldest first.
Retail FS2
3.6.10
3.6.12
3.7.2 (Also known as MVPs 2014
3.8.X"
The list can then be updates when new MVPs are created. Easy peasy :-)
-
MJN stated that he wanted to update more frequently, so I'm afraid the list would be confusingly long at some point. Currently out are 3.8.0, 3.8.1 and 3.8.2.
Question: are the files for all previous sub-versions (3.8.0 and 3.8.1) archieved/available on Knossos or are only the main revisons backwards compatible?
-
This is something that may confuse newbies if they are trying out older mods, so this probably needs sorting. Going forward it will be less of an issue since almost all new mods / updated mods will use 3.8.X or later. That will make it easier after that since everyone will be on the numbering scheme.
Why? I can't state this strongly enough; Knossos takes care of this. There is no reason to mention version numbers to a newbie except when debugging, which is a completely different scenario. Just tell people to install Knossos and download the MVPs. Knossos will work its magic in the background to ensure they're using the correct version.
A very simple work-around is to simply create a list showing the order they were created and put it somewhere very easily accessible - perhaps as text in knossos itself or in the upcoming noob's guide. This should also point out that Knossos will use the most up-to-date MVP a particular campaign/mod is compatible with, and that trying to force a mod to use more recent MVPs than it was designed for may cause glitches/crashes etc.
Again, no reason to even bring up the possibility that you can force using a different version or that some mods use different versions.
Question: are the files for all previous sub-versions (3.8.0 and 3.8.1) archieved/available on Knossos
https://fsnebula.org/mod/<mod_id>/x.x.x. For example, https://fsnebula.org/mod/MVPS/3.7.2. Unless the mod dev deletes the previous version(s), they remain publicly available.
-
Ahahaha the irony. When we used MediaVPs 2014 instead of the old versioning there was a similar backlash. Ya'll are impossible.
We're sticking with the current versioning. 3.8.x is essentially the same, save for bugfixes.
Changes to the last number is effectively the same as patches the older versions used to do. They just never increased a minor version number which is now required for knossos. Backwards compatibility should be unaffected by these minor updates.
Additionally, players using knossos shouldn't be having an "is 2014 newer or older" problem. Players not using knossos should read the release thread in full because it includes links to all older versions. The linked release thread for 3.7.2/2014 explains the rebrand in big bold red letters. If people are getting downloads and/or information outside of these 2 locations, it's out of my control and whoever is making those Reddit posts or whatever need to do it right.
-
Apparently the problem was that he was using the FSO Installer which lists the 2014 MVPs and the 3.8.2 MVPs without explaining which is newer. I'll send Goober a PM to change the label to 3.7.2.
-
The backlash to the 2014 MVPs was over versioning them at all, which is a lot less of a problem with Knossos/a working installer.
-
The backlash to the 2014 MVPs was over versioning them at all, which is a lot less of a problem with Knossos/a working installer.
Lol wut
We had 3.6.9zeta, 3.6.10, 3.6.12, and it was finally in 2014 that people had a problem with versions?
-
Oh. Er, whenever we started doing versions, that's when people got mad. Look, I don't know, just make the numbers get bigger.
-
Release Version 86 already :nervous:
Anyway, downloading an updated copy today and trying it out.
-
I've managed to find some Normal maps for retail textures which are missing in the current MVP; most of them were once part of the INF modpack. Also included are the high-res Navbouy-maps that were part of the retail map set but aren't present at all in the current MVPs. I think there are a couple mods using/could use them, not entirely sure though.
Also I've noticed that the Hippocrates maps are present as DDS and PNGs, the PNG ones can probably be deleted.
Edit: Forgot the glowmap for Navbouy2
[attachment stolen by Russian hackers]
-
Cool, well done. Will these be incorporated into the next MVP release?
-
I've been reinstalling FS_Open using Knossos (my old folder was a mess) but MV_Music and MV_RadarIcons don't pass the integrity verification and I've re-donwloaded them multiple times.
-
That might be partially my fault. It's a Knossos / Nebula bug. Your mod installation is fine. I'll hopefully be able to resolve this (and a bunch of similar issues) during the next few weeks.
-
Hi, I have a question: I've just installed Knossos on a fresh PC, installed FS2 from GOG package and downloaded MediaVPs 3.8 as shown here: (all downloaded without any errors)
https://www.dropbox.com/s/meaaunqpif8qluv/Screenshot%202019-02-21%2022.33.38.png?raw=1
The problem is when I play FS2 using this version i have some bugs like: (I only played the 1st mission, skipping training)
- some ships not showing (Deimos for example - only it's engines are visible
- the display on the bottom left showing targeted ship not displaying anything no matter what I target
- no warpout animation
and maybe more...
I've downloaded another campaign (Aeos Affair) which uses MediaVPs 2014 and with it everything looks okay.
-
Please post your fs2_open.log file. Instructions on how to do this can be found in this post.
I'm going to guess that it's due to the fact that the newer MediaVPs require nightlies which still have bugs on AMD cards.
-
Hi, there's an error when I click on upload log in Knossos, something about my interenet connection, weird...
Anyway I uploaded it here: https://my.mixtape.moe/rngsjj.log
I have AMD GPU indeed