Now that Insecticide is completed, I need a new project. Hopefully one that won’t take 8 years. I had begun work on Action 54, but I have decided I didn’t want to do that any more. I had thought of a better idea. One that I can actually do, and one that I will enjoy play testing. So I’ve begun work on a game called “Chris’s Casino.” This idea came about because I figured card suits are red and black, roulette numbers are red and black as well (well, except for the green zeros.) And so I figured why not make this game for a system whose specialty is showing red and black then? I am not an artist, though, so I’d need a better title screen. The logo is independent of the cards/roulette table world. If someone could design a better picture I could use, I would very much appreciate it. First I would like to finish Video Poker and Roulette, and if that is successful, I might add more games, but for now, those are the two I want to do. I think I began work on a casino game before for the VB, but darned if I can find it. I also had a tough time because it took a while to display the title screen in Mednafen for some reason. Insecticide’s warning screen comes on right away. How odd.
Attachments:
So after hours and hours of trying, I finally made a roulette table where you can place a chip where you want to bet. It’s not a very nice-looking roulette table, though, but it gets the job done. I think I’ll play some casino game with roulette to further get the rules on where the chips can be placed.
Attachments:
Was thinking about it, and feel like this would be a good time to work on my 3d modeling skills; started modeling the roulette wheel and should be done with it soon enough.
Basic idea would be to pair it with a pixel art shader. Toshihiro Kushizaki’s made rounds at some point:
It’s quite excellent (and that way I could render it separately for both eyes if you wanted a stereoscopic version of it).
(PS: Swapped out the example cause I found one that wasn’t as awk.)
- This reply was modified 7 years, 7 months ago by Twila.
I now have an error when compiling with VBDE saying an argument error is too long. What argument? Where is it? Why does it even say that?
You should provide the whole project including all files, otherwise it’s hard to recreate the error.
Just to make sure, did you add a header file to the root of your project folder? You can just copy one from any of the sample projects and edit it.
I opened the file “release” and it had a file folder called “release” and I opened it and it had a file folder called “release.” It goes to infinity apparently. It’s a wonder I still have room on my hard drive.
VirtualChris wrote:
I opened the file “release” and it had a file folder called “release” and I opened it and it had a file folder called “release.” It goes to infinity apparently. It’s a wonder I still have room on my hard drive.
This generally happens when the incorrect bulding type is passed to the makefile. Make sure that you replicated exaclty the folder structure of the VBDE sample projects, delete the release folder, and try to compile from VBDE’s Notepad++ again (I guess you’re using that).
VirtualChris wrote:
I can’t delete the release folder. It says it’s too long.
I deleted it using Robocopy. But what’s weird is that VDBE worked for a while and then stopped because the name got too long. How did it get too long?
This is what it came up with at the end of the purge using Robocopy. Why does the VB development program just keep adding to the file name?
Attachments:
VirtualChris schrieb:
I deleted it using Robocopy. But what’s weird is that VDBE worked for a while and then stopped because the name got too long. How did it get too long?
I’m not sure about how VBDE’s makefile handles the building of its sample projects, since I only work with the VUEngine, but that makefile is a port of the VUEngine’s so the problem may be related to what I previously pointed. For the moment, just delete the release folder each time you compile until KR1553 can chime in.
- This reply was modified 7 years, 7 months ago by jorgeche.
You found a bug in the default makefile! Problem is that the compiler processes the contents of the build folder along with all the actual sources and thus produces that deep nesting you encountered.
I fixed the command to ignore the build folder. Please replace {VBDE}\system\makefile with the attached makefile.
Note: I had to zip it because our forum software does not seem to like files without a file ending…
Attachments:
While that did help with the deep nesting, it does seem like this could be shortened even more, am I correct? It looks like it is generating duplicate files of files I already have. (But I don’t know anything about what you’re doing, though.)
Attachments:
These are fine. The *.o and *.d files in the ./build/release/ folder are intermediate files for the compiler (a cache) which speed up consecutive builds, since only changed files will have to be processed the next time.
I meant the
casino/build/release/c/users/Chris/libs/libgccvb/compiler part. Does it really need to be that long?