安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
I go to my bench machine in the garage which uses an NVIDIA GeForce GTX 750 Ti and installed the latest driver, 388.31. For those who're running NVIDIA hardware, try this driver for it DOES work.
Downloading 385.41 to test with my NVIDIA GF GTX 750 Ti-based box on my workbench in the garage.
I can't replicate the issue, but that might be because I'm running a GF GTX 750 Ti rather than a GF GTX 1050
ReLive is only a streaming program.
On your "nvidea" [sic] machine, which hardware are you using and which drivers? Trying to isolate it to whether it's a game engine or a driver issue. My AMD machines use three different cards spread over two generations, both are affected. I also have an NVidia machine which I cannot reproduce the issue on at all. Knowing your hardware (which NVidia card) and software (driver version) would help in seeing if I can reproduce the same problems you're observing.
NB: I don't work for any of the parties involved (i.e. AMD, NVidia, Idea Factory Int'l or Felistella); I'm just a persistent enthusiast who wants to see this game work just as much as anyone else does.
Here's something else to try:
If you have Re;Birth 1, 2 or 3, try them. If the problem is the same as the one plaguing us AMD folk, you'll see the same issue there. They all have two things in common with Sega Hard Girls: Felistella as a developer and use of the NVidia Cg toolkit.
Another thing to note is that the rest of the IFI Neptune back catalog is NOT affected.
In relation to my RX 570 (and maybe my RX 550 as well), here is the sequence of events and whether, if known (based solely on filenames here), the driver is WHQL-certified:
17.4.4 - Works - Non-WHQL - RX 500-series added as "RX 570 and RX 580" in release notes
17.5.1 - Works - Non-WHQL - Support now designated as "RX 500 series"
17.5.2 - Works - Non-WHQL
17.6.1 - Works - Non-WHQL
17.7.1 - Works - WHQL status unknown
17.7.2 - Works - WHQL
17.8.1 - Does not work - WHQL status unknown
17.8.2 - Does not work - Non-WHQL
17.9.1 - Does not work - Non-WHQL
17.9.2 - Does not work - Non-WHQL
17.9.3 - Does not work - Non-WHQL
17.10.1 - Does not work - Non-WHQL
17.10.2 - Does not work - Non-WHQL
17.10.3 - Does not work - Non-WHQL
17.11.1 - Does not work - WHQL
17.11.2 - Does not work - Non-WHQL
17.11.3 - Does not work - Non-WHQL
It's also worth noting that this also affects my three-year-old Radeon R7 250.
It'd be interesting to see whether something similar is in the NVidia world.
As for the NVidia side of my house, I have a GeForce GTX 750Ti in a bench machine in the garage. I have yet to see any issues with that card just yet, so the issue may only manifest itself with later chipsets.
Which card do you have? It's likely the card you have does not have any support in recent driver releases, with support for your card having been relegated to "legacy" status.
The ones I recently got were introduced earlier this year, and this timeline is based on the introduction of support for those cards to the present day.
However, for my R7 250, I haven't tried anything prior to 17.4.4 to see if anything breaks it. I can build up another system to see how that plays out.
Try downloading and installing 17.7.2 from this page[support.amd.com] and see if it works any better. It's still very much a recent card and is receiving support.