raistlin
CAGiversary!
I'm new to PinballFX/2. Tonight when I tried to play speed machine or extreme etc on pinball fx2, it said import detection failed.
This process was really confusing because it throws out the "failed" message instead of telling you that you need to buy the classic tables right away like they would with any other table. So it made me think I needed to buy the original pinball FX game. So I did...and now it's looking like there's a completely separate purchase you can make directly for pinball fx 2 to get the classic tables. When I try to play speed machine or extreme etc on pinball fx2, it still says import detection failed. Yet I can play the original pinball fx fine.
I just wish they would remove the old pinballfx all together, because I feel like I got cheated out of updated tables now, and the convenience of having everything in one place. Not to mention possibly a higher all together score. According to the Zen website, this was some kind of Microsoft server issue that couldn't be resolved by removing the cache. But since the problem is so old, I'm afraid I may just be out the money. The problem was supposedly fixed back then, but is apparently back now.
This process was really confusing because it throws out the "failed" message instead of telling you that you need to buy the classic tables right away like they would with any other table. So it made me think I needed to buy the original pinball FX game. So I did...and now it's looking like there's a completely separate purchase you can make directly for pinball fx 2 to get the classic tables. When I try to play speed machine or extreme etc on pinball fx2, it still says import detection failed. Yet I can play the original pinball fx fine.
I just wish they would remove the old pinballfx all together, because I feel like I got cheated out of updated tables now, and the convenience of having everything in one place. Not to mention possibly a higher all together score. According to the Zen website, this was some kind of Microsoft server issue that couldn't be resolved by removing the cache. But since the problem is so old, I'm afraid I may just be out the money. The problem was supposedly fixed back then, but is apparently back now.
Last edited by a moderator: