What version of the prereq file did you install? The error message you posted doesn't make much sense since you have a decently new computer running Windows higher than 7 with a dedicated GPU that can do 3D quite well. I'm pretty sure DX9 games work on Win8 so the fact it fails to create a Dx9 device is troubling. The other thing I can think of is updating your GPU drivers and/or Intel if it does both. Other thing I can think of is forcing BizHawk to use NVidia.
Sorry, i was wrong. I have AMD graphic (with updated drivers and Catalyst).
Anyway i've installed the correct prereqs, but after i saw it didn't work, i installed other prereqs too but nothing changed...
Sorry, i was wrong. I have AMD graphic (with updated drivers and Catalyst).
Anyway i've installed the correct prereqs, but after i saw it didn't work, i installed other prereqs too but nothing changed...
Sorry, i was wrong. I have AMD graphic (with updated drivers and Catalyst).
Anyway i've installed the correct prereqs, but after i saw it didn't work, i installed other prereqs too but nothing changed...
Which two prereq files versions did you try?
I've tested v1.1, v2.0 and v2.1 (and different bizhawk version)
I've tested v1.1, v2.0 and v2.1 (and different bizhawk version)
If you don't mind some reboots, can you try this?
1. Reboot
2. Install version 2.1 of prereq
3. Reboot
4. Extract to a new folder of BizHawk version 2.3
5. Try it out!
What do you mean by that? It should work for any console.
[14:15] <feos> WinDOES what DOSn't
12:33:44 PM <Mothrayas> "I got an oof with my game!"
Mothrayas Today at 12:22: <Colin> thank you for supporting noble causes such as my feet
MemoryTAS Today at 11:55 AM: you wouldn't know beauty if it slapped you in the face with a giant fish
[Today at 4:51 PM] Mothrayas: although if you like your own tweets that's the online equivalent of sniffing your own farts and probably tells a lot about you as a person
MemoryTAS Today at 7:01 PM: But I exert big staff energy honestly lol
Samsara Today at 1:20 PM: wouldn't ACE in a real life TAS just stand for Actually Cease Existing
I've tested v1.1, v2.0 and v2.1 (and different bizhawk version)
If you don't mind some reboots, can you try this?
1. Reboot
2. Install version 2.1 of prereq
3. Reboot
4. Extract to a new folder of BizHawk version 2.3
5. Try it out!
Hi Darth Marios,
In order to get a visually rich RAM watch like the one you are referring to, I created a "simple" C DLL. I then invoked the functions of that DLL from a Lua script.
In a C library, you can theoretically do anything. One of my entry points was creating a thread, which spawned a graphical window with SDL. Another entry point was writing the RAM data in shared variables so that the UI thread could display these values.
When first loading the script, I would launch the UI thread. At each frame update, I would send the library my variables.
Really that's the extent of it... Hope that helped.
In Virtualdub do you change the aspect ratio after you setup the resize filter settings for the video you made?
Asol, is the aspect ratio different for Genesis consoles or is it just the same?
In Virtualdub do you change the aspect ratio after you setup the resize filter settings for the video you made?
If you're processing in Virtualdub alone, then you can do this at any stage but for the best quality output it's best to do it last. I'd resize each dimension to something larger (it doesn't have to be way over, just slightly bigger) than the 4:3 resolution you want using nearest neighbor, then I'd resize back down to the destination using Lanczos. You'll get even better clarity if you can avoid resizing either the width or height in this final step. I'll do my best to explain via some examples:
Assuming you have Genesis footage which is 320x224. You can point resize this by 300% to 960x672. From here, you can do a number of resizes to make it 4:3. You can Lanczos resize it to 960x720, which will expand the height or you can Lanczos resize it to 896x672, which will shrink the width. In both cases, one dimension remains untouched and will remain perfectly clear from the point resize.
The other option you have (in terms of hard resizing and maintain pixel sizes) is resizing by some larger number for both dimensions, such as 500%. That'll push it to 1600x1120, then you can Lanczos resize this down to 1440x1080 for a 1080p clip.
If you're going encode MKV, I'd probably just avoid AR correction altogether and just upscale via a percentage in nearest neighbor, then use mkvmerge to set the display dimensions to 4:3. Then it'll be stretched on playback to the AR.
It's worth noting that selecting the aspect ratio by right clicking the preview window is for the preview only and doesn't affect the output clip.
Guernsey wrote:
Asol, is the aspect ratio different for Genesis consoles or is it just the same?
Genesis uses 4:3. A good way to remind yourself is that if the console was intended for display on a CRT television, then it was intended for 4:3 display.
I'm not as active as I once was, but I can be reached here if I should be needed.
Hi Darth Marios,
In order to get a visually rich RAM watch like the one you are referring to, I created a "simple" C DLL. I then invoked the functions of that DLL from a Lua script.
In a C library, you can theoretically do anything. One of my entry points was creating a thread, which spawned a graphical window with SDL. Another entry point was writing the RAM data in shared variables so that the UI thread could display these values.
When first loading the script, I would launch the UI thread. At each frame update, I would send the library my variables.
Really that's the extent of it... Hope that helped.
Hi nitrovski! I really enjoyed your Spyro 3 tas :D
Anyway there's no tutorial about this process C DLL + lua script? An example maybe?
Im a bit noob, but i'd like to know those cool stuff.
I'm having a bit of difficulty with a video dump, specifically the 10bit MKV encode (the other two worked just fine). When I get to encoding the video, the following error comes up:
Feos said it's likely something to do with Bizhawk's N64 dumping as this is for the Banjo-Kazooie run recently submitted and to ask in IRC. I spoke to Spikestuff who encounted the same problem a while back with a run he encoded which was solved by RGamma. Unfortunately I can't stick around in IRC any longer, so can anyone here offer any insight or solution to the issue?
Maybe back then what Aktan suggested was better, but I did a test, looked at x264 code, and checked the result, and for N64 footage from Bizhawk that seems to be the only cause of this, we should be passing --timebase 1001/60000 for primary. I'll add this check to the package soon.
As a side note, my own build of x264 was 10 times smaller than what they provide. I'll do some testing and then maybe switch over.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
In Virtualdub do you change the aspect ratio after you setup the resize filter settings for the video you made?
If you're processing in Virtualdub alone, then you can do this at any stage but for the best quality output it's best to do it last. I'd resize each dimension to something larger (it doesn't have to be way over, just slightly bigger) than the 4:3 resolution you want using nearest neighbor, then I'd resize back down to the destination using Lanczos. You'll get even better clarity if you can avoid resizing either the width or height in this final step. I'll do my best to explain via some examples:
Assuming you have Genesis footage which is 320x224. You can point resize this by 300% to 960x672. From here, you can do a number of resizes to make it 4:3. You can Lanczos resize it to 960x720, which will expand the height or you can Lanczos resize it to 896x672, which will shrink the width. In both cases, one dimension remains untouched and will remain perfectly clear from the point resize.
The other option you have (in terms of hard resizing and maintain pixel sizes) is resizing by some larger number for both dimensions, such as 500%. That'll push it to 1600x1120, then you can Lanczos resize this down to 1440x1080 for a 1080p clip.
If you're going encode MKV, I'd probably just avoid AR correction altogether and just upscale via a percentage in nearest neighbor, then use mkvmerge to set the display dimensions to 4:3. Then it'll be stretched on playback to the AR.
It's worth noting that selecting the aspect ratio by right clicking the preview window is for the preview only and doesn't affect the output clip.
Guernsey wrote:
Asol, is the aspect ratio different for Genesis consoles or is it just the same?
Genesis uses 4:3. A good way to remind yourself is that if the console was intended for display on a CRT television, then it was intended for 4:3 display.
So this what I have to do in order to get the right size for my Genesis footage? I just need to make sure that get this thing right. I can resize the the footage using Nearest Neighbor and resize again in Lanzcos using the dimensions that you had suggested. Am I close?[/list]
What is a good software to convert from MKV to a format that can play on a DVD?
Also what is a good free software to burn the file to DVD, without a watermark?
Does anyone know how to get a 480p60fps video on youtube? I know TASVideos is one of the few channels ive even SEEN it working. Ive tried it with my retrotink 2x i just got, and while the video isnt out quite yet at time of this writing (its set to premiere), in the preview its showing just 480p(non 60) and its been an hour or so to process.
So I would like to know if there is a "trick" to get 480p60fps footage working on youtube.