Jump to content

andyrkki

Members
  • Content count

    50
  • Joined

  • Last visited

  • Days Won

    1

andyrkki last won the day on January 29 2016

andyrkki had the most liked content!

Community Reputation

4 Bug

About andyrkki

  • Rank
    TRINITY

Country

  • Country
    Canada

Profile Information

  • Favourite Set
    CC1

Recent Profile Visitors

614 profile views
  1. Other puzzle game recommendations

    Just wondering: anyone here tried out the game I mentioned in the first post? I'd be very curious to hear what experienced CC players think of it in particular, and if it matches my view that it's just about the only puzzle game with fundamentally different gameplay from CC that has anywhere near the potential it did back in the day... or would if it had a level editor, that is.
  2. Call for CC2LP1* Level Pack Submissions

    I see - did you edit the first post here? Otherwise I must have missed that... Regardless, if what @Ihavenoname248 wrote in the other topic about the CC1 boots feature being added late is correct, we really should consider treating these two things the same way: either both CC1 boots and 9x9 viewports are allowed, or neither option is. (By the way, I apologize if I've taken this topic off track - I thought the decisions were final. Please feel free to split and/or merge posts as necessary.)
  3. Call for CC2LP1* Level Pack Submissions

    Is there a list of CC2 level viewport sizes somewhere? The wiki doesn't seem to have that information. May I ask which ones?
  4. CC2 Community Pack Survey

    Just to clarify my view on the set name: remember that CCLP1 was made first and foremost as a replacement set for the freely licensed Tile World. So if the final name does turn out to be CC2LP1 it would seem to permanently close the door to a CCLP1-type set in the future, which may well be needed as the official CC2 levels are no less copyrighted than the CC1 ones were.
  5. Call for CC2LP1* Level Pack Submissions

    @quiznos00 Why are 9x9 viewport levels allowed when there were numerous opinions against it in the feedback topic, and they clearly go against the spirit of a CC2 set? Yet at the same time you did decide to ban CC1 boots rules, which are not much more of a carryover from the original...
  6. UPDATED: "Native" MSCC on 64-bit Windows

    The "UPDATED" in the topic title refers to a much bigger update than what the first post might previously have suggested. It's now been... updated.
  7. Which CC game do you play?

    Mostly CC1, sometimes CC2 - but I would definitely play CC2 more if there were an option to buy it completely separate from Steam, even at a much higher price. It's ridiculous that the bloatware that is Steam needs to be installed to play a game from the late 90s...
  8. UPDATED: "Native" MSCC on 64-bit Windows

    Did you use the setup method from this topic, so that you simply click on CHIPS.EXE and it runs without you doing anything else? Also, are you using the original files that come with MSCC, with the original filenames (and modification dates from the early 90s)?
  9. UPDATED: "Native" MSCC on 64-bit Windows

    All of the files that come with MSCC should be in a single folder (i.e. the same one CHIPS.EXE is in).
  10. CC2 Community Pack Survey

    CC2LP2, not CC2LP1! 200 Absolutely not. 10x10 No limit, because this should be CC2LP2 and not CC2LP1. If a set like the latter is ever made, it should definitely have the 40x40 limit though. Anything that the official editor supports should be fair game. Anything that cannot be done with the official editor should be banned. There are some decent suggestions in this topic, but I've run out of patience with the quote handling mechanism here so I'll just leave this at that.
  11. Other puzzle game recommendations

    You should be aware that most people don't have Flash in their browser anymore, and basically nobody will have it in just a couple of years. I suggest remaking any Flash games in something that is widely supported, preferably HTML5.
  12. UPDATED: "Native" MSCC on 64-bit Windows

    Easiest way to get the path right: look at where the file "otvdm.exe" ended up after you extracted everything. So, if "otvdm.exe" sits under "C:\WineVDM" for example, both lines should read like this exactly: "MappedExeName"="C:\\WineVDM\\otvdm.exe" Though I find it strange that you just say it doesn't work, instead of posting the error message (it's virtually guaranteed there is one). Please do so if you still have problems after this.
  13. UPDATED: "Native" MSCC on 64-bit Windows

    Download the binary from that post (the link is at the bottom). Make sure you don't accidentally get the source code instead somehow. Unpack the archive into a folder of your choice. There is no installer, so this is where it will run from. Copy-and-paste this exact path. Open the file "install.reg" with a text editor (right-click -> Edit usually works) and replace the two obvious spots with the path you just copied. The only tricky part is that all backslashes in the path have to be doubled (just like in the examples you're overwriting), or it won't work. Open "install.reg" normally. Make sure it tells you the data actually got imported into the registry. From now on, 16-bit programs such as CHIPS.EXE should "just work", assuming you already have all the files they originally came with. (You'll notice a command prompt opening in the background - this is normal. You can minimize it, but if you close it the 16-bit program will close too.) Enjoy MSCC!
  14. UPDATED: "Native" MSCC on 64-bit Windows

    I'm just not really sure how to simplify it even more than I already did in my previous post here. Which part are you having trouble with exactly?
  15. UPDATED: "Native" MSCC on 64-bit Windows

    You should have downloaded the binary build at the bottom of the linked post... it doesn't need any "setup" to run MSCC, or anything else for that matter. You can unpack it and use it as-is if you want. But the readme file tells you how to make it so that 16-bit executables just work by clicking on them like any other program. After you unpack it, you edit the "install.reg" file - there are two spots where you need to put the path you unpacked the files to, using double backslashes like the example. After that you simply run the edited .reg file to import the changes into the system registry.
×