Paper Cutting - Pattern not showing up
Describe the bug
The pattern that's supposed to be crafted on page one, isn't supposed to result in a blank paper on the finalised "unfolding" screen:
Expected behavior
n/a
Content Location
https://ooooooooo.ooo/static/?81c96162-fc99-49b4-96db-54714e4f3c13
Affected platform
Browser's extension
Operating system
SteamOS Beta latest (Arch Linux)
Browser
Mozilla Firefox 128
Additional information
Player Info
Allows script access: true Renderer: wgpu Adapter Backend: Gl Adapter Name: "Radeon HD 3200 Graphics, or similar" Adapter Device Type: IntegratedGpu Adapter Driver Name: "WebGL" Adapter Driver Info: "2.0" Enabled features: Features(TEXTURE_COMPRESSION_BC | FLOAT32_FILTERABLE | TEXTURE_ADAPTER_SPECIFIC_FORMAT_FEATURES | SHADER_UNUSED_VERTEX_OUTPUT) Available features: Features(DEPTH32FLOAT_STENCIL8 | TEXTURE_COMPRESSION_ETC2 | TEXTURE_COMPRESSION_ASTC | PUSH_CONSTANTS | CLEAR_TEXTURE) Current limits: Limits { max_texture_dimension_1d: 16384, max_texture_dimension_2d: 16384, max_texture_dimension_3d: 8192, max_texture_array_layers: 256, max_bind_groups: 4, max_bindings_per_bind_group: 1000, max_dynamic_uniform_buffers_per_pipeline_layout: 8, max_dynamic_storage_buffers_per_pipeline_layout: 0, max_sampled_textures_per_shader_stage: 16, max_samplers_per_shader_stage: 16, max_storage_buffers_per_shader_stage: 0, max_storage_textures_per_shader_stage: 0, max_uniform_buffers_per_shader_stage: 11, max_uniform_buffer_binding_size: 2130706432, max_storage_buffer_binding_size: 0, max_vertex_buffers: 8, max_buffer_size: 268435456, max_vertex_attributes: 16, max_vertex_buffer_array_stride: 255, min_uniform_buffer_offset_alignment: 32, min_storage_buffer_offset_alignment: 256, max_inter_stage_shader_components: 128, max_color_attachments: 8, max_color_attachment_bytes_per_sample: 32, max_compute_workgroup_storage_size: 0, max_compute_invocations_per_workgroup: 0, max_compute_workgroup_size_x: 0, max_compute_workgroup_size_y: 0, max_compute_workgroup_size_z: 0, max_compute_workgroups_per_dimension: 0, min_subgroup_size: 0, max_subgroup_size: 0, max_push_constant_size: 0, max_non_sampler_bindings: 1000000 } Surface quality: high Surface samples: 4 Surface size: (550, 400, 1)
Page Info
Page URL: https://ooooooooo.ooo/static/?81c96162-fc99-49b4-96db-54714e4f3c13 SWF URL: http://img-hws.y8.com/cloud/y8-flash-game/contents/item_versions/flash_games/6823/original/paper_cutting.swf
Browser Info
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 Platform: Linux x86_64 Has touch support: false
Ruffle Info
Version: 0.1.0 Name: nightly 2024-07-28 Channel: nightly Built: 2024-07-28T00:05:45.885Z Commit: 2ac4e7e62d911da59db109704239b8be28ed5da1 Is extension: false
Metadata
width: 550 height: 460 frameRate: 30 numFrames: 2 swfVersion: 9 backgroundColor: #FFFFFF isActionScript3: true uncompressedLength: 1792131
This doesn't log any relevant stub errors
Even the print button does not work properly on the fold-out screen.
It just produces a render of the page on the bottom right, let's you press it a bunch of times until it's invisible partially, and doesn't even pop out a "Print to PDF" option.
3 months later Can confirm it's still prevalent
Another important detail is the preview thumbnail whenever the screen transitions in-between.
This one's how it's supposed to look in Flash 32:
This one's taken in the latest Ruffle:
Notice that the Ruffle version lacks drop shadows, and the highlight white stroke bars, in the transition screenshot while the Flash version does not.
Neither version lacks shadows, or the white stroke, on the regular screen. Here's a screenshot in ruffle before I clicked on Start Game:
UPDATE:
Latest version/nightly finally fixed it.
Albeit there's still 3 issues related to the comment above.
The drop-down shadows are still missing, and clicking the print button just makes it stutter for a second before nothing happens.
Could Ruffle possibly have the option to communicate with your printer in order to, well... print things out?
Closing since the original issue was fixed. See #21565 for the drop shadow issue