nbohr1more

@STRUNK I think I missed a previous question in this thread. When making normal maps for TDM, the supported formats are uncompressed TGA or BC5 DDS. ( in case you are automating this )

Please post your Darkmod.cfg

I guess if these are mission specific textures, you could use material keywords to do the inversions: { blend bumpmap map scale( invertColor( /path/to/bumpmap ), 1, 1, 0, 1) } invertcolor does all RGB, the scale reverts blue

@STRUNK Try this: Inverted the red and green channels in GIMP

The AI tools render inverted red channels. So you often have to invert both red and green to get the right results. I think Materialize can be configured to make normals with the correct color output. Post a few problem normal images and I can identify the broken inversions (etc).

Yep, I've tinkered with Materialize. I mostly understand it's weird parameters but man it was a bear getting started. See also: https://wiki.thedarkmod.com/index.php?title=Creating_textures_from_Ornate_Photos

Courtesy of Bikerdude, Winter Harvest has returned to the mission database with bug-fixes, improved textures, improved lighting and EFX Reverb. Datiswous also added subtitles!

Please feel free to review any mission with translations. We will try to fix any issues found

Yep. Skybox was at fault. No need for the bottle cm. ( was just a guess about what could be different )

Fix confirmed! Thank you!

@Amadeus can you find or create a suitable collision mesh for the potion bottle and add: "clipmodel" "models/darkmod/path/to/clipmodel" // etc etc to the slowfall_potion def?

Crashes during mission loading while trying to generate entities.

Woo! We are now in the Moddb Top 100! Please vote again!

Looks like something is causing the collision code to go nuts trying to finish the polygonal windings? @stgatilov

Maybe the gravity value is going out of range when set negative? I'll test out with gdb tonight. Which mission is impacted?

Some sort of buffer overflow. Are you using any parameters that reference "long" floats? Are all your variables lower case or case matched ? ( Linux is case sensitive )

@Anderson do you still rely on image_downsize settings to make TDM playable? Do any other players use image_downsize so they can load larger missions on their older \ weaker GPU's?

This is a CYA thing. We tell them that we don't permit this stuff and if they hide it somewhere in a sub-folder of the pack then we accidentally distribute it we have our TOS setup to ensure we have plausible deniability. Perhaps @demagogue can speak to whether such a thing would keep us out of hot water ( DMCA, etc)?

I think of translations as an accessibility feature. We should be able to offer them just as projects like the Dolphin emulator do. We now use a system that ensures that the original mission is distinct from the translation so it should be no different than if someone posted a translation pack to moddb or any other social media site. I am not really gung-ho about this topic but ( on the other hand ) I just rescued over 40 translation packs from obscurity to be included in the mission database. Lots of people worked very hard on those and it felt wrong to let them go to waste. The map file does need to be changed but the changed map file exists inside the language pack override pk4. Thus the original mission is not altered at all. Yes we should probably specify that translation packs must contain at least objectives and readables. This is a widely discussed feature. The current mission database must increment by 1 integer every time you want to notify players that the mission has been updated. This leads to mission versions that are very high when authors keep fixing things and want those fixes to be known. I think we will make this more sensible someday ( maybe add a public_version attribute to the mission xml in the database so that the integer changes are invisible ? ) . Do we really need to force mission authors to explain what they fixed or changed? It's a good thing if they do so but I'm not sure about making authors admit to embarrassing mistakes they made and then secretly fixed? The readme file is where that data should be added though.

The rule would mostly just keep us out of the political sphere. That said, it also has the side benefit of being an easy excuse to reject any missions that are overtly racist for the purpose of astro-turfing or trolling. Of course authors can create missions that contain characters that reflect the historical racism, sexism, etc of the 16th century.

Quoted for truth

This only impacts database side updates. Would be cool if we did zipsync stuff to missions too. @stgatilov ?

Now that we have a rather large mission database, it's probably a good idea to spell out some rules and iron out some details. Once this is agreed on, we can update this wiki with the results: https://wiki.thedarkmod.com/index.php?title=How_to_pack_your_Mission Missions eligible for hosting in the mission database: 1) No malware or malicious data 2) No illegal content ( CSAM or Exploitive Images, Classified documents, PII or doxxing details, revenge porn, pirated game ISO's, PDF of commercially published books, login credentials to bank accounts, etc.) If it's illegal to distribute the file or information then it doesn't belong in your mission package. 3) No intellectual property or assets owned by Embracer Group ( the current owners of the Thief Series Games ) 4) No unauthorized commercial game assets 5) No unauthorized commercial music 6) Missions must start and must be possible to complete 7) Missions that are poorly optimized and are unplayable for 90% of players may be rejected 8 ) Missions intentionally designed to give players a bad TDM experience ( trolling, etc) may be rejected 9) Missions designed to promote Racism, Sexism, Homophobia, or other inflammatory viewpoints may be rejected 10) Missions that are very low quality ( broken visuals, broken audio, filled with navigation bugs for the AI or player, broken readables, etc) may be rejected Possible controversial TOS options: In the past, it was mooted that the TDM Team would have the executive authority to add language translations to missions but that was met with understandable push-back. The main problem was that these translations required the map files and other assets in the mission to be altered rather than existing independently. The new "system" for language packs leaves the mission along and instead uses an override pk4 to display translations so users can always access the original un-translated mission. A secondary problem with the old system was that the translator may misinterpret the details of story and thus relay the wrong meaning to non-English speakers. Since the language pack is kept separate, any translation issues can be easily attributed to the translator rather than the mission author and the author can clearly state that they had no involvement with the translation so they bear no responsibility for it's shortcomings. With that situation in mind, I am proposing the following TOS additions: 1) If not supplied, the TDM Team can create screen-shots for the mission database at 800x600 resolution ( the resolution compatible with our GUI's) ( we already do this so it's not very controversial ) 2) Missions without an animated or customized loading screen will be given the default loading page GUI by the TDM Team so that players won't think TDM has crashed \ froze when they are awaiting a mission to load 2) Subtitles can be added to missions with cut-scenes or videos by the TDM Team 4) Language packs can be added to the mission database by the TDM Team Please let me know your thoughts, objections, etc and we will solidify whatever is most agreeable to mission authors and team members. Regarding Mission Updates: The new mission database uses an SVN system so that we have the ability to do SVN rollback if anything gets broken during an update. With this change, missions are now stored unpacked so we can update them in granular fashion. Rather than providing the full mission package, please provide only the changed files in a zip archive along with a list of any files you removed ( if any ). If you are unsure what you added or removed simply provide the full package and we will compare and update it.

Yes, but I think png and jpg require a material def that can then be referenced by the GUI keyword for images via the material path