Jump to content
COMBATSIM Forum

Krycztij

Members
  • Content Count

    1,706
  • Joined

  • Last visited

  • Days Won

    2

Krycztij last won the day on February 5 2018

Krycztij had the most liked content!

Community Reputation

3 Neutral

About Krycztij

  • Rank
    Brig. General
  • Birthday 09/05/1981

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I see … If until now you just maintained a single transformation matrix which you overwrote when a transformation opcode occurred, you now need to maintain a stack. Push the new transformation onto the stack before you jump to the sub, and pop it when you return. IIRC, the Osprey was a good reference to check whether you got the transformation right … … and if this turns out to be too complicated, just stuff it all into a single object and we’ll add the VRML rotation node manually after looking at the bytecode
  2. Mike, it just occurred to me: No matter what we use for terrain, it won’t cover the cockpit. Having a reliable cockpit model would be a great benefit for all terrain modifications. Could you try to convert TAW’s cockpit?
  3. I know, that’s why I still haven’t gotten to port TFXplorer to Vulkan. Mike, it’s okay. I’ll just put my current TFX renderer behind a wrapper and we only use VRML & Co. for new terrain.
  4. Indeed, that’s a problem … I don’t have a solution right here in my sleeve; need to think about it first
  5. I found this in Supershape::preparePartlyCulledRasterization(): Each shape’s priority, in turn … bool tryToLoadShape():
  6. I can understand that quite well. AFAIK TAW’s plane coordinate system is also different (X is forward or something like that). Lean Viewer should be perfectly fine with STL, but STL does not support texture coordinates (not even vertex colors) – so it’s probably useless
  7. Too late, here it is http://krishty.com/2019-04-19 Lean Viewer.zip Two interesting points in the changelog: now falling back to software rendering (slow) if the GPU is too old If there is no hardware support, it falls back to Windows’ software rasterizer automatically. This means that you can use it on embedded Windows 7 systems without GPUs, or in old virtual machines (and the quality cannot be distinguished from the original). I doubt that Wine has already replicated the software rasterizer component, though. fixed folder navigation after drag and drop The left/right arrow keys didn’t work after drag & drop, never did. But they do now. This *could* in some way be affecting you.
  8. I don’t know debugging specifics of Wine, but this bit is quite interesting already. This is the flag for BGRA color format. Windows always used BGRA until they introduced D3D 10 with Vista and switched to RGBA. Then they noticed how bad RGBA performs on mobile devices and rebuilt the whole infrastructure to default to BGRA again with D3D 11 and Windows 7. Seems like Wine doesn’t like that. But I doubt it has to do with your problems. This should be DXGI_USAGE_BACK_BUFFER then, which I only use for the swap chain, and indeed the documentation says: … so this just simplified my code a very little bit But nothing to do with performance problems. This is the centroid interpolation mode which improves quality with antialiased rendering. It could well have to do with the bright lines around textured polygons. But this is a perfectly legal thing which improves the graphics on Windows quite a bit, so I won’t disable it for Wine. Again, nothing to do with performance problems. I guess I’ll just give you a new build but I did some clever things to improve rendering of scenes with thousands of objects and now I fear it’ll only run worse on Wine
  9. That’s pretty bad. Is there any chance to get debug output from Wine? (I notice on the screenshot above that the antialiasing looks wrong, too. Pretty discomforting.)
  10. I may be wrong here, but the scene at 6:40 looks like a glimpse at DID’s uncompleted Red Sea level, possibly from a level editor:
  11. … people without 3D vision ready hw can just rename the files to .JPG, open them on a widescreen monitor, and try crossing their eyes :-)
  12. Thank you! I have just as many snapshots from TFXplorer development to come, but it’ll take a while to sort and comment on them …
  13. It appears like file hosters deleted my 3View uploads (again) and image hosters deleted the screenshots (again) and one of the forum upgrades messed up some of my posts (again) … so I decided to host a dedicated website for 3View: http://krishty.com/taw/3view_en All my screenshots are uploaded and explained there, so you can scroll through the gallery for some TAW modding nostalgia.
  14. It’s probably these instructions in the model files: There’s also semi-transparent versions 003E and 007E for smoke effects.
×
×
  • Create New...