Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Encountering A Weird Glitch - But Love The Game

A topic by alexw128 created 52 days ago Views: 357 Replies: 23
Viewing posts 1 to 6

Hey there, I'm running into an odd glitch on the 0.40 test version where in all modes after the first straight the turn is compressed into a extreme angle and everything gets messed up. Just wanted to see if that was a known thing.

Also, congrats on the new baby!

Also, also, this is a fantastic tribute and game, love what you've done here. Outrun is awesome and I think you've managed to distill what is awesome about it and even amplify and enhance it. Very cool. I've thought about attempting some kind of retro racer too and never dived in, maybe I should try it with my average Unity, art, and coding skills haha. 

Thanks!

This is exactly what I was coming here to report. I hope we can figure out what is the problem. I am testing it on a Legion Go.

Developer

Hello Alex,

Thank you very much!

It probably has something to do with the option "corner sharpness". It's a slider that can be set between 50 and 100 %. I believe it's under "miscellaneous" at the bottom. Standard value is 85. Can you take a look at that?

Did you use the options file that came with the v0.4.0 zip file?

Changing the value to 85 fixed it for me.

Thank you! This Reimagining of Turbo Outrun is INSANELY good!

Any chance adding rumble support in the future?

Developer

Awesome! And it should work with any value between 1 and 100.

I've been looking into it, and I will add the rumble function as an extra update once v0.4.0 is ready!

(1 edit)

Hi! When I opened the Options.txt file all I see is this (v0.4.0)

1

1

0

1

0

1

1

1

1

1

1

0,75

0

0

0

0

1;0;0

1;0;0

1;0,33;0

0

0,5292969;0,7207031;0,5273438

1

1

0

0

1

1

0

1

0

0

1

0,85

25

1

0

 I dont see the Miscelanous section any naming .

 Any ideas?

 Thanks

Developer(+1)

馃槅 I mean in the game itself. I intentionally didn't label these values because I don't want people to know what those are. (Not all values are option values. There is also a boolean that triggers a secret mode that no one has discovered yet.)

That was it. 85 is perfect. Dang it looks sweet in my Legion Go! :D
Thanks a ton!!!!!!

Developer(+1)

Awesome! Have fun!

Hi Sk1ds! 

I'll give that a shot when I boot up the game next thanks!

As far as I know I was using the options file that came with and inside the v0.40 zip and haven't altered it. I'll let you know if tweaking the corner sharpness slider fixes it. 

By the way how did you achieve that cool endless plane look of the ground/road in Unity? It's a really neat effect.

Thanks!

Developer (1 edit)

Really? Oh dear, then it might be another regional problem. I'll look into it as soon as I can. Changing the option setting in game might do the trick, because then it stores the value with a point instead of a comma.

To answer your question: it's not really an effect. I just made the ground 1 kilometer wide to each side.

Interesting, I have heard of issues with some geometry as far as rounding errors and whatnot when it gets to be a great size. Really only a problem in very large open world games though I think. I've thought about trying to recreate that SNES mode 7 look and make a racing game like that, but getting the driving feel down just right is the make or break of a great racing game and I think you've got that for sure. 

Developer

True, when development was still in its early stages, I was stress testing the game, by just letting a bot drive for about 3600 km. After a while the road and the other cars started to shake and the bot was constantly stopping, instead of slowing down for the corner. That's why I reset the z-position after each stage. I haven't got it 100% seamless though, as you'll see the trackside objects disappear for 1 frame.

The regional problem was an issue before. I called it the lightspeed bug. I've made a file that represented a tire slip curve. Those were values between 0 and 1. The decimal sign was a comma, because I'm from Belgium. But for people from the USA for instance, who use a point instead of a comma, this was a big problem, because the game just skipped the decimal sign, multiplying the values by 100 in the process. The cars went like the speed of light. I solved it back then, but maybe this new issue is something similar.

