547 replies to this topic

[Philsan]

jwierer, on Thu Feb 10, 2011 12:48 PM, said:

Philsan, on Thu Feb 10, 2011 12:34 PM, said:

I think a DPC+ toggle in sprite editor or in VbB editor would be the best solution.

Sure but in the meantime I am not sure why flipping the bits from upside down to right side up doesn't work in the interim.

I agree.
The most important feature to start immediately to design sprites is to have non-square 2:1 pixels in the editor.

Edited by Philsan, Thu Feb 10, 2011 1:53 PM.

[SuperNESFreak]

Me again.

I'm running vbB on an XP machine now, and the program freezes when I try to compile. It says 'compiling c:\batari\blah blah blah' but it doesn't get any further.

On my Vista machine the compile takes all of half a second. What's going wrong?

Thanks.

[jwierer]

More than likely it's not vbB but that bB isn't configured correctly and nothing is happening. vbB will just wait for the compilation to complete. Assuming you're using the latest, right click on the project and launch the commandline. See if you are able to manually compile that way. If that doesn't work then the problem is actually with your bB installation.

-Jeff

[SuperNESFreak]

jwierer, on Fri Feb 18, 2011 10:26 AM, said:

More than likely it's not vbB but that bB isn't configured correctly and nothing is happening. vbB will just wait for the compilation to complete. Assuming you're using the latest, right click on the project and launch the commandline. See if you are able to manually compile that way. If that doesn't work then the problem is actually with your bB installation.

-Jeff

I think my config is correct.

The message reads:

Compile started at 18/02/2011 16:35:45
Compiling C:\vbB\projects\CosmicChaos\game.bas

Nought after that.

Emulator, compiler and alternative compiler are all there.

Sometimes it doesn't lock up.

Confused.

[RevEng]

Jeff is right. You need to try compiling it from command-line.

There's at least one condition I know that will cause bB to hang during the compile attempt (dividing by zero) and there could be more.

Edited by RevEng, Fri Feb 18, 2011 10:56 AM.

[SuperNESFreak]

Hrm.

Probably that my PC is buggered up majorly. I hope to get a Mac soon (treason! treason!) and I saw people were requesting a Mac release, is this feasible/possible/going to happen? Could you pret-PC froze again-Could you post the source so that it could be compiled for Mac or something?

What did you write this in, anyway?

[jwierer]

SuperNESFreak, on Mon Feb 21, 2011 12:24 PM, said:

Hrm.

Probably that my PC is buggered up majorly. I hope to get a Mac soon (treason! treason!) and I saw people were requesting a Mac release, is this feasible/possible/going to happen? Could you pret-PC froze again-Could you post the source so that it could be compiled for Mac or something?

What did you write this in, anyway?

Not portable to Mac, never going to happen. Did you confirm that you can compile from the commandline? If you're not able to compile at the commandline then it's not a problem with vbb, just means bB was never installed correctly.

-Jeff

[jwierer]

Philsan, on Thu Feb 10, 2011 1:15 PM, said:

The most important feature to start immediately to design sprites is to have non-square 2:1 pixels in the editor.

I posted a "test" version of vbB that includes some new support for the DPC+ kernel. You can download and play with it from my blog. There are a few other features I've added as well such as a integration with bblint, bookmarking, and a titlescreen kernel wizard. When I get a chance I'll add some additional information there on how those work.

-Jeff

[SuperNESFreak]

Okay, last time. I promise. Hopefully. Maybe. Possibly.

Well, I just installed Windows 7 (horray!) and now there are error messages popping up half of the time. A couple of things that I don't see why Batari is complaining about.

 if player1x !== player0x && player1y> 5 then player1y = player1y - 1 <-- This line is fine.
 if player1x > player0x && player1y = 5 then player1x = player1x - 1 <-- VbB complains here.
 if player1x < player0x && player1y = 5 then player1x = player1x + 1

Another problem which asks me to ignore or quit the program immediately.

Quote

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: StartIndex cannot be less than zero.
Parameter name: startIndex
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at VisualbB.mainIDE.colorThisLine(RichTextBox rtc1, Int32 myLineStart, Int32 myLineEnd, Int32 LocLine, Boolean isColored)
at VisualbB.mainIDE.Compile(String filePath, String filename, String sourceDirectory)
at VisualbB.mainIDE.CompileToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VisualbB
Assembly Version: 1.0.0.554
Win32 Version: 1.0.0.554
CodeBase: file:///C:/Batari/VisualbB.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

And here a message from DASM, I think.

Quote

2600 Basic compilation failed!
LINE -->Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Batari\projects\crazycrane>preprocess <default.bas >34cef53b-d114-4785-9ca4-2b0cc7611ac3.tmp

C:\Batari\projects\crazycrane>2600basic -i <34cef53b-d114-4785-9ca4-2b0cc7611ac3.tmp %bB%
game
.L00 ; set tv pal : set romsize 2k

.menu
; menu

.playfield:
; playfield:

.XXX.XXX.XXX.XXX.X.X.......X.....
; XXX.XXX.XXX.XXX.X.X.......X.....

.X...X.X.X.X...X.X.X.......X.....
; X...X.X.X.X...X.X.X.......X.....

.X...XX..XXX..X...X........X.....
; X...XX..XXX..X...X........X.....

.X...X.X.X.X.X....X........X.....
; X...X.X.X.X.X....X........X.....

.XXX.X.X.X.X.XXX..X........X.....
; XXX.X.X.X.X.XXX..X........X.....

..........................XXX....
; .........................XXX....

.XXX.XXX.XXX.XX..XXX.....XX.XX...
; XXX.XXX.XXX.XX..XXX.....XX.XX...

.X...X.X.X.X.X.X.X......XX...XX..
; X...X.X.X.X.X.X.X......XX...XX..

.X...XX..XXX.X.X.XXX...XX.....XX.
; X...XX..XXX.X.X.XXX...XX.....XX.

.X...X.X.X.X.X.X.X......XX...XX..
; X...X.X.X.X.X.X.X......XX...XX..

.XXX.X.X.X.X.X.X.XXX.....XX.XX...
; XXX.X.X.X.X.X.X.XXX.....XX.XX...

.L01 ; COLUPF = 14

LDA #14
STA COLUPF
.L02 ; COLUBK = 0

LDA #0
STA COLUBK
.L03 ; if joy0fire then goto gamestart

bit INPT4
BMI .skipL03
.condpart0
jmp .gamestart

.skipL03
.L04 ; drawscreen

jsr drawscreen
.L05 ; goto menu

jmp .menu

.gamestart
; gamestart

.L06 ; player0x = 80

LDA #80
STA player0x
.L07 ; player0y = 40

LDA #40
STA player0y
.L08 ; player0color = 32

LDA #32
STA player0color
.L09 ; player1x = 5

LDA #5
STA player1x
.L010 ; player1y = 5

LDA #5
STA player1y
.L011 ; player1color = 12

LDA #12
STA player1color
.game
; game

.L012 ; player1:

LDA #<playerL012_1

STA player1pointerlo
LDA #>playerL012_1

STA player1pointerhi
LDA #7
STA player1height
.L013 ; if player1x = = player0x then player1y = player1y + 2

LDA player1x
CMP =
BNE .skipL013
.condpart1

C:\Batari\projects\crazycrane>@exit

Does anyone have any idea what's going wrong? I really want to use this program and it seems just recently it's dying a horrible death on my PC.

EDIT: Another error message that stops me from using the Music Editor as soon as I try to open it:

Quote

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at VisualbB.SoundLib.vbBSoundLib..ctor()
at VisualbB.DialogMusic..ctor()
at VisualbB.mainIDE.MusicEditorToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VisualbB
Assembly Version: 1.0.0.554
Win32 Version: 1.0.0.554
CodeBase: file:///C:/Batari/VisualbB.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
VisualbB.SoundLib
Assembly Version: 1.0.0.1
Win32 Version: 1.0.0.1
CodeBase: file:///C:/Batari/VisualbB.SoundLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Edited by SuperNESFreak, Sat Feb 26, 2011 9:52 AM.

[jwierer]

Actually I think you're first line is incorrect. I believe you want the <> operator

  if player1x <> player0x && player1y> 5 then player1y = player1y - 1

For the crashes, don't just send the dump. Please send the steps to reproduce it. On the Music editor, I am at a loss. It's as if it's not detecting the .dlls, assumming they are in the directory.

-Jeff

[SuperNESFreak]

jwierer, on Sat Feb 26, 2011 10:37 AM, said:

Actually I think you're first line is incorrect. I believe you want the <> operator

  if player1x <> player0x && player1y> 5 then player1y = player1y - 1

For the crashes, don't just send the dump. Please send the steps to reproduce it. On the Music editor, I am at a loss. It's as if it's not detecting the .dlls, assumming they are in the directory.

-Jeff

What does the <> operator do?
To reproduce the crash, just open the Music Editor.
Also, Windows 7 is getting all huffy about vbB and it never saves settings etc. I don't want to turn UAC all the way off, is there a way around this?

[RevEng]

SuperNESFreak, on Sat Feb 26, 2011 11:08 AM, said:

What does the <> operator do?

The <> operator is bB's logical "not equal to" operator.

!== isn't valid bB syntax. ! is the "not" operator, but it only works on booleans (e.g. if !joy0up then ..., if !switchselect then ..., etc.) not on other operators.

[jwierer]

SuperNESFreak, on Sat Feb 26, 2011 11:08 AM, said:

To reproduce the crash, just open the Music Editor.
Also, Windows 7 is getting all huffy about vbB and it never saves settings etc. I don't want to turn UAC all the way off, is there a way around this?

I honestly think you have something else running that is interfering such as anti-virus, spyware, or other that doesn’t trust the application. I personally run with UAC off, but you could also just right click run as administrator if you want to grant it full privileges. I can confirm, as with others, that it runs fine on Windows 7 32-bit and 64-bit. I assume you’re not on some netbook with insufficient memory?



