Module DXTCheck: ensure dds files use correct DXT formats, suggest conversion to DXT1 where possible.xml-file well-formedness (only required by the game to a certain extent, but should be fulfilled nonetheless).In the following the individual modules and their test cases are explained in detail instruction on how to correct errors are colored green.the generated html file will be automatically opened in your browser where you can check if errors were found in your mod.the xml contains all errors and more detailed (meta)information.html file only contains all the found errors (per module).files are named after the directory name of the tested mod and contain the result of the test.a xml and html file will be generated in the same directory as the TestRunner.when the test process has finished, the message "Finished execution" will be displayed inside the command line.note: depending on the size of the mod and the speed of the hard drive the process may take several minutes.GIANTS Editor will be automatically opened and closed during the process.Unless there is a "critical" message, this can be ignored the command line will display some information on the current progress.if requirements are met the tool will start to analyze the mod.if something went wrong an error message is displayed giving details on the problemĪll outputs are also saved in the "TestRunner.log".a command-line window will open displaying current progress.note: folder of the mod does not have to be in the same directory as the TestRunner.drag and drop the directory of an unzipped mod onto TestRunner_public.exe.Ideally use the "TestRunner" project on our public Bugtracker for reporting any bugs When making a bugreport please include testrunner log, the result files (xml and html) and if possible the mod itself (or its id on the ModHub), so we can reproduce the issue please report any cases where you think the tool outputs errors which are false positives.Particularly "unused files" reported by module "ObsoleteFiles" the tool is still in beta status, some tests might show errors which are none (so called "false positives").latest version of the Farming Simulator 22 TestRunner (0.8.8).=> the path to game installation needs to be correctly set within the editor all found problems will be provided in form of an HTML document and and xml file.and much more, for detailed explanations see "Test Cases" section.provide information about shader problems, which need fixing for a console release.show duplicate files (within the mod and in the base game).warn about wrongly exported dds textures.check if the descVersion matches current patch level.Key Features / What it does (selected examples) improve performance and minimize overall mod file-size and memory usage.detect various errors and provide hints how to fix them.speed up the process of testing mods by helping the modder to identify and fix problems (before submitting to ModHub).tool is also used by our QA internally (with an extended feature-set).tests are structured in multiple modules/groups.provides test result as html and xml document. checks a mod and shows various errors and violations of ModHub guidelines.Tool for testing Farming Simulator 22 ModsĪs with FS19 we are happy to provide our Mod Testing Tool updated for FS22.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |