Outrun

[Arcatech]

Can anyone else check but I have used the supplied zImage_dtb for use with the OUTRUN core but noticed that on 2 seperate Mister setups I have here the USB ports are no longer showing as having anything being plugged into them and my WiFi dongle no longer works.

This have been confirmed on my Jamma Expander and Mistercade setups

Changing back to my original backup of the zImage_dtb file the USB ports start working again so it is something to do with that file.

Has to be something on your end. This has been tested by multiple people with wheel setups. You can also try this build if you plan to use logitech wheels as it has the changes applied as well. I've been using the kernel linked for over 90 days.

https://github.com/coolbho3k/Linux-Kern ... tag/v1.0.1

No problem, I never noticed the missing wifi icon initially in the Mister menu until I tried to do an update_all which failed so was wondering if it was something that may have been overlooked but as you say if you been using it for 90 days+ then it's something going on my end.

I'll try the attached Linux Kernel and report back....thanks!

[thorr]

Does force feedback work to jiggle the wheel when going off the road at this point with Outrun? I know this was discussed for PSX and as of last I heard isn't supported. Just curious.

[Arcatech]

Can anyone else check but I have used the supplied zImage_dtb for use with the OUTRUN core but noticed that on 2 seperate Mister setups I have here the USB ports are no longer showing as having anything being plugged into them and my WiFi dongle no longer works.

This have been confirmed on my Jamma Expander and Mistercade setups

Changing back to my original backup of the zImage_dtb file the USB ports start working again so it is something to do with that file.

Has to be something on your end. This has been tested by multiple people with wheel setups. You can also try this build if you plan to use logitech wheels as it has the changes applied as well. I've been using the kernel linked for over 90 days.

https://github.com/coolbho3k/Linux-Kern ... tag/v1.0.1

Just tried this Kernel and USB/Wifi back working....Thanks!

[AmanoJacu]

I just got the beta from Jotego, I'm trying to make xbox one or PS4 controllers to work as analog (wheel on left stick, accelerate in right trigger, brake in left trigger) following these instructions (Analog Trigger Mapping for MiSTer Main):

https://www.patreon.com/posts/logitech-wheel-69857028

I put this configuration in mister main, and in the core I leave buttons by default, and "A. triggers". But brake gets mapped to right analog stick down. Steering and accelerate work fine.

I don't know what I'm doing wrong. Any help will be appreciated. Thanks!

EDIT: In attrac's instructions, I changed the last one from "Stick 1 Tilt Down = down on right stick" to "Stick 1 Tilt Down = left analog trigger", since it made more sense to me, and using the original instructions I got brake in right analog stick down. Now it works with both xbox one and PS4 controllers.

So I don't know what is happening, but if anybody has the same problem, you can try this.

[fierman]

I fiddled a bit, trying to see if Turbo Outrun would load at all, used the manual for the Outrun upgrade kit as a reference (https://arcarc.xmission.com/PDF_Arcade_ ... lement.pdf)
The game boots, but does not load the graphics set. I assume this is because the jumpers are not set as instructed in the manual. I also assume this would be relatively easy to do in the core code. We just have to wait it out a bit

Code: Select all

<!--          FPGA arcade hardware by Jotego

              This core is available for hardware compatible with MiST and MiSTer
              Other FPGA systems may be supported by the time you read this.
              This work is not mantained by the MiSTer project. Please contact the
              core author for issues and updates.

              (c) Jose Tejada, 2022. Please support this research
              Patreon: https://patreon.com/jotego

              The author does not endorse or participate in illegal distribution
              of copyrighted material. This work can be used with compatible
              software. This software can be homebrew projects or legally
              obtained memory dumps of compatible games.

              This file license is GNU GPLv2.
              You can read the whole license file in
              https://opensource.org/licenses/gpl-2.0.php

-->

<misterromdescription>
    <about author="jotego" webpage="https://patreon.com/jotego" source="https://github.com/jotego" twitter="@topapate"/>
    <name>Turbo Out Run</name>
    <setname>toutrund</setname>
    <rbf>jtoutrun</rbf>
    <mameversion>0232</mameversion>
    <year>1986</year>
    <manufacturer>Sega</manufacturer>
    <players>1</players>
    <joystick/>
    <rotation>horizontal</rotation>
    <region>World</region>
    <mraauthor>jotego</mraauthor>
    <rom index="0" zip="toutrun.zip" md5="None">
        <part>
            00 00 00 00 00 00 00 00
            00 00 00 00 00 00 00 00
        </part>
        <!-- maincpu - starts at 0x0 -->
        <interleave output="16">
            <part name="epr-12512.118" crc="5e9d788b" map="01"/>
            <part name="epr-12513.133" crc="a1881cea" map="10"/>
        </interleave>
        <interleave output="16">
            <part name="epr-12514.117" crc="faf00bd6" map="01"/>
            <part name="epr-12515.132" crc="fd432e2d" map="10"/>
        </interleave>


        <part repeat="0x20000"> FF</part>
        <!-- subcpu - starts at 0x60000 -->
        <interleave output="16">
            <part name="opr-12294.58" crc="27cdcfd3" map="01"/>
            <part name="opr-12295.76" crc="d43a3a84" map="10"/>
        </interleave>
        <interleave output="16">
            <part name="opr-12296.57" crc="0a513671" map="01"/>
            <part name="opr-12297.75" crc="1d9b5677" map="10"/>
        </interleave>
        <part repeat="0x20000"> FF</part>
        <!-- soundcpu - starts at 0xC0000 -->
        <part name="epr-12300.88" crc="e8ff7011"/>
        <part repeat="0x8000"> FF</part>
        <!-- pcm - starts at 0xD0000 -->
        <part name="opr-12301.66" crc="6e78ad15"/>
        <part repeat="0x8000"> FF</part>
        <part name="opr-12302.67" crc="e72928af"/>
        <part repeat="0x8000"> FF</part>
        <part name="opr-12303.68" crc="8384205c"/>
        <part repeat="0x8000"> FF</part>
        <part name="opr-12304.69" crc="e1762ac3"/>
        <part repeat="0x8000"> FF</part>
        <part name="opr-12305.70" crc="ba9ce677"/>
        <part repeat="0x8000"> FF</part>
        <part name="opr-12306.71" crc="e49249fd"/>
        <part repeat="0x8000"> FF</part>
        <!-- gfx1 - starts at 0x130000 -->

	<interleave output="16">
	    <part name="epr-12292.116" crc="51d98af0" map="01"/> <!-- TOR -->
	    <part name="epr-12293.131" crc="f4321eea" map="10"/> <!-- TOR -->
	</interleave>



        <interleave output="32">
            <part name="opr-12323.102" crc="4de43a6f" map="0001"/>
            <part name="opr-12324.103" crc="24607a55" map="0010"/>
            <part name="opr-12325.104" crc="1405137a" map="0100"/>
            <part name="opr-12325.104" crc="1405137a" map="1000"/>
        </interleave>
        <!-- sprites - starts at 0x170000 -->
        <interleave output="32">
            <part name="mpr-12336.9" crc="dda465c7" map="0001"/>
            <part name="mpr-12337.10" crc="828233d1" map="0010"/>
            <part name="mpr-12338.11" crc="46b4b5f4" map="0100"/>
            <part name="mpr-12339.12" crc="0d7e3bab" map="1000"/>
        </interleave>
        <interleave output="32">
            <part name="mpr-12364.13" crc="a4b83e65" map="0001"/>
            <part name="mpr-12365.14" crc="4a80b2a9" map="0010"/>
            <part name="mpr-12366.15" crc="385cb3ab" map="0100"/>
            <part name="mpr-12367.16" crc="4930254a" map="1000"/>
        </interleave>
        <!-- segaic16road - starts at 0x270000 -->
        <!-- Singleton region. The files are merged with themselves. -->
        <interleave output="16">
            <part name="epr-12299.47" crc="fc9bc41b" map="01" length="0x4000"/>
            <part name="epr-12299.47" crc="fc9bc41b" map="10" length="0x4000" offset="0x4000"/>
        </interleave>
        <interleave output="16">
            <part name="epr-12298.11" crc="fc9bc41b" map="10" length="0x4000"/>
            <part name="epr-12298.11" crc="fc9bc41b" map="01" length="0x4000" offset="0x4000"/>
        </interleave>
        <!-- Total 0x270000 bytes - 2496 kBytes -->
    </rom>
    <rom index="17" zip="jtbeta.zip" md5="None">
        <part name="beta.bin"/>
    </rom>
    <nvram index="2" size="12288"/>
    <rom index="1">
        <part>00</part>
    </rom>
    <switches page_id="1" page_name="Switches" base="16" default="ff,f9">
        <!-- COINAGE -->
        <dip name="Coin A" bits="0,3" ids="Free Play or 1/1,1/1 2/3,1/1 4/5,1/1 5/6,2/1 4/3,2/1 5/3 6/4,2/3,4/1,3/1,2/1,1/6,1/5,1/4,1/3,1/2,1/1"/>
        <dip name="Coin B" bits="4,7" ids="Free Play or 1/1,1/1 2/3,1/1 4/5,1/1 5/6,2/1 4/3,2/1 5/3 6/4,2/3,4/1,3/1,2/1,1/6,1/5,1/4,1/3,1/2,1/1"/>
        <!-- DSW -->
        <dip name="Cabinet" bits="8,9" ids="Unused,Mini Up,Up Cockpit,Moving"/>
        <dip name="Demo Sounds" bits="10" ids="On,Off"/>
        <dip name="Time Adj." bits="12,13" ids="Hardest,Hard,Easy,Normal"/>
        <dip name="Difficulty" bits="14,15" ids="Hardest,Hard,Easy,Normal"/>
    </switches>
    <buttons names="Accelerate,Brake,Gear (Low / High),-,Start,Coin,Core credits" default="Y,X,B,A,Start,Select,-" count="3"/>
</misterromdescription>

[PistolsAtDawn]

I realize it's in beta so expecting perfection would be dumb, but these differences from MAME caught my attention:

The acceleration is off in low gear, and it shows a different speed when at max revs in low gear. In MAME it wants me to shift from low to high gear around 130-140. In the new beta your speed continues on towards 200 before you're in the green area of the RPM indicator.

The rate of acceleration is lower while in low gear in the beta than it is in MAME. It takes longer to get into high gear especially when you wreck and have to wait for the car to reset position.

Changing down from high gear while at max speed doesn't have the same dramatic reduction in speed either.

These things make recovery from minor mistakes take longer which makes the game harder overall.

Braking also seems to work better than in MAME. In the beta I can avoid flying off the road on hard turns much more often due to the difference in braking.

I compared using the same revision B ROM. I'm using MAME .249

I have reported these bugs here: https://github.com/jotego/jts16/issues

[Aspie]

Anyone else find it crashes a lot? It usually plays ok on the first credit. The next game it's liable to crash or I get thick black horizontal lines across the screen. Sometimes it just stops and says game over.

Super Hang On was playing perfectly before the update. Now I get a weird bar across the sky and the graphics have become all jittery.

[PistolsAtDawn]

Anyone else find it crashes a lot? It usually plays ok on the first credit. The next game it's liable to crash or I get thick black horizontal lines across the screen. Sometimes it just stops and says game over.

Super Hang On was playing perfectly before the update. Now I get a weird bar across the sky and the graphics have become all jittery.

I find that the graphics get a little more glitchy as time goes on, but I have not experienced a crash.

Are you up to date on everything else?

[charmless]

Anyone else find it crashes a lot? It usually plays ok on the first credit. The next game it's liable to crash or I get thick black horizontal lines across the screen. Sometimes it just stops and says game over.

Super Hang On was playing perfectly before the update. Now I get a weird bar across the sky and the graphics have become all jittery.

I'm having similar problems. Super Hang On went from running great to looking all messed up. But the stuff is still in Beta so it'll probably get fixed later on.

[eldritch]

I've noticed a gap in the road in various places and graphical anomalies. Nothing game breaking and can hopefully be fixed with some tweaking. I'm linking some examples below. Both issues are reproduceable and predictable.

oi5MHqa.jpeg (4.73 MiB) Viewed 5118 times

WbsLsHc.jpeg (2.61 MiB) Viewed 5118 times

[PistolsAtDawn]

I've noticed a gap in the road in various places and graphical anomalies. Nothing game breaking and can hopefully be fixed with some tweaking. I'm linking some examples below. Both issues are reproduceable and predictable.

Jotego probably just wanted to release something now rather than wait for perfection since it had been a while since his last release. This is from the Patreon post:

If you can operate your circuit logic at a very fast speed, it is possible to get away without the frame buffer. This is the preferred solution for modern FPGA systems because it reduces the board requirements. I did this for CPS2 and that’s why it can work in small systems like the MiST family. However, things didn’t go as well for Out Run. Even processing the video at 100MHz, there are some scenes so clutered that the line time finishes before all sprites have been parsed and that results in a missing line in the image.

100MHz is also a challenging speed for FPGAs so a lot of timing violations start to happen inside the system. A timing violation in digital circuits means that under some circumstances the signals either arrive too late or disappear too soon, so information may be lost. Overall, the line-buffer solution on a fast clock is not a solution for Out Run on FPGA. We need a real frame buffer.

Today’s beta operates using the line-buffer approach but I am working on the frame buffer one. The frame buffer is only possible on MiSTer and Pocket FPGAs.

[twonunpackmule]

I tested the game with a recently acquired Logitech G920 wheel and pedals. I was able to get the game to play using the setup, but found that during gameplay the pedals would get confused. Basically, once I tapped the brake pedal, it would then require me to hold the brake pedal in order for the acceleration pedal to work.

Any known reason why this might happen?

[AmintaMister]

I tested the game with a recently acquired Logitech G920 wheel and pedals. I was able to get the game to play using the setup, but found that during gameplay the pedals would get confused. Basically, once I tapped the brake pedal, it would then require me to hold the brake pedal in order for the acceleration pedal to work.

Any known reason why this might happen?

The author of the driver answered me on Patreon that he can't support officially the G920 but only the G29 because G920 doesn't offer the needed documentation / API to developers. I've ordered a G29, tomorrow it will be delivered to me and I will let you know if the pedals (same problem here) work correctly...

[twonunpackmule]

I tested the game with a recently acquired Logitech G920 wheel and pedals. I was able to get the game to play using the setup, but found that during gameplay the pedals would get confused. Basically, once I tapped the brake pedal, it would then require me to hold the brake pedal in order for the acceleration pedal to work.

Any known reason why this might happen?

The author of the driver answered me on Patreon that he can't support officially the G920 but only the G29 because G920 doesn't offer the needed documentation / API to developers. I've ordered a G29, tomorrow it will be delivered to me and I will let you know if the pedals (same problem here) work correctly...

Hmm. Not excited about having to get a new wheel. I grabbed this one because I was able to get the whole kit for $100 on Facebook Marketplace. Still, let me know. I wonder if there's any way to pester Logitech for the documentation?

[AmintaMister]

I tested the game with a recently acquired Logitech G920 wheel and pedals. I was able to get the game to play using the setup, but found that during gameplay the pedals would get confused. Basically, once I tapped the brake pedal, it would then require me to hold the brake pedal in order for the acceleration pedal to work.

Any known reason why this might happen?

The author of the driver answered me on Patreon that he can't support officially the G920 but only the G29 because G920 doesn't offer the needed documentation / API to developers. I've ordered a G29, tomorrow it will be delivered to me and I will let you know if the pedals (same problem here) work correctly...

Hmm. Not excited about having to get a new wheel. I grabbed this one because I was able to get the whole kit for $100 on Facebook Marketplace. Still, let me know. I wonder if there's any way to pester Logitech for the documentation?

Apparently, not...

[twonunpackmule]

That's sad. Either way, let me know how the G29 goes. I have some ideas on how to correct my misfortune.

[Milspex]

Is wobbly video output and losing sync a known bug on hdmi 1080p?

Its the only game where the video is skewed and wobbling all over the place on my LG C7 oled

[Fpg-lee]

Is wobbly video output and losing sync a known bug on hdmi 1080p?

Its the only game where the video is skewed and wobbling all over the place on my LG C7 oled

I have the same issue on my C8 all resolutions under that display fine.
Weirder still, I tried my Mister multi-system on my LG C9 in the other room and got no signal at all on clean boot didn't even get to try a game.

[Milspex]

good to hear its not just me

[PistolsAtDawn]

I imagine (hope anyway) that those sync issues will be better when Jotego releases a version with a frame buffer. If I'm reading his message correctly, the current method using a line buffer at a very high frequency is a bit of a hack which isn't super stable either.

[twonunpackmule]

The author of the driver answered me on Patreon that he can't support officially the G920 but only the G29 because G920 doesn't offer the needed documentation / API to developers. I've ordered a G29, tomorrow it will be delivered to me and I will let you know if the pedals (same problem here) work correctly...

Hmm. Not excited about having to get a new wheel. I grabbed this one because I was able to get the whole kit for $100 on Facebook Marketplace. Still, let me know. I wonder if there's any way to pester Logitech for the documentation?

Apparently, not...

So, I tried it with a G29 and still experience the issue with the brakes and accelerator. Have you had better luck?

[AmintaMister]

Hmm. Not excited about having to get a new wheel. I grabbed this one because I was able to get the whole kit for $100 on Facebook Marketplace. Still, let me know. I wonder if there's any way to pester Logitech for the documentation?

Apparently, not...

So, I tried it with a G29 and still experience the issue with the brakes and accelerator. Have you had better luck?

Tested tonight, same issue here also. I'm writing to the author, I think I will keep the G920 and I'll send back the G92...

[tecteam]

Logitech g29 or other users - ensure you have used the forked Linux kernel that has the drivers. Then configure controller in MiSTer Menu
left stick right axis steering
Left stick down axis acceleration pedal
Right stick right axis brake pedal
Right stick Down axis 3rd pedal

I found it worked better with no other controller plugged in

Good luck
Ps my first post but read here everyday for 12 months - Hello

[twonunpackmule]

I was able to get it to work...magically. Following the directions to a T led to the same issue occurring over and over again. However, when mapping the buttons to the MiSTer Main I followed the directions, but when mapping to the OutRun Core I swapped brakes for clutch. This led to the brakes working correctly via the brake pedal. Not sure why. But, I am not messing with it anymore.

[bankshot]

2 Questions:

Exactly what modifications need to be made to the other arcade driving cores to make atrac17's hard work more usable across the platform? Spy Hunter arcade core, I'm looking at you!

I was also thinking about purchasing a GRS Star Wars yoke and was curious what it would take to apply atrac17's work to that piece of hardware?

[suww37]

Does the Jotego Outrun core work well at the moment? It was first released. The Outrun core screen was so broken that it couldn‘t be played. I wonder if these problems have been solved now.

[charmless]

Does the Jotego Outrun core work well at the moment? It was first released. The Outrun core screen was so broken that it couldn‘t be played. I wonder if these problems have been solved now.

OutRun, Turbo OutRun and Super Hang-On are still broken, at least for me.

[Retro-Nerd]

The games need a frame buffer implementation. The work on that isn't finished yet.

[insanityprawnboy]

When Outrun loads up, it says "Beta Bin not found", is that the same for everyone else? I ask as it plays, but the graphics look a tiny bit odd (the shadow on the car has an outline etc).

[jca]

Outrun is in beta. You must have enabled the download of Jotego Betas in update all script and you are not one of his patrons.
What you see is normal.