For our code problems you should probably start a new thread.

-Jeff

[SuperNESFreak]

Turned off UAC, still doesn't remember settings.
Running a desktop PC with 2GB of ram. (built with my own two hands, </brag>)
Using Microsoft Security Essentials.

[jwierer]

SuperNESFreak, on Sun Feb 27, 2011 7:21 AM, said:

Turned off UAC, still doesn't remember settings.
Running a desktop PC with 2GB of ram. (built with my own two hands, </brag>)
Using Microsoft Security Essentials.

For your Music Dialog error I believe it either cannot find, or you have the incorrect version of these

irrKlang.NET.dll verison 1.1.0.0 date 2/17/2010
ikpMP3.dll version 0.0.0.3 date 2/17/2010

Other than that I am out of ideas what could be wrong with your machine.

-Jeff

[jwierer]

I posted another test build to my blog. This one includes instructions on how to use the Title Screen Wizard which simplies the process of creating high resolution title screens using RevEng's titlescreen kernel. You still need to create the graphics in a seperate graphics editor, but this should expedite the process of generating the bit code, assembly files and a sample .bas file. The post includes instructions on creating a basic title screen, though it can be used to create a title screen with a scrolling, animated, or mutli-colored image. I'll post some additional how to steps when I have a chance.

-Jeff

[jwierer]

In case anybody is playing with the test release, I posted a couple tutorials on how to create a scrolling and animated titlescreen using visualbB.


(You'll need to click to view as an animated gif)

-Jeff

[Philsan]

Jeff,
when I use bBlint (with new versions of bB and VbB) on my program "L.E.M. (2010) (Filippo Santellocco) (PAL50).bas" I get this message:
[08.03.2011 13:52:02] bblint found the following errors in L.E.M. (2010) (Filippo Santellocco) (PAL50).bas
ERROR: couldn't open file "D:\Filippo\Emulatori\AtariVCSbB\VisualbB_1.0_Build_557\l.e.m."
Exiting...
If I rename it to "test.bas" no problems.
I think it is a problem of blank spaces in filenames.
Mike told me it should not be a problem related to his program.

[jwierer]

Philsan, on Tue Mar 8, 2011 9:02 AM, said:

Jeff,
when I use bBlint (with new versions of bB and VbB) on my program "L.E.M. (2010) (Filippo Santellocco) (PAL50).bas" I get this message:
[08.03.2011 13:52:02] bblint found the following errors in L.E.M. (2010) (Filippo Santellocco) (PAL50).bas
ERROR: couldn't open file "D:\Filippo\Emulatori\AtariVCSbB\VisualbB_1.0_Build_557\l.e.m."
Exiting...
If I rename it to "test.bas" no problems.
I think it is a problem of blank spaces in filenames.
Mike told me it should not be a problem related to his program.

Thanks for reporting the problem. The way I use bblint, I have to take the active code in the code editor and write it to temporary file and shell out so bblint can check it. I do this because I can't assume the programmer wants to save the active code using the actual name as I may be overwriting good code with bad code! The problem is I use a random guid and append it to the actaul name. If the existing file path is quite long, as yours is, you hit an argument limit in .NET. when a commandline process. I figured out a workaround and subseqent releases won't have this problem. For now if you want to keep the long name, then put it in a shorter folder name and that should fix the problem. I should have another test build out this week(end) which will add more support for the latest bB1.1 beta.

-Jeff

[SpiceWare]

Are you sure it's the length? Looks like it's the space in the filename that's causing the problem. Do you have the filename parameter wrapped in quotes?

[Philsan]

SpiceWare, on Tue Mar 8, 2011 10:34 AM, said:

Are you sure it's the length? Looks like it's the space in the filename that's causing the problem. Do you have the filename parameter wrapped in quotes?

You're right.
Filename "test.bas" works.
Filename "te st.bas" doesn't work.

[jwierer]

Philsan, on Tue Mar 8, 2011 11:41 AM, said:

SpiceWare, on Tue Mar 8, 2011 10:34 AM, said:

Are you sure it's the length? Looks like it's the space in the filename that's causing the problem. Do you have the filename parameter wrapped in quotes?

You're right.
Filename "test.bas" works.
Filename "te st.bas" doesn't work.

While investigating the length issue, I actually added the quotations at the same time. So both should not be an issue in the future.

-Jeff

[SpiceWare]

Cool - I've run into that problem before when shelling out commands via .Net. The max path in WIndows 260, which is why I didn't think the problem was the length.

[jwierer]

SpiceWare, on Tue Mar 8, 2011 4:29 PM, said:

Cool - I've run into that problem before when shelling out commands via .Net. The max path in WIndows 260, which is why I didn't think the problem was the length.

When using startInfo you can add a working directory and arguments property. It appears the arguments property is one that has a length limitation. Working directory doesn't appear to have any problems with lengths or quotes...

-Jeff

[jwierer]

I posted my last tutorial on how to create a multi-colored title screen in bB using visualbB.

-Jeff