Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

3dSen VR - 3D NES Emulator For Virtual Reality

Breathing new life into classic NES games by magically converting it into 3D and letting you play in VR · By geod

Road Fighter

A topic by JJXB created May 19, 2018 Views: 1,239 Replies: 13
Viewing posts 1 to 5

I've been thinking on some things and thus i know there's a 3dn file out there for this already but i wondered if i could use the work i've done on RCR in any other games and it actually work without any problems. as it turns out, yes!. so while very incomplete and buggy, this is my initial work on getting this to work in third person via playfield manipulation if anyone wants to either try it or improve upon it.

3dn file

okay, updated 3dn file. the road is in a semi-working state but the actual cars work and you could "play" it in this state:

3dn File

(3 edits)

After an extensive rewrite of the field handling, i am proud to say that the functionality of both the road and the cars are now working! i'd have to tidy up some of the 3d shapes but everything is being auto-layered via script so it won't look stupidly out of place. oh and there's a cheat script in place that you can easily disable.

rename as needed.

edit: got to reupload it

Edit 2: as of further testing there's very minor bugs but still very usable. 3dn

Edit 3: screenshot added

(1 edit)

Could you attach a screen shot so  it's easier for everyone to imagine about the profile please?

done.

Thank you!

By the way what game is it RCR? 

River City Ransom if you recall the other thread on it.

I guess you mean scripting reuse right? At first i thought it were graphic reuse so a little bit surprised :)  

yeah, scripting reuse. thankfully, the sprites in this weren't an issue with changing Y to Z.

(1 edit)

Just give it a try. Wow there are massive scripting in there, my hat off too you. This profile makes me wondering if support : camera z-rotation and input remap from scripting is the right choice.

By the way as you found out is : Script:ReadMem not ScriptManager:ReadMem. This is a document bug. I just recheck and hexa number works fine. 

(1 edit)

well then, thanks :) trying to figure the stuff out was something i took longer to figure out than i'd like to admit overall but i got there and cleaned up the code enough that it doesn't look like an absolute mess.

it just always seems very intermittent as to when hex addresses work for me in some instances. and on WriteMem it tends to not accept values to write like 0E or 1E but accepts E on it's own (the error with the previous examples being malformed number error). is that just me doing something wrong or is that another thing entirely like the address has to be in hex but the value to write has to be in decimal?

with hexa number we have to ad 0x prefix then it will work

so that's where i was going wrong. I'd suggest putting notes into the documentation on small bits like that where relevant though since things like that will help anyone else wanting to try and script for this.