Problem with new HLSLccExporter
See original GitHub issueImport: System.Exception: Unexpected program type DX9VertexSM30 bei DXShaderRestorer.ShaderGpuProgramTypeExtensions.GetMajorDXVersion(ShaderGpuProgramType _this) bei DXShaderRestorer.ResourceChunk..ctor(ShaderSubProgram shaderSubprogram) bei DXShaderRestorer.DXShaderProgramRestorer.GetResourceChunk(ShaderSubProgram shaderSubprogram) bei DXShaderRestorer.DXShaderProgramRestorer.RestoreProgramData(Version version, GPUPlatform graphicApi, ShaderSubProgram shaderSubProgram) bei uTinyRipperGUI.Exporters.ShaderHLSLccExporter.Export(ShaderWriter writer, ShaderSubProgram& subProgram) bei uTinyRipper.Classes.Shaders.ShaderSubProgram.Export(ShaderWriter writer, ShaderType type) bei uTinyRipper.Classes.Shaders.SerializedSubProgram.Export(ShaderWriter writer, ShaderSubProgramBlob blob, ShaderType type, Boolean isTier) bei uTinyRipper.Classes.Shaders.SerializedProgram.Export(ShaderWriter writer, ShaderType type) bei uTinyRipper.Classes.Shaders.SerializedPass.Export(ShaderWriter writer) bei uTinyRipper.Classes.Shaders.SerializedSubShader.Export(ShaderWriter writer) bei uTinyRipper.Classes.Shaders.SerializedShader.Export(ShaderWriter writer) bei uTinyRipper.Classes.Shader.ExportBinary(IExportContainer container, Stream stream, Func3 exporterInstantiator) bei uTinyRipperGUI.Exporters.ShaderAssetExporter.Export(IExportContainer container, Object asset, String path) bei uTinyRipper.AssetExporters.AssetExportCollection.Export(ProjectAssetContainer container, String dirPath) bei uTinyRipper.AssetExporters.ProjectExporter.Export(String path, FileCollection fileCollection, IEnumerable1 assets, ExportOptions options) bei uTinyRipper.GameStructure.Export(String exportPath, Func2 filter) bei uTinyRipperGUI.MainWindow.ExportFiles(Object data)
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top GitHub Comments
I have that game, no need to upload the asset for that one.
I think HLSHcc doesn’t support DX9. I set old exporter for this shader type in b5e19357b454aff2685fc4e48f6291e765701744. Waiting for @spacehamster to clarify this moment.