Commit graph

146 commits

Author SHA1 Message Date
Ian Curtis bb3c538808 remove debug code 2017-06-20 19:46:06 +00:00
Ian Curtis 260daa1b91 Fix the fix shading in star wars. Fixed shading still needs some work for mag truck and dirt devils to match the arcade. 2017-06-17 16:05:54 +00:00
Ian Curtis 73a7d2760d cosmetic 2017-06-07 23:16:22 +00:00
Ian Curtis 1193069709 Tweak scroll fog logic again .. should fix missing 2d fogging in Spikeout. 2017-06-07 23:14:01 +00:00
Ian Curtis 45741b24d2 rewrite scroll fog logic 2017-05-06 16:47:31 +00:00
Ian Curtis 80004b0dad Remove debug code 2017-04-25 00:31:39 +00:00
Ian Curtis 7694e4eb0c minor culling node optimisations 2017-04-25 00:10:55 +00:00
Ian Curtis ff936c588b don't need cast, conversion is implicit 2017-04-20 19:46:40 +00:00
Ian Curtis 912bb0e7cf better state handling 2017-04-20 19:43:41 +00:00
Ian Curtis 9b226ed478 parse out some culling node values 2017-04-17 10:40:07 +00:00
Ian Curtis 3c78571615 There are 2 bits in the polyheader labelled discard. When both are set ie in sega rally, the polygons are totally discarded. Scud seems to set bit 1 which seems halve the opacity. 2017-04-15 19:00:46 +00:00
Ian Curtis 21836c088c The real3d has a flag that allows the hw to skip polygons so that they aren't rendered. Sega rally2 uses this for the dust effects. Triangles or quads that have this flag are junk, and look like random corruption if you try to draw them. We assumed polys that shared vertices with these bad polygons were also bad. It turns out the last few shared vertices in these polys were in fact valid, and thus the entire quad/triangle strip should be drawn and not discarded. 2017-04-14 23:41:11 +00:00
Ian Curtis fc50bdee98 light parameters must be clamped (HarryTuttle) 2017-04-14 00:08:17 +00:00
Ian Curtis 391aafd4c1 Virtua fighter has a few massive polys that shouldn't be visible. It looks like these polys have a bad matrix, but the node distances are all zero. This means the bounding box that encapsulates them is of size zero. Skipping over these entirely seems to fix the issue. 2017-04-12 15:47:57 +00:00
Ian Curtis 101e43213e cosmetic 2017-04-05 19:32:01 +00:00
Ian Curtis edfb521a9b Daytona seems to use this completely undocumented feature of the real3d pro-1000, the ability to invert texture colours. This patch fixes the colours on the cars, and the signs which should flash by alternating their colours. 2017-04-05 17:57:38 +00:00
Ian Curtis f0e00c5dc7 Rewrite the spot light code, and implement the missing fog logic. (HarryTuttle) 2017-04-02 21:03:59 +00:00
Ian Curtis 69eac95846 Replace glsl 3 function. Apparently this doesn't work on OS X. 2017-03-28 20:24:44 +00:00
Bart Trzynadlowski f34e25dfc7 Massive internal change: removed CConfig object and replaced it with a hierarchical config object system (Util::Config::Node). Games are now defined in an XML file. Hopefully I didn't break too many things :/ 2017-03-27 03:19:15 +00:00
Ian Curtis ff624afb4d The mipmap data in some games seems to being sent behind the base textures, and when the base textures are bound and created the mipmap chain is not yet valid in memory. To fix this, we invalidate the base textures, when the mipmap chain is updated. 2017-03-25 00:06:24 +00:00
Ian Curtis 06c1cdcf94 Just use 1 hash map for the textures, instead of 1 for each format. Should greatly speed up texture invalidation. TODO invalidate texture mipmaps .. the h/w actually seems to stream the mipmap data separate from the base textures in some cases. 2017-03-24 20:54:12 +00:00
Ian Curtis 98d56ff011 cosmetic 2017-03-24 17:43:07 +00:00
Ian Curtis 82ac030dff calculate the correct number of mipmap textures 2017-03-24 16:51:52 +00:00
Ian Curtis 17f878421b Originally to do mipmapping, I just used the base texture and then let the h/w automatically generate the mipmap chain. I wasn't sure the real3d api even exposed to the programmer the ability to directly set the mipmap data. Anyway, as pointed out by HarryTuttle scud actually uses darker mipmaps for an effect on the water. This patch uses the uses the actual mipmap data from the real3d memory. Only tested scud, so hopefully I didn't cause any cataclysmic errors :) 2017-03-24 13:38:20 +00:00
Ian Curtis 9780f333b4 The model3 has this weird issue where the 2d and 3d planes are misaligned by 2 pixels. Originally I made a quick hack that shifted subviewports 2 pixels. But apparently that wasn't enough, as the issue effects everything. Thanks to HarryTuttle for pointing this out, and making a patch :) 2017-03-19 01:33:45 +00:00
Ian Curtis b19ceb0b6a Texture coordinates seem to be scaled relative to the fixed texture size of 256. Thanks to HarryTurtle for figuring this crazy logic out. The road in scud matches the arcade now almost perfectly. 2017-03-13 00:59:35 +00:00
Ian Curtis dcd018ab7e Change microtexture scaling values. Seem to much better match expected output. (thanks HarryTuttle) 2017-03-12 19:00:00 +00:00
Ian Curtis 732e3ef51f More fixes to microtexture coordinates. They go vertically up and down the texture sheet, and not horizontally as I had guessed. (Thanks HarryTurtle) 2017-03-11 12:55:47 +00:00
Ian Curtis 6636776f03 Fix microtexture texture coordinates (thanks HarryTuttle) 2017-03-11 01:18:43 +00:00
Ian Curtis 503c88df11 fix the bad projection matrix in dirt devils and lost world 2017-03-07 01:29:07 +00:00
Ian Curtis f173c3c3ce The hardware actually seems to treat the quad primitive as a triangle strip. The winding order can actually change between the first and second 'triangle' inside the quad, leading our code to incorrectly backface cull the 2nd triangle. So we must re-calculate the winding order for the 2nd triangle. This fixes a massive missing poly in the road in la machine guns, probably other games too. The hardware is unaffected by the winding order, as it doesn't calculate the poly normal from the vertices directly, instead it uses the provided normal in the poly header. 2017-02-21 23:35:40 +00:00
Ian Curtis 5b9741bd5d Support high priority polygons. They are treated as a separate overlay plane by the h/w. Fixes some missing fx in harley. 2017-02-20 17:22:32 +00:00
Ian Curtis 2ae2010ee4 Add high priority poly function. Used by harley. 2017-02-18 23:58:08 +00:00
Ian Curtis 4a116190b5 When the translator map?? bit is enabled the colour format seems to be 4-5bit. Max observed value is 16. Scaling these values up seems to produce the correct colours in harley and dirt devils. 2017-02-16 17:20:42 +00:00
Ian Curtis 7407d03036 Put a check in there, in case near values come out really close to zero. Fixes a slight corner case in lemans24. A check probably should have been there originally :) 2017-02-08 16:14:50 +00:00
Ian Curtis 24cbeed526 Dynamically calculate near/far frustum planes for each viewport priority layer by clipping the overlapping meshes with the 4 frustum planes. A bit brute forcy, but the results are great. 2017-02-07 14:05:03 +00:00
Ian Curtis 144125a62e mark the nodes without valid distances set 2017-02-05 15:36:05 +00:00
Ian Curtis c82dc55485 cosmetics 2016-12-22 22:11:19 +00:00
Ian Curtis 72dd0dbf98 only need to cull against 4 clipping planes 2016-12-22 22:09:13 +00:00
Ian Curtis 20a9514aa2 For scroll fog set the viewport to the entire area, allows fog to work in widescreen mode 2016-12-15 19:27:08 +00:00
Ian Curtis ca7046729e properly cache un-normalised texture coordinates, fixes a texturing regression in Daytona 2016-12-15 12:10:52 +00:00
Ian Curtis f355e2d062 fix microtexture colours 2016-12-15 00:45:32 +00:00
Ian Curtis 89e75a9803 Only check scroll fog value from the first viewport from each priority layer. Seems to fix problems with background fogging. 2016-12-14 19:57:05 +00:00
Ian Curtis 707e945db9 delete unused files 2016-12-09 14:15:11 +00:00
Ian Curtis 2c23268d88 Support microtexture relative scale. The exact scaling values are not known, but a 2x difference between each level seems highly likely. We know from visual inspection from scud that the first level is exactly 4. The SDK has a function that accepts a float input for scale and does this. lod = (1/scale) + 0.5. If lod>3 lod = 3. So this is our best guess. 2016-12-09 14:13:46 +00:00
Ian Curtis da8b63b44b The model3 shares vertices between polygons. But it also seems to do this for polygons with different textures. This means the texture coordinate for potentially different sizes textures is shared. Currently this was broken leading to some corrupted looking textures. The fix is to simply cache the old texture coordinates, and recalculate the normalised coordinates in the new texture coordinate space. 2016-12-06 14:39:46 +00:00
Ian Curtis 10a5d2c0e1 refactor 2016-12-06 12:25:34 +00:00
Ian Curtis eece2d75b4 tweak scroll fog logic 2016-12-04 22:37:49 +00:00
Ian Curtis a310e8e5cf minor optimisations 2016-11-28 17:32:25 +00:00
Ian Curtis abc8c24b69 Only check the geometry for culling with valid node distances. We will need this later. 2016-11-27 19:30:46 +00:00