That mode 7 game shouldn't be too hard to make! But yes, getting an engaging driving model isn't easy. Most of my driving model comes from the drivetrain and straight-line tire simulation, but also the way the car starts to understeer when you go too fast through a corner AND very importantly and the finishing touch: how the car gets slightly more grip when you release the throttle or brake very gently while steering. I got my inspiration from Super Hang-On where the same effect was pretty obvious when you rapidly toggle the turbo on and off. Without this, the driving was rather dull.

Developer(+1)

Update: I was right. It was a regional issue. I parsed the values of the corner sharpness instead of converting them with a default culture setting. I've  changed it and now it should work flawlessly without having to change the setting in-game! (After I've uploaded the new version.)

Well that's great you figured it out, that's an unusual bug, definitely something that's hard to test and catch yourself, I never would have even thought of it. 

That's awesome that you have so thoroughly detailed the driving model for the game and have so many different factors playing into it. There's many racing games out there now and in the past that just don't achieve the fun factor and sheer joy of driving that Outrun captures, and what you've got going here. Sega sure made a lot of great racing games. One thing you have to be sure to add is a great game over screen, in the proud tradition of great Sega ones in Daytona, Sega Rally, etc. 馃槃

Developer

Yeah, haha, I couldn't wrap my head around it when that regional problem manifested for the first time. I just couldn't replicate the problem that so many people had.
I got my epiphany when I made and uploaded a log version of my game so I could compare my log file with the log file of someone else. I knew something was up when I saw that the decimal sign in my own log file was a comma and in the other one a point. I then set my system to USA settings and voila, I was able to replicate the problem on my system. The rest is history.

Yeah, I'm so glad that my game seems to hit the spot! About the game over screen: yeah, maybe I can add some dramatic voice-over to the game over message!

As a matter of fact: I'd really like to add some spoken lines to the game, especially in the car select menu. I'd like to replicate the excitement of Daytona USA2.

That sounds exactly like my experience with debugging anything, feeling around the edges and weird output of a problem until you suddenly piece together what's going wrong with it in your mind. 

Yeah some radio chatter might add a little bit of flavor to the game for sure. Daytona USA is great and I haven't played Daytona USA 2 that much but it seems fun as well. Have only toyed with it in emulation, where it's kind of a broken mess. I really wish Sega would rerelease that. Or make a racing compilation with Outrun, Turbo Outrun, Outrunners and Outrun 2 on it. But I think they lost the Ferrari license which complicates things. 

Daytona and Virtua Racing kinda make me want to make a low res polygon racer too haha. But there are a couple of those out there already. 

I also had this problem and fixed it according to this thread and setting this value to 85.  FYI, when I downloaded the game the default setting for this value was 850, not 85! No wonder the game went crazy...

Developer

It was a regional problem. The value in the options file is 0,85 with a comma as the decimal sign. On your system the decimal sign is probably a point, so Unity skips the decimal sign, multiplying the value in the process. You probably have a similar setting for the traffic car engine sounds, which makes them way too loud.

It's fixed in the latest version.

Using 3840x2160 143.999Hz with v0.4.0

I had to amend line #33 in the options.ini file from 85 to 1 to make it playable, any other number higher then 1 was too fast and unplayable on bends.

Im not sure if that line is the correct line for corner speed setting but it seemed to work for me.

A suggestion instead of "Rival here" above cpu cars, a simple "Rival" would seem shorter and neater. either way the game is cool

Developer

Hah, good detective work!

The problem is fixed in the latest version.

The "rival here!" message is a direct homage to Chase HQ where the arrow said " criminals here!". You're the second person who suggests to drop the "here", so if there are more people, I'm probably about to do it.

changing the value to 85 fixed it for me.

Thank you

(1 edit)

This game is great! Question is the police car in one of the modes? The one that tries to run you over. I havent seen it yet. 

Developer

Not yet. It will someday. The code for the police car is pretty much there, but right now it's used for another very special and secret opponent...