Jump to content

Bmack36

Members
  • Posts

    1,133
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Bmack36

  1. You can install core 8 on an old Phoenix, but there is potential that your TV might not like it. Worst case is you revert to 7 if it doesn't work. Just don't mess with the service core and it will be fine. Not saying this is the case for cavern fighter but lots of CV games (even official ones) have issues that really shouldn't work or rely on dumb luck to work. One example is the Heist where it is reading in uninitialized ram and acting upon it when starting the game. Another example is Centipede where it is acting on the spinner input and the controller gets locked out of menu input due to the spinner being in a specific location (with stock CV and stock Super Action Controller)
  2. Looks to be a bug in the game to me. Once a fire button is pressed everything works fine and it no longer has the issue. After game over everything works properly in the menu as well. There is nothing different in the control section between Gen 1 and Gen 2. Loading up the controller tester shows no buttons are being pressed until they are physically pressed on the controller. Those are just the bootloader firmware versions. You would need to check the colecovision core version in the load cores screen or install cores screen. Just FYI don't install old cores on the Gen 2.
  3. There is a github issues page with exactly what you are looking for. It is linked in the first post and on the Collectorvision Phoenix webpage https://github.com/CollectorVision/Phoenix-Colecovision/issues
  4. This is a known issue with the 2600 core at the moment.
  5. No, the firmware fix is still in development. The suggested adapter is just a stopgap until the real fix in firmware. This adapter is cheaper and works for me: https://www.amazon.com/gp/product/B07KVRYWDF/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
  6. You don't need to update the service core at this time on old units. There is no real value to it until the TV compatability issues are resolved.
  7. I need to verify, but I think it was built with the new hardware settings, so it should work on both.
  8. This is a temporary measure until the firmware is fixed. It is purely an issue with the pixel clock in the colecovision core that needs to be adjusted to be closer to spec, but the resolution causes a rippling change throughout the core that just takes a lot to resolve. The adapter specified is different to some other similar looking scalars in that this one doesn't add an appreciable amount of lag. A different scalar (that looks similar) was HDMI to scart had so much lag, games were pretty much unplayable. You can verify the issue by pressing * and then 2 immediately after pressing the power button. This loads the 2600 core which has a different video output where the pixel clock is correct.
  9. To your original issue you can find more info here: https://github.com/CollectorVision/Phoenix-Colecovision/issues/1 Does it do the same thing when hooked directly to the TV instead of through the receiver? One solution is to get this adapter which fixes the unsupported video on my Samsung TV: https://www.amazon.com/gp/product/B07KVRYWDF/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1&fbclid=IwAR3aOmJ4kHvpCSFnk3T81CL50RvnfY96thHYOBp4Tzvk6Y7ycyXlfZ3wMDQ It says it is HDMI to composite, but it has HDMI passthrough which works on mine.
  10. This was in response to Zinister's post about flashing old service menu. The system were shipped with the latest version, but in this instance an old "incompatible" version was flashed which caused video to cut out
  11. Also there is no need to update the service menu on the second batch. If you "revert" a second batch phoenix to the service menu posted on the first page in the thread, the video will not work. The menu will still function but nothing on the screen. SO you will need to update blind by pressing # then 3. You should then see the led change to purple while updating and then back to the green. Service Core for Second Batch Phoenix(only needed if accidently flashed with previous service menu). There is no reason to update a first revision phoenix with this version. SERVICE.PHX
  12. The front sticker is all a part of the bottom assembly. You can take it apart without touching or moving the sticker.
  13. Yes the Avermedia Live Gamer Portable 2 Plus works with the current core. That is the one I use.
  14. Do you have any games with it or is it just the system?
  15. No, it was Richardthe7th and Itchy. In that thread Richardthe7th makes some critical snide remarks to Tony and then Itchy comes in to stand up for the developers and call out Richardthe7th(himself) for the bad remarks. He also made a jab at you for "stealing" MSX games.
  16. The CV core is currently only outputting 640x480 with a 25MHz pixel clock (which is why there is the tv compatibility issue and will resolved with the firmware update). The atari2600 core is 720x480 with 27MHz which has better compatability. I use the avermedia live gamer portable 2 plus and it has worked well. Someone on the Collectorvision Phoenix Facebook group found a cheap one that worked as well.
  17. Yes that project is still ongoing. The hope was to have it done, but it is not there yet. It will be released as soon as it is ready.
  18. Did you watch the whole video? You have to watch the start of the next game after it goes back to the title.
  19. Full playthrough of L'Abbaye des Morts (including secret easter egg at the end)
  20. Did you replace the C3 capacitor on your F18a CV? I think it needs to be changed to 10uF to delay startup so the F18a has time to startup
  21. The expansion module would be applicable for both units with the exception that the 2nd batch Phoenix boards wouldn't need the HDMI passthrough (you could just use the HDMI plug on the back of the phoenix.
  22. The "noise" isn't an issue with filtering. The issue is the potential difference and change between the ground of the power to the roller controller and the ground of the Phoenix. If you connect the ground of the roller controller to a ground on the Phoenix the issue goes away. This also resolves if you power the roller controller from the Phoenix as the grounds will already be at the same potential.
  23. Phoenix production Update: The Phoenix PCBs are in the process of being produced and we should be on track to ship out at the end of March. The issue that delayed production was due to sporadic control with the Roller controller. This turned out to have nothing to do with the board itself and instead was caused by the power to the roller controller. Even though it was getting the "proper" voltage, there was no common ground connection between the Phoenix and the roller controller, which caused noise in the signals and the position to jump around. The way to solve this is to use the Phoenix to power the roller controller. We are working on an expansion port adapter that will address some issues: -On Rev1 Phoenix's there would be an HDMI passthrough to resolve the HDMI power backfeed issue -There would be some dipswitches to set the default scanline, sprite limit, and encoder disable. The encoder disable switch would be set so that custom controllers do not cause games to lock up or have other issues by disabling the controller port Pin 7 and Pin 9 inputs -Roller controller Power port- This would provide a port that the power connector for the Roller controller could plug into so no external power would be needed. This adapter is still just in the Proof of Concept Phase but something we are looking to release at a later date.
  24. We are still on track for Q1. Most likely end of March.
×
×
  • Create New...