-
Posts
5120 -
Joined
-
Last visited
-
Days Won
37
Content Type
Profiles
Forums
Events
Downloads
Store
Articles
Everything posted by headkaze
-
[APPLICATION] VJoy Virtual Joystick Driver v1.2
headkaze replied to headkaze's topic in User Projects
VJoy Virtual Joystick Driver v1.2 released! - 2 Joysticks - 8 Axes with a range of -32768 to 32767 - 32 Buttons - 4 POV's VJoy SDK v1.2 is now available for using VJoy in your own applications. There are many real world applications using VJoy right now such as a Steel Batallion Controller, replacing axes for Flight Simulator, head tracking, using Wiimotes and Kinect to control games or even to interface with robots. Some of the things people are using VJoy for are pretty amazing! Check out the new VJoy SDK v1.2 which includes source code to control the drivers in languages such as C++, C#, VB.NET, Delphi and VB6. Download VJoy SDK v1.2 -
I'm glad to hear that, It certainly helps to get into good habits Yes Application.StartupPath is definately the way to go for a Form based application. For dll's (GX plugins) and console apps the one I mentioned works well. It's a good habit to get into. That is defined as "\r\n" but on some systems it will be "\n" or "\r". Environment.NewLine maintains compatibily for these systems. It's quicker to read everything into memory and then processing the data. I just like how the File class makes it nice and easy. For creating a text file I use a List<string> textList then textList.Add() to it. You don't even need to add the newline characters. Then just call File.WriteAllLines(textList.ToArray()). That's interesting as .NET Reflector (which I used to peek at your code) converts it to a goto statement. But the Exit While is definately the preferred way despite what it compiles to.
-
Nice work Adultery. Just a few suggestions (you can take them or leave them). - Don't use Directory.GetCurrentDirectory() because the current directory isn't necessarily the executable's folder. Use Path.GetDirectoryName(this.GetType().Assembly.Location) instead. - Rather than creating a folder by appending strings use Path.Combine. Eg. Path.Combine(Path.GetDirectoryName(this.GetType().Assembly.Location, "history.dat"). If you ever run your code using Mono the folder separator for Windows is different on Linux based machines. - For the same reason use Environment.NewLine instead of "\r\n". - Rather than use StreamReader consider the helper class File. Eg. File.ReadAllLines(). - Rather than using "goto" you can use "break" to break out of a loop or "continue" to continue a loop (VB.NET equivalents would be Exit For/Exit While/Exit Do and Continue)
-
Probably a silly question but when you upgraded to VS 2010 did you make sure you were still compiling for x86?
-
Can you do an Alt + Print Screen of the error message?
-
[PLUGIN] UltraStik plugin 1.22 update to support ServoStik
headkaze replied to headkaze's topic in User Projects
Well actually I could have added support before the joystick's were released because I write the drivers for Ultimarc PS I'm talking with Andy about giving away a pair of ServoStik's as prizes. So stay tuned -
Tapatalk is great on an iPad.
-
The support is added via my UltraStik plugin from the Plugin Manager. It's now posted it in the User Projects area and should be available in the next release of GameEx.
-
Here is the PlugInUltraStik updated to support the ServoStik. I've also added an "Edit Configuration" button which will open PlugInUltraStik.ini for editing. This includes the latest PacDrive.dll which should overwrite the current one in GameEx's plugin folder. NOTE: This plugin will be available in the next release of GameEx so you should not need to download it here. PlugInUltraStik.zip
-
It will only take a few minutes to add support for it. Stay tuned.
-
I just got RickRoll'D
-
Here is a video review of the game [media=]
-
Yeah I thought so.. I should probably have read the whole post lol. Anyway I appreciate the help Adultery.
-
There were a few issues with your settings but I did manage to get it working. I've attached images showing the main settings you need to set. Just to go over them briefly. - No need for verbose logging (I know you probably turned that on when you were having trouble) but more logging means more lag. - You need to set a layout file for "Mame Layout Sub". This is one of the most important things you missed. This is what is displayed on the secondary monitor. It can be a single layout or you can have it rotate between multiple layouts by having them end with a suffix (Eg. "Sub (0)", "Sub (1)" or in your case "Walker (0)", "Walker (2)" or for your single layout use "Walker"). Personally I think you should copy your "Walker.xml" layout file over "Sub (2).xml" and set your "Mame Layout Sub" to "Sub (0)" and then it will include your custom layout in a bunch of different layouts that show artwork, game info and other information on your secondary screen. Layouts are stored in the "Layouts" folder in the CPWizard main folder. - Make sure "Auto Show (On Game Start)" is disabled - Another important setting. Under Display options the Screen settings should be the same as what you're displaying MAME on. This is for the main CPWizard display (menu etc.) You can't have this the same as your sub screen display. This is the reason why the setting was being automatically turned off. - Turn on "Sub Screen" and set it to your secondary monitor. - The sub screen display is separate to CPWizard's main functionality that comes from a menu system. You have that turned off. If you want it back on go to the Data options and turn off "Show CP Only" and then put a tick on all the "Mame Data Options" you want to show on the menu (for now select them all so you can see what it can do). When Mame is running and you press pause (default 'p') it should minimize Mame and show a menu. If the menu doesn't show try setting the "Detect Pause" setting in Mame, Pause Options. You should probably also have "Send Pause" set aswell. Finally I discovered I had to actually quit CPWizard and launch it agian for it to work. I can't remember why that is but I guess it's because certain things need to happen on intialization. As you may tell it's been a while since I worked on CPW. Anyway after that it seemed to work for me. Let me know how you go
-
Okay post your CPWizard.ini and the layout you're using. Also post your mame.ini and let me know the version you're using.
-
Not sure why you can't find the option. Obviously I'm talking about a CPWizard setting unless I specify otherwise. Here is a screenshot.
-
Under MAME options do you have "Auto Show (On Game Start)" turned on?
-
I see that Adultery posted about the D3D version too. It's tough to debug these type of problems. The MAME window can be a bit of a pain to deal with. Can you try turning off the "Skip Disclaimer". Also try setting the switchres setting to "0" in mame.ini.
-
Sorry guys I have no idea what the problem is. Can you post your CPWizard.log file. Also have you tried using an older version of DirectX for MAME as suggested on the CPWizard website?
-
Sorry to hear that KRC. I hope that nail the bastards that did it too.
-
Adultery: How are you launching XPAdder? If you're using the Process class have you tried setting: process.StartInfo.WindowStyle = ProcessWindowStyle.Minimized; That way it should not steal focus or cause GameEx to minimize.
-
Golf is already in there
-
It may be on the cards (if you will pardon the pun lol) BTW We will be releasing an update in the near future with another game pack added. If you have a varition of solitiare you'd like to see included please post about it here.
-
Thanks for the support guys. If you can take the time to check it out and perhaps make a review on the App Store, like / tweet at the top of the website, it would be greatly appreciated!
-
Grats KRC