Known Issues: Recettear Demo

[Eclipse]

I would think that there's probably going to be more than that; a possible scenario would be that if the dialogue was closed, the same customer would immediately offer the same item again, unless there's some flag which states "this customer has already attempted to Do This Thing but was refused".

not much more than setting a variable, it's still a line of code, they have already that thing working for when you set a low price, they just need to don't make the customer angry (or at least less angry than when you offer 0)

[Capitalism]

Well, I'm not gonna cry bout it, especially since coding isn't what CF is supposed to do anyhow. But I don't think customers would offer same items repeatedly, that doesn't sound random enough to me.

[Eclipse]

yes it's not a great issue, it's just a bit weird because makes customers selling you stuff more annoying than useful

[merphle]

I, too, am having some severe framerate issues in the dungeon, on an Intel-integrated-video laptop (dxdiag below).

With the default configuration, in full-screen mode: In the shop, I'm getting a pretty consistent 35-40 fps. Outside the shop (menus; elsewhere around town) I'm getting a rock-solid 60 fps. In the Hall of Trials, I get a meager 5 fps. Two things are interesting about this, though:

1) Checking the lower three dungeon performance settings (simple models, no light processing, no fog) gets me up to about 30 fps in the Hall of Trials, and if I happen to find a long corridor that leads far away (three sections?) from any rooms, it jumps up to 60 fps
2) I have no framerate issues with Jade Way. I can uncheck all of the dungeon performance settings and set the frame limiter to 60, and it happily gives me a solid 60 fps. And yes, this strange performance divergence between the Hall of Trials and Jade Way is very repeatable.

I updated my video driver today hoping it would help, but alas.

Other than this, I'm having a lot of fun with the demo!

<dxdiag>
------------------
System Information
------------------
Time of this report: 8/28/2010, 22:41:03
       Machine name: [redacted]
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100427-1636)
           Language: English (Regional Setting: English)
System Manufacturer: LENOVO
       System Model: 1951WPX
               BIOS: Phoenix FirstBIOS(tm) Notebook Pro Version 2.0 for ThinkPad
          Processor: Intel(R) Core(TM) Duo CPU      T2500  @ 2.00GHz (2 CPUs)
             Memory: 2038MB RAM
          Page File: 921MB used, 3010MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode

---------------
Display Devices
---------------
        Card name: Mobile Intel(R) 945 Express Chipset Family
     Manufacturer: Intel Corporation
        Chip type: Intel(R) GMA 950
         DAC type: Internal
       Device Key: Enum\PCI\VEN_8086&DEV_27A2&SUBSYS_201A17AA&REV_03
   Display Memory: 224.0 MB
     Current Mode: 1024 x 768 (32 bit) (60Hz)
          Monitor: Default Monitor
  Monitor Max Res:
      Driver Name: igxprd32.dll
   Driver Version: 6.14.0010.4926 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 2/15/2008 13:12:06, 57344 bytes
</dxdiag>

[SpaceDrake]

Yeah, we're going to be updating the FAQ and sysreqs very soon, but I'll say this in advance: if you're using Intel Integrated graphics, expect very poor performance. You'll almost certainly have to use Reduced Processing Mode and several other things. I'm afraid that Intel's (piss-poor) implementation of certain graphics functions on their older graphics chips will simply bring the game to a near-screeching halt, and performance will still be fairly poor even with options turned down.

There's very little we at CF can do about this (and EGS is busy with Territoire), so I'm afraid Intel Graphics users will simply underperform. To be frank, though, we cannot possibly recommend an upgrade for people with such PCs enough. Intel chipsets vastly underperform even compared to the cheapest chipsets from Nvidia or ATI; if you are at all capable of upgrading your PC's graphics capability, we recommend you do so, not just for Recettear but for your computer performance in general.

[joshrl]

Yeah, we're going to be updating the FAQ

You must be allergic to actually doing that. 

[Insert quote here.]

[Insert remark here.]

[merphle]

Yeah, we're going to be updating the FAQ and sysreqs very soon, but I'll say this in advance: if you're using Intel Integrated graphics, expect very poor performance. You'll almost certainly have to use Reduced Processing Mode and several other things. I'm afraid that Intel's (piss-poor) implementation of certain graphics functions on their older graphics chips will simply bring the game to near-screeching halt, and performance will still be fairly poor even with options turned down.

Thank you for your prompt response. Let me reiterate that I have absolutely zero performance issues with the second dungeon (Jade Way), even with every performance-booster checkbox UNchecked; it's ONLY the first dungeon (Hall of Trials) that I have a problem.

I was hoping this might help you/EGS narrow down whatever it is about the Hall of Trials that's causing such a performance hit to us Intel Integrated folks. Aside from this one issue, Recettear makes for a fine laptop game, and I'd love to recommend it to a bunch of friends who have similar system specs. Would you at least be willing to forward this information on to your contacts at EGS?

Edit: Also, upgrading the video card on a laptop is impossible in most cases.

[Baughn]

I'm afraid that Intel's (piss-poor) implementation of certain graphics functions on their older graphics chips will simply bring the game to a near-screeching halt, and performance will still be fairly poor even with options turned down.

Would you be able to expand on this?

I've got a certain curiosity about driver implementations, but can't afford to buy a forest of computers to test on myself - and trying to find a decent overview of driver flaws is like searching for hen's teeth in an elephant graveyard.

[iviv]

I'm afraid that Intel's (piss-poor) implementation of certain graphics functions on their older graphics chips will simply bring the game to a near-screeching halt, and performance will still be fairly poor even with options turned down.

Would you be able to expand on this?

I've got a certain curiosity about driver implementations, but can't afford to buy a forest of computers to test on myself - and trying to find a decent overview of driver flaws is like searching for hen's teeth in an elephant graveyard.

I don't think its anything to do with the driver, more that the hardware is barely worth the silicone its based on :p

[SpaceDrake]

I don't think its anything to do with the driver, more that the hardware is barely worth the silicon its based on :p

Pretty much this. Earlier Intel integrated chipsets lack a few hardware features - particularly hardware transform and lighting, which is more important in the dungeons than may be initially apparent - which will simply cause Recettear to choke when it tries to do these things in software. The most recent offerings from Intel - their GMA HD silicon integrated into their various Core-i offerings, particularly on their newest Core-i offerings codenamed "Sandy Bridge", are actually competent enough to run many games without many problems (even Territoire, which is significantly more complicated, would run on that hardware). Earlier offerings like the GMA 900 so common from 2005-2007, though, will simply roll over when trying to render certain scenes in Recettear; I'm honestly not sure how much can be done about this.

[joshrl]

I don't think its anything to do with the driver, more that the hardware is barely worth the silicon its based on :p

Pretty much this. Earlier Intel integrated chipsets lack a few hardware features - particularly hardware transform and lighting, which is more important in the dungeons than may be initially apparent - which will simply cause Recettear to choke when it tries to do these things in software. The most recent offerings from Intel - their GMA HD silicon integrated into their various Core-i offerings, particularly on their newest Core-i offerings codenamed "Sandy Bridge", are actually competent enough to run many games without many problems (even Territoire, which is significantly more complicated, would run on that hardware). Earlier offerings like the GMA 900 so common from 2005-2007, though, will simply roll over when trying to render certain scenes in Recettear; I'm honestly not sure how much can be done about this.

Seems you were in a good state at that time!

I can only assume what's going on.

[potatochobit]

I am using an HT Omega striker with windows7 64
game also crashes soon as you start with Xear 3D and possibly virtual 7.1 shifter on
I disbaled them and everything seems ok so far

[Kriby]

Suffering crashes at seemingly random intervals after entering the halls of trials. First crash occured approx. two days gametime after entering, 3 replay attempts crashed almost immediately after exiting the halls of trials, and one final attempt crashed during the trials themselves. The sound stuttered for approx 3-4 seconds before the crash message, so I tried disabling hardware accelerated sound, but no change. The game seems to run indefinitely prior to the halls of trials.

Edit: Leaving the game on in the background crashes it after about 10 minutes, without entering the halls of trials. Strangely, the (first) attempt where I skipped no dialogue got me the furthest without crashing.

Edit #2: I noticed the error report included a bit about ffdshow.ax. I downloaded and installed FFDShow, since I hadn't installed any version of it previously and thought it might help. I've now made it all the way to merchant level 3 and the Jade Way dungeon without crashing.

Edit #3: Just confirming I could complete a playthrough after updating FFDShow. :)

------------------
System Information
------------------
Time of this report: 9/2/2010, 00:07:39
       Machine name: SHODAN
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: EP35-DS4
               BIOS: Award Modular BIOS v6.00PG
          Processor: Intel Pentium III (4 CPUs), ~2.8GHz
             Memory: 3582MB RAM
          Page File: 1684MB used, 18101MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode
    
---------------
Display Devices
---------------
        Card name: NVIDIA GeForce 9600 GT
     Manufacturer: NVIDIA
        Chip type: GeForce 9600 GT
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0622&SUBSYS_827F1043&REV_A1
   Display Memory: 1024.0 MB
     Current Mode: 1680 x 1050 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0012.5721 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 6/8/2010 01:57:00, 6300544 bytes
      WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 6/8/2010 01:57:00, 10531200 bytes
Device Identifier: {D7B71E3E-4562-11CF-AA65-73A200C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0622
        SubSys ID: 0x827F1043
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: *Huge chunk of text cut, pm if these are interesting*
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
      
-------------
Sound Devices
-------------
            Description: Realtek HD Audio output
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0885&SUBSYS_1458A002&REV_1001
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RtkHDAud.sys
         Driver Version: 5.10.0000.5672 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 7/24/2008 19:02:44, 4749824 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Full
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: Yes, Yes
   I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
               Registry: OK

[konzy]

Found a window that stayed on the screen.  When I was getting the training for the item suggestion portion, when the item page opened up, I skipped the training using esc and that window remained on my screen.  I fixed it by walking to a counter and selecting it.

[Rincewind]

If anyone with a Quadro has issues, try updating your graphics card drivers
I used to have loads of problems with games before I updated my Quadro drivers. As in, half the games I owned would crash on start or randomly die while I was playing it. Since the driver update, I don't have any issues

Some Quadro cards (my one for instance) don't have any recent drivers listed as compatible. I just downloaded one of the newer ones that listed other Quadro's of a similar age to mine and the drivers installed and worked, and they resolved all my problems!
Before that I tried the newest driver that did mention my graphics card, that fixed most of the games, but not all.

Recettear runs at a solid 60 fps all the time, all settings on max, on my Core 2 Duo / Quadro. The Quadro cards are functionally identical to the GeForces, in some cases the only difference is 1 extra resistor on the Quadro. They aren't "crappy for gaming" if you make sure you pick good drivers.

Incidentally, the Game Over screen seems to have a mildly annoying flickery effect - I think its intentional, but its a bit fast