byuu's message board

cool debugger additions, tried it out but I get crashes when I try to export (as I do with the previous release) memory.

Attempting to export anything in memory editor leads to a crash, but the new property additions seem to work fine.

Oops nvm, i found out how to solo map ctrl, alt, keys.

I had to put input.modifierEnable = false in the config file.

Excellent release as always, 1000x thumbs up for you mate, you freaking rock!

Edit: I don't know if this question has been asked already but would it be possible to add toggle for "fast forward" and "slowdown"? so you only have to press the key once and it start "fast forwarding" without letting the finger in the keys.

Thanks.

> I get crashes when I try to export (as I do with the previous release) memory.

Make sure your export path is read-write. It defaults to "same as loaded game", but you can override it in the paths section.

> I had to put input.modifierEnable = false in the config file.

Yep. Be sure to remap all the GUI shortcuts as well after doing that. Alt+Enter for fullscreen will now work by only pressing enter.

> would it be possible to add toggle for "fast forward" and "slowdown"?

It's already there. User Interface -> Emulation Speed -> Increase and Decrease. It's set to ctrl+multiply and ctrl+divide (on the numpad) by default. Press to permanently increase and decrease speed. Doesn't work so great with Vsync enabled for obvious reasons.

i keep bsnes & all its dirs/files in a folder in ~/.
i have now discovered that when putting libs (such as snesreader) in the same folder (as the bsnes binary) they are not recognized.
could you make bsnes also search in the same dir as the binary for libs?

clearing the appdata and making a bsnes.cfg file fixed it thank you very much.

I've been away for a while from the bsnes development forums. I've downloaded this latest version and was a little concerned about the way fullscreen works now...

Edit: My apologies. I've found what I was looking for. You pretty much have to toggle everything for fullscreen like you do in window mode. I was not aware of this.

I also noticed the controller graphic is gone again (unless I'm missing a secret checkbox). I recall the general consensus was to keep it, so what happened?

Given that you mention "~/" I assume you're using Linux. If so, you can make bsnes (or any other program) search for libraries wherever you want:

If you don't want to type that out each time, you can put it in your ~/.bash_profile, or just make a "startbsnes" shell-script that does that export before running bsnes.

I already have the d3dx_24.dll file, and otherwise have directx fully updated anyway.

Anything else that may be causing it?
Any way for me to help troubleshoot?

Thanks!

Edit:
I tried doing the same on a different computer -- my laptop, running Win7 x64. I'm getting the same crash...
Something is incredibly strange here. How can I be the only one experiencing the same crash, on two completely different configurations?

How do I access these modes please; I cannot find the fullscreen mode?

Thank you.

Windows 7 64 Bit
Pentium E8400

Hit 'Alt+Enter' to go fullscreen, and now hit 'Tab' to bring up the menubar.

I've managed to get this to happen to by having an opengl shader selected then switching to d3d mode. After going into the config file and clearing out the shader paths, it will start normally again, as you've discovered. Based on this, my suggestion would be to make sure that, when in d3d mode, you select a valid HLSL shader (the opengl shaders use a different, though similar, language and will NOT work with d3d). HLSL shaders will typically have a .fx extension. There's some in the recent WIP thread you should be able to try.

Given that there are already bsnes-specific uniforms, I am thinking it would be best to create a custom file format for bsnes pixel shaders and merge it all together so that only one file needs to be selected. Make it all text-based.

Something like:



Then the user only has to select one file, and can chain shaders together.

i don't know why this didn't occur to me. thanks Screwtape.

The .fx file format already supports this, actually. You can have as many "technique" blocks as you want, and as many functions in the file as you want. The D3D patch for dosbox makes use of this by allowing you specify via semantics which techniques to apply in which order. Semantics are basically a way to add a flag to a variable that can be queried by the effect framework. So for instance, a uniform could be tagged with the SOURCETEXTURE semantic, instead of having to have a specific name. As an example, the dosbox version of my shader has:

After the shader is compiled, dosbox looks for the technique semantics and uses them to determine what order to apply them. Since my shader is only 1 pass, I leave the PREPROCESSTECHNIQUE blank.

FX also supports attributes, which allow you to associated more detailed metadata with a variable, such as a description string and min/max values that can be used in UI generation. Programs like FX Composer go crazy with this kindof stuff.

The rub is, of course, that every program that consumes a shader will do it slightly differently. I think this is basically unavoidable though. As long as the necessary information is exposed somehow, it's not that hard to adapt a shader to whatever system.

I don't know enough about GLSL specifically to suggest the best approach in that case though.

Ah. Feeling silly.

Couple of thoughts then:
1. This is not at all clear from the configuration dialog. Specifically having a folder called "pixelshaders" that only works for the OpenGL driver is extremely confusing to anyone not an expert on shaders.
2. bsnes should not crash when trying to load the wrong kind of shader file...

Thanks for the help and clarification.