![]() tools searches for installed Giants editors in giantsPackageRegistry xml located in appdata/local.problem: editor installation can not be found.solution: run in cmd (see instructions below) with argument -g to manually set the path.reason: tools checks default install location and reads location from registry, make sure you didn't move the game after installation.problem: game installation can not be found.Module ShaderCheckEditor: warn if custom shaders are present in the mod nullifying console compatibility, raise errors if material configurations are used which are not available in the shader cache.Module EditorCheck: load all i3d files contained in the mod and check for errors.Module ObsoleteFiles: list obsolete source files not loaded by the game, list possibly unused textures, list duplicate files.Module SlotCheck: calculate estimated number of used slots for each store item as a reference for the modder.Module VehicleCheck: ensure specific vehicle xml elements are present (e.g.Module ModDescCheck: check a set of ModHub guidelines (descVersion, version number format, changelog, localization.Module I3DCheck: check reference integrity, obsolete lights/cameras, textureArray usage.Module TextureCheck: ensure textures have a resolution of 2^n.Module MipMapCheck: ensure textures for 3D objects have MipMaps, warn if texture has too low resolution.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" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |