Author Topic: Project To Do for SP List  (Read 1559 times)

0 Members and 1 Guest are viewing this topic.

Offline Gent

  • PJ64 Dever
  • Hero Member
  • *****
  • Posts: 506
  • Karma: +100/-0
  • SuperFly Deving Guy
    • Project64 Website
Project To Do for SP List
« on: July 10, 2011, 12:11:55 pm »
I know Rad is going to/is doing a full list but i am just writing this down as i remember it.

Anything with a line through it will indicate fixed in any build that follows this post.


File Meta Section for About Ini Dilog:

[Meta]Homepage= < This example will result in a blank page where as:[Meta]< This example will result in a correct URL refferal.We need to allow for sub sites in all ini files as they are more common then ever.

Rumble (Force Feed Back)

Rumble for Jabo Direct Input in 1.6 is broken in the exe and just results in a constant (pulse like) rumble effect and forces the user to have to use Nrage.The fix in the 1.6 source is not actually a fix?This is an issue that needs adressing.


Jabo's DirectSound Issues

Sync Game To Audio Games Broke < Click Link To View
« Last Edit: August 26, 2017, 08:32:31 pm by Gent »
System 1 Specs:

OS:Windows 7 Professional 64Bit
CPU:Intel® Core™2 Quad Processor Q8400, 2.66 GHz, 1333 MHz FSB
System RAM:8GB Ddr2 Ram
Video:ATI Radeon HD 7470 PCI-E Graphics Card 1Gb
Sound:Creative Labs SB0460 X-fi Fatality Sound Blaster

System 2 Specs:

OS:Windows 7 Professional 64Bit
CPU:AMD Intel Quad Core i7 860 @ 2.80GHz Lynnfield 45nm Technology
System RAM:16.0GB Dual-Channel DDR3 @ 664MHz (9-9-9-24)
Video Card:512MB NVIDIA GeForce 310 Graphics
Sound Card:Realtek High Definition Audio

System 3 Specs:

OS:Windows 7 Professional 64Bit
CPU:AMD Essentials E1-2100 Accelerated Processor clock speed : 1.0 GHz
System RAM:Crucial 16GB  DDR3 RAM (1,333 MHz)
Video Card:AMD E1-2100 APU with AMD Radeon™ HD 8210 Graphics
Sound Card:Realtek ALC269Q-VB5-GR

Offline Witten

  • PJ64 Dever
  • Newbie
  • *****
  • Posts: 5
  • Karma: +0/-0
  • SuperFly Deving Guy
Re: Project To Do for SP List
« Reply #1 on: July 12, 2011, 11:28:40 pm »
Code: [Select]
  Main.c line 170case WM_COMMAND:       {
         char String[200];switch (LOWORD(wParam)) {case IDC_RDB_HOME:             {
               sprintf(String,"http://%s", RDBHomePage);                ShellExecute(NULL,"open",String,NULL,NULL,SW_SHOWNORMAL);             }
            break;case IDC_CHT_HOME:             {
               sprintf(String,"http://%s", CHTHomePage);                ShellExecute(NULL,"open",String,NULL,NULL,SW_SHOWNORMAL);             }
            break;case IDC_RDX_HOME:             {
               sprintf(String,"http://%s", RDXHomePage);                ShellExecute(NULL,"open",String,NULL,NULL,SW_SHOWNORMAL);             }
« Last Edit: July 12, 2011, 11:47:13 pm by Gent »

Offline RadeonUser

  • PJ64 Dever
  • Sr. Member
  • *****
  • Posts: 251
  • Karma: +1/-0
  • SuperFly Deving Guy
Re: Project To Do for SP List
« Reply #2 on: July 13, 2011, 12:12:22 am »
VS2010 build with Witten's modification.
Just don't add http:// to the files.

Offline RadeonUser

  • PJ64 Dever
  • Sr. Member
  • *****
  • Posts: 251
  • Karma: +1/-0
  • SuperFly Deving Guy
Re: Project To Do for SP List
« Reply #3 on: July 14, 2011, 05:25:37 pm »
I'm wondering how we all feel about the CIC-NUS-6105 algorithm that should, in theory, replace the pif2.dat file.
I would like to try to incorporate the algorithm into PJ64 and see if Banjo Tooie still runs sanely.

The second thing I'm wondering about is the permanent cheats.
While I do appreciate the need for them I've always felt uneasy about them.
I know Gent brings up that we should at the very least hide them better but I would like to stick to Witten's idea of not relying on them at all and fixing the core.
The latter is a lot more difficult so I don't know if it's possible to do but it would be entertaining to see if the core's issues can be fixed.

Aside from that I'm not aware of sufficient issues to compile a full list of issues.
I know there's small tweaks that Gent is suggesting but those can be handled on an individual basis.
For example, one that's not on here is to shove the configuration files into their own folder similar to how 1.7 handles things.
I think that's small enough to not mention on a list since it should just be changing the default directory's path and possibly adding some error checking.