Coder Social home page Coder Social logo

xdc's People

Contributors

mobygamer avatar shattered avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

xdc's Issues

XDC_COMP: Divide-by-zero at startup

Hello!

I'm having some really weird behaviour with the compiler binary provided in the COMPILED directory. I'm getting a divide-by-zero exception, ostensibly as it parses the input script, and I'm not sure if it's an error in my script or something wrong in my DOSBox config (although it also seems to happen on a default config with 0.74). Hopefully someone else has run into this before.

Error:

Fatal runtime error 200 at 0000:0570: Division by zero

Script:

# Smells Like Teen Spirit
screenmode=1
sourcefps=24
waveinput=smells.wav
maxdiskrate=160
# frames
sm000001.bmp
sm000002.bmp
sm000003.bmp
sm000004.bmp
sm000005.bmp
#...

Log:

594928 bytes free
Parsing input script ..\smells\smells.scr
Assuming encoding fps of 59.922751014 which grants 39824 cycles pe

The log ends in the middle of that line, but I assume it's because the rest of it was lost in a write buffer.

I think that the only non-default thing I have in my DOSBox config is cycles=max, but I don't expect it to be an issue.

Any pointers for things I should investigate?

Visual artifact running 'silent mode' in DOSBOX

The running the XDC_PLAY.EXE in DOSBOX with /q parameter in DOSBOX will result in 30%~50% pixels displayed correctly, but others are just filled with random patterns. This is worse when video mode is set to svga_s3. However, there is always a portion of pixels displayed correctly and the timing (i.e. framerate) also seemed correct.
I presume that this problem may be caused by imperfect emulation of 8253 by DOSBOX, therefore it shouldn't appear on a real PC.

Video running too fast?

Per the title, it seems the video always runs too fast. I have an ESS ES488 SB clone, which isn’t supported, so it defaults to using quiet mode. Any advice?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.