don't click here


Discussion in 'Fangaming Discussion' started by MainMemory, Mar 31, 2010.

  1. Dario FF

    Dario FF

    Tech Support Hotline Tech Member
    Just a minor adjustment to improve how Sonic warps in the screen.

    You're just checking if Sonic goes < 0 to warp to the other side right? Wouldn't it be better to warp him at something like "< -width/2"? It feels a little weird when he goes around the screen, because you can see him disappear.
  2. FlameTheFox


    Dude, this is awesome! Reminds me of a Mini Mario widget released by Nintendo that walks around your Desktop and stuff, and you control it (flipping it) with your mouse.

    Can we remove the coins though? I wanted to know how it worked before when he was affected by the insides of the window.

    I'm really looking forward for Tails, and what do you think about making a Super Sonic mode? That would be cool. Maybe you have to collect 50 rings, or you could have emeralds scatter around your desktop. You just plainly click a button on the options.
  3. MainMemory


    Kate the Wolf Tech Member
    It seems like my computer has been fried, so I won't be able to work on this unless my computer makes a miraculous recovery or I get a new computer and transfer it from the old HDD.

    And I was right in the middle of making Motobug into an enemy too. :(

    FlameTheFox: I don't keep old versions of my programs around unless I host them on the wiki.
  4. That's disappointing, hopefully you can get it back up and running soon. Can't wait for possible Tails or Super Sonic mode, and especially placeable badniks!
  5. I have every version of the program you have released thus far if that helps.

    (I haven't deleted them, lucky me!)
  6. Phithpleis


    Nein Member
    Your location
    Current Project
    Code (Text):
    1. See the end of this message for details on invoking
    2. just-in-time (JIT) debugging instead of this dialog box.
    4. ************** Exception Text **************
    5. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DirectX.DirectInput, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
    6. File name: 'Microsoft.DirectX.DirectInput, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
    7. &nbsp;&nbsp; at WindowsZone.Controller.UpdateControllerData()
    8. &nbsp;&nbsp; at WindowsZone.Form1.Timer1_Tick(Object sender, EventArgs e) in C:\Users\Mike\Documents\Visual Studio 2008\Projects\WindowsZone\WindowsZone\Form1.vb:line 37
    9. &nbsp;&nbsp; at System.Windows.Forms.Timer.OnTick(EventArgs e)
    10. &nbsp;&nbsp; at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
    11. &nbsp;&nbsp; at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    13. WRN: Assembly binding logging is turned OFF.
    14. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    15. Note: There is some performance penalty associated with assembly bind failure logging.
    16. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    20. ************** Loaded Assemblies **************
    21. mscorlib
    22. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    23. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4200 (NetFxQFE.050727-4200)
    24. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    25. ----------------------------------------
    26. WindowsZone
    27. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    28. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version:
    29. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Users/Da%20Bratz/Desktop/WindowsZone/WindowsZone.exe
    30. ----------------------------------------
    31. Microsoft.VisualBasic
    32. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    33. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
    34. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/
    35. ----------------------------------------
    36. System
    37. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    38. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    39. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/
    40. ----------------------------------------
    41. System.Windows.Forms
    42. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    43. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    44. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/
    45. ----------------------------------------
    46. System.Drawing
    47. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    48. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    49. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/
    50. ----------------------------------------
    51. System.Runtime.Remoting
    52. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    53. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    54. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/
    55. ----------------------------------------
    56. System.Core
    57. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    58. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 3.5.30729.1 built by: SP
    59. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/
    60. ----------------------------------------
    61. Rat234
    62. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    63. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version:
    64. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Users/Da%20Bratz/Desktop/WindowsZone/Rat234.DLL
    65. ----------------------------------------
    66. ManagedWinapi
    67. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    68. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 0.3
    69. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Users/Da%20Bratz/Desktop/WindowsZone/ManagedWinapi.DLL
    70. ----------------------------------------
    71. System.Web
    72. &nbsp;&nbsp;&nbsp;&nbsp;Assembly Version:
    73. &nbsp;&nbsp;&nbsp;&nbsp;Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    74. &nbsp;&nbsp;&nbsp;&nbsp;CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/
    75. ----------------------------------------
    77. ************** JIT Debugging **************
    78. To enable just-in-time (JIT) debugging, the .config file for this
    79. application or computer (machine.config) must have the
    80. jitDebugging value set in the section.
    81. The application must also be compiled with debugging
    82. enabled.
    84. For example:
    86. <configuration>
    87. &nbsp;&nbsp;&nbsp;&nbsp;< jitDebugging="true" />
    88. </configuration>
    90. When JIT debugging is enabled, any unhandled exception
    91. will be sent to the JIT debugger registered on the computer
    92. rather than be handled by this dialog box.
    Even downloading the older version doesn't help. I think it's because of where I downloaded the DirectX files. It didn't tell where to download them, so I put the files in a new folder called C:\DirectX. Did I do it wrong?
  7. There should have been a setup.exe somewhere in that file.
  8. HeartAttack


    is a smug hipster, brah! Member
    How does this run for people? It's pretty awesome but runs kinda slow.
  9. SF94


    Tech Member
    Runs pretty smoothly over here. Specs:
    Intel Pentium 4, 2.4GHZ CPU--
    ... need I even say more? :v:

    But yeah, it runs pretty smoothly on both Windows 7 and Windows XP on this computer. (as long as I'm not doing much else, considering I don't have a dual core =<)
  10. MainMemory


    Kate the Wolf Tech Member
    It ran okay for me (.05 seconds per frame avg.). I know what the main problem is, it's drawing a bitmap the size of the whole screen every frame, but I don't know how to fix it. I tried giving each object its own form once, but that slowed it down even more because then it ended up creating a form for every open window every frame.
  11. HeartAttack


    is a smug hipster, brah! Member
    Hm...I'm running an E5200 @ 2.8ghz per core, 6gb PC2-6400, GeForce 9800GT (1gb, 650mhz). Perhaps it's the fact that I'm using 2 monitors (at 1920x1080 and 1280x1024), and the program draws at full screen across both monitors?
  12. Nibble


    Instead of refreshing an entire screen-sized bitmap, you could do something similar to dirty rectangles. For each object you could keep their old X/Y positions (their position in the previous frame) and when it comes time to draw something, you clear a sprite-sized rectangle at the old position, then draw the sprite at the new position. This way, you put a lot less load on the CPU depending on the number of on-screen objects.

    Either that or there's still WPF, though it is a bit much to learn compared to to WinForms/GDI+. Either way, I'm sure there's an efficient way to go about it.
  13. Been wondering what this topic is about for a while.
    This sounds really interesting and cool! I couldn't get it to work but I wasn't too fussed about why. Still sounds really fun!
  14. MainMemory


    Kate the Wolf Tech Member
    I could do that, however, it would cause the sprites to flicker when I clear the area where they used to be. I tried drawing the images onto the form directly, and it was about twice as fast, but it made everything flicker. Your method might make it less noticable, as it would only affect each sprite immediately before it's drawn, but it would still be there. As for WPF, it seems that I would have to add a control to the canvas for every object I want to draw, and if I'm doing that, I might as well try to give each object a form, or alternatively, a PictureBox. The only problem with that is that I would need to figure out a way to prevent it from making one for all the top level windows every frame.

    Cracker: I can't figure out why it doesn't work for you if you don't give me any information! :specialed:
    My first guess would be that you didn't install the directx runtimes. Maybe I could add something to catch that and just disable joypad support instead of crashing.
  15. ^ Oh I'm not to fussed about getting it to run that's why ^^ It's a really cool idea but I will rarely use it and it'll just take it space and ram (which I already don't have enough of most times!)
  16. ...I just thought of something EPIC.


    DO IT.
  17. DigitalDuck


    Arriving four years late. Member
    Lincs, UK
    TurBoa, S1RL
    That would truly be epic. Absolutely no idea how you'd get it to work, though.
  18. Aren't both these made in Visual Basic?

    Im thinking it would be a kind of level tester kinda deal.
  19. MainMemory


    Kate the Wolf Tech Member
    I had... considered offering to make an engine for that, but I would have to completely redo the collision for that to work (which would make it just like the games actually). The collision now does not allow for slopes, only rectangles, as I didn't find a need for slopes in this particular program.
    I was pretty much planning on making this into a more traditional fangame engine at some point, and if I did, I could probably support that program's level format.

    And yes, I'm using VB 2008, although it doesn't really matter unless the programs are going to be combined.
  20. I'll tell you one thing you could make slopes for...

    The Windows Orb. Its weird that it acts like a block...