It is currently Sat Nov 18, 2017 7:02 am

All times are UTC - 7 hours





Post new topic Reply to topic  [ 129 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7, 8, 9  Next
Author Message
 Post subject: Re: NESICIDE
PostPosted: Wed Nov 28, 2012 6:59 am 
Offline
User avatar

Joined: Mon Jan 03, 2005 10:36 am
Posts: 2981
Location: Tampere, Finland
If the text box returns the text with CR+LF, and then it's saved to a file opened in text mode, the LF will get converted to CR+LF on Windows, resulting in CR+CR+LF.

_________________
Download STREEMERZ for NES from fauxgame.com! — Some other stuff I've done: kkfos.aspekt.fi


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Wed Nov 28, 2012 1:38 pm 
Offline

Joined: Mon Jun 27, 2011 4:14 am
Posts: 27
Location: Lurker Cave
cpow wrote:
That's really strange...what do you have set for End-of-Line style in Environment Settings->Code Editor->Whitespace. Do you have "Force consistent" set?

Yep, it is set. I never changed a thing in that menu.


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Sun Dec 02, 2012 10:19 am 
Offline

Joined: Thu Nov 15, 2012 2:43 pm
Posts: 6
tepples wrote:
Have you ever made a simple game for the PC or Mac before?


not


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Sun Dec 02, 2012 10:50 am 
Offline

Joined: Thu Nov 15, 2012 2:43 pm
Posts: 6
FLAVIO wrote:
tepples wrote:
Have you ever made a simple game for the PC or Mac before?


not



make examples of a simple game to learn.


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Sun Dec 02, 2012 11:57 am 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
Version 1.035 (windows build only) is out.

ChangeLog:
1. Added mappers 21, 22, 23, 24, 25, and 26. No extra sound support yet on 24 or 26, although the registers are viewable in the Mapper Memory inspector.
2. Added turbo controller support. Thanks Eugene.S for the suggestion and OGR for the graphic.
3. Made an attempt at CR+LF line-ending correction based on Jsolo's bug report. This might need more work but I'm waiting on a new snapshot build from Phil to correct the problem with annotations and scrollbar height.

Depending on how quick things go in, next release will have sound support for mappers 24 and 26, and hopefully mapper 85 [VRC7].


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Sun Dec 02, 2012 1:20 pm 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
cpow wrote:
Depending on how quick things go in, next release will have sound support for mappers 24 and 26, and hopefully mapper 85 [VRC7].

Dang...already got the VRC6 audio working. Akumajou Densetsu sounds awesome as hell!

That was easy. Oh well. I guess I'll wait 'til at least tomorrow to make sure the Qscintilla annotation and CR+LF bugs get fixed before doing 1.036. :roll:


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Thu Dec 06, 2012 7:51 am 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
Version 1.036 (windows build only) is out.
Also, I hear hyarion is able once again to make OSX builds...

ChangeLog:
1. Added mappers 18, 19, 210.
2. Added sound to mappers 24, 26, and 19.
3. Fixed turbo controller issues reported by Eugene.S.
4. Updated to latest Qscintilla2 snapshot which fixes the annotations vs. scroll-bar height problem in mixed-mode C source files.

Just a general note...while implementing mapper 19 I thought I'd start implementing deep internal state inspection for things like the sound channels so the internal state of the sound channels could be seen. But then I decided that I'd hold off on that, since I don't know but I'd guess that nobody uses mapper 19 [Namco 106] as a homebrew dev platform. So, as a more general note I think what I'll do with the remaining mapper implementations -- the ones I don't even support yet, but I'm adding as time goes by -- is add support for viewing their *register* internal state [Debugger->Cartridge->Mapper Memory] but not necessarily their deep internal state. For an example of what I mean, load any MMC1, MMC2, or MMC3 game [or, indeed, tepples' mapper 28], open the Debugger->Cartridge->Information debugger, and select the "Internals" tab.

I'll gladly take requests for mapper support or deep internal state inspector capabilities for any mapper that anyone is using as a homebrew dev platform that I don't currently support or have deep internal state inspection for.

Let me know, here or in PM. Thanks.


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Thu Dec 06, 2012 8:12 am 
Offline

Joined: Sun Sep 19, 2004 11:12 pm
Posts: 19222
Location: NE Indiana, USA (NTSC)
cpow wrote:
I'd guess that nobody uses mapper 19 [Namco 106] as a homebrew dev platform.

A bunch of Japanese NSF composers apparently do, if by "106" you mean the common misnomer for 163. But then it's hypothesized that all of a channel's state is stored in the mapper's 128-byte SRAM.

(Side note: 128 byte SRAM? Was it prototyped with a RIOT pulled from an Atari 2600 out of frustration over the bad Pac-Man port? I wonder how many macrocells it'd take to implement N163 audio on a CPLD + SRAM.)


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Thu Dec 06, 2012 8:30 am 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
tepples wrote:
cpow wrote:
I'd guess that nobody uses mapper 19 [Namco 106] as a homebrew dev platform.

A bunch of Japanese NSF composers apparently do, if by "106" you mean the common misnomer for 163. But then it's hypothesized that all of a channel's state is stored in the mapper's 128-byte SRAM.

(Side note: 128 byte SRAM? Was it prototyped with a RIOT pulled from an Atari 2600 out of frustration over the bad Pac-Man port? I wonder how many macrocells it'd take to implement N163 audio on a CPLD + SRAM.)


Disch's mapper docs, 019.txt wrote:
========================
= Mapper 019 =
= + 210 =
========================

aka
--------------------------
Namcot 106
N106

That's what I mean...not sure where N163 comes from.

You are correct all the internal state is in the 128 byte SRAM. I was just saying that I hadn't yet put anything in NESICIDE to show that SRAM. If there's a user that wants it I'll add it.

You bring up a good point, though. I don't support NSF...yet. Nobody's asked. :|


Last edited by cpow on Thu Dec 06, 2012 9:32 am, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Thu Dec 06, 2012 8:50 am 
Offline

Joined: Sun Sep 19, 2004 11:12 pm
Posts: 19222
Location: NE Indiana, USA (NTSC)
I think the actual chip is marked 163, and 106 might have been a typo that got spread far and wide. Can anyone dig up the old forum discussion about 106 vs. 163?


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Fri Dec 07, 2012 2:54 am 
Offline
User avatar

Joined: Sat Apr 18, 2009 4:36 am
Posts: 259
Location: Russia
Cpow. Try to listen Akumajou Densetsu VRC6.
Tune1 - Beginning (without DMC channel)
Tune1 - Beginning (with DMC channel)
DMC is very bad.


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Fri Dec 21, 2012 12:49 am 
Offline
User avatar

Joined: Sun May 27, 2012 8:43 pm
Posts: 1311
tepples wrote:
I think the actual chip is marked 163, and 106 might have been a typo that got spread far and wide. Can anyone dig up the old forum discussion about 106 vs. 163?


I'll check my rolling thunder!

Image
Image

Aww.


Which carts aren't glop-tops?


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Fri Dec 21, 2012 1:06 pm 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6440
Location: UK (temporarily)
None of the N163-class ICs found in BootGod's database mention "106" at all. AFAICT, it's most likely entirely spurious, or maybe an internal code name that somehow leaked.

NesCartDB's PCB viewer: N163, N175, N340


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Mon Dec 24, 2012 12:30 pm 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
Happy Holidays! Enjoy this preview release of hopefully many more UI and project management enhancements to come, thanks mostly to contributions from JSolo [both in actual code and in feedback/idea exchanges].

Version 1.037 (windows build only) is out.

ChangeLog:
1. Updated to QScintilla2 version 2.7.0 release.
2. The UI is now "mode based". There is a "Coding mode" and a "Debugging mode". Coding mode is intended to free up the majority of the UI for space for code documents. Debugging mode is intended to remember the prior state of debugger windows. Coding mode is sort of like "show desktop" in Windows, I guess.
3. Project Browser now has an Open Items section for easier context switching.
4. Search (Ctrl+Shift+F) dialog has been moved into the Output Pane. Output Pane is hidden unless explicitly opened (with buttons accessible in the status bar), as opposed to having it annoyingly pop open.
5. Search bar (Ctrl+F) now includes replace functionality.
6. Files can be syntax highlighted as C or assembly based on their extension.
7. Double clicking on a symbol in the symbol watch window will open a memory window to its address.
8. Context menus for Project Browser redone.
9. Breakpoints can have an exclusive/inclusive mask set on the address and data fields. Exclusive is non-one-mask bits must be zero. Inclusive is non-one-mask bits are don't care.
10. Added EEPROM support to mapper 16.


Top
 Profile  
 
 Post subject: Re: NESICIDE
PostPosted: Sat Sep 14, 2013 9:12 pm 
Offline
NESICIDE developer
User avatar

Joined: Mon Oct 13, 2008 7:55 pm
Posts: 1049
Location: Minneapolis, MN
bunnyboy on #nesdev asked for a feature to breakpoint whenever an APU channel DAC hits a specified value.

NESICIDE v1.038 windows installer.

NESICIDE dependencies windows installer.

I had to split the package in two to fit google project page's 20MB upload limit...but it made a bit of sense to do so anyway because the dependencies don't change that much.

The breakpoint feature [not sure if anyone else will find it useful] is accessed selecting "APU Event" as the breakpoint type when adding a breakpoint, then selecting one of the events for DAC value, then providing the DAC value you are wanting to break on.

Please note...this build includes a Windows version of the Qt FamiTracker port that I've been working on. It is not yet properly integrated into NESICIDE thus the menu bar, tool bar, and status bar are a bit gunked up.

Tepples...if you're so inclined perhaps you could try the Windows FamiTracker Qt build in WINE? See if you get the same performance...


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 129 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7, 8, 9  Next

All times are UTC - 7 hours


Who is online

Users browsing this forum: fred and 8 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group