01-31-2009, 09:59 PM | #21 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Originally posted by Jim Sachs:
Sorry, I read "Right-click on the desktop" as "Right-click on the icon". It's been a long 72 hours - getting these bugs chased down, trying to implement the clock/calendar/logo system, and creating the new website.
That system might be off the bottom end of the chart, but I've got a weak old Sony Vaio that still runs MA3 at about 20 FPS. How much video RAM does your card have? However, tomorrow I'll try to dig up some old video card(s) to try in the machine to see what happens. Note 1: My suggestions are really aimed at "if it isn't going to work, then don't run". Note 2: This is of course NOT a FIRST-priority issue. But I think it needs to be sorted out before a "production version" is declared. Note 3: There's also a related installer issue - which I will tackle in the Installer thread. |
01-31-2009, 10:35 PM | #22 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
That old Vaio I mentioned only has a 32-meg video card (chip), but it is still able to use the HAL and not fall back to software rendering. Speed is poor - you can tell that the system is paging the textures - and there are occasional video hiccups. But it does run MA3 without errors, so it seems like your 32-meg card should, too. I'll be interested to see if swapping cards has any effect.
Jim Sachs
Creator of SereneScreen Aquarium |
02-01-2009, 12:30 AM | #23 |
Prolific/SereneScreen Developer
Join Date: Mar 2003
Location: Norwalk, CA
Posts: 513
|
I think 82810 does not support pixel or vertex shader.
It will pass DirectX and MA2.6 specs but will fail MA3. Jim, which Intel graphics card do you have? Edit: http://www.intel.com/support/graphics/sb/cs-014257.htm |
02-01-2009, 12:44 AM | #24 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
Intel 82915G.
MA3 uses Vertex Shaders, but not Pixel Shaders. Good catch, Edgar. That's probably the problem, but it would seem that the proper drivers would step in and take over for the shader. Some people have reported that this type of problem is fixed by new drivers.
Jim Sachs
Creator of SereneScreen Aquarium |
02-01-2009, 12:46 AM | #25 |
Prolific/SereneScreen Developer
Join Date: Mar 2003
Location: Norwalk, CA
Posts: 513
|
It looks like you have the lowest Intel card with Shader support.
|
02-01-2009, 10:48 AM | #26 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Originally posted by Jim Sachs:
Intel 82915G.
MA3 uses Vertex Shaders, but not Pixel Shaders. Good catch, Edgar. That's probably the problem, but it would seem that the proper drivers would step in and take over for the shader. Some people have reported that this type of problem is fixed by new drivers. Of course, how do you tell "Joe User" what to look for? |
02-01-2009, 10:54 AM | #27 |
Prolific/SereneScreen Developer
Join Date: Mar 2003
Location: Norwalk, CA
Posts: 513
|
I read somewhere but wasn't sure, that 82810 does NOT support multi-textures also.
|
02-01-2009, 11:09 AM | #28 |
Forum Administrator
Join Date: Dec 2000
Location: Rock Hill, SC
Posts: 10,939
|
Originally posted by Dale:
I checked to make sure I have the latest driver version from Compaq. However, that turns out to be a higher version than the latest driver version from Intel. I'll try that one later today or tomorrow.
Of course, how do you tell "Joe User" what to look for? So many variations on the same video card hardware are released with just minor changes that this table would be massive and impossible to maintain. Fortunately, there's always MA2.6. P.S. You may not be, but I'm really impressed with the support you're getting in this thread. The research into various video cards and the functionality that they offer.
"Journalism is printing what someone else does not want printed. Everything else is public relations." - George Orwell
"If voting changed anything, they'd make it illegal." - Emma Goldman |
02-01-2009, 11:16 AM | #29 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
I have a kludge built into the program to deal with cards that have no multi-texture capability. That's how I'm able to get it to work on my old Vaio and certain ATI cards. The fish don't look quite as realistic (the shading, especially), but the casual observer probably wouldn't notice the difference unless they saw a side-by-side comparison.
Jim Sachs
Creator of SereneScreen Aquarium |
02-01-2009, 11:43 AM | #30 |
Prolific/SereneScreen Developer
Join Date: Mar 2003
Location: Norwalk, CA
Posts: 513
|
Jim,
But if the driver and card does not support shaders, then the card is out of luck. Do you still plan to try to support it? |
02-01-2009, 11:57 AM | #31 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Originally posted by feldon32:
I don't see how the Aquarium could deal with this situation, short of having a table of all supported hardware.
So many variations on the same video card hardware are released with just minor changes that this table would be massive and impossible to maintain. Fortunately, there's always MA2.6. P.S. You may not be, but I'm really impressed with the support you're getting in this thread. The research into various video cards and the functionality that they offer. With respect to "dealing with" this issue, there are (in my view) two separate aspects: (a) how the simulation software deals with the issue, and (b) how Prolific deals with the issue. I think both parts have reasonable solutions. This thread is about part (a). And we're still doing diagnostics, but I believe that's just from intellectual curiosity. One aspect not already mentioned, is what to do if the user changes video cards to a new one that does not support MA3 requirements (after MA3 has already been installed). [Or, off-topic, uninstalls DirectX9.0c] I've made a suggestion about how to handle the part (a) issues - "simply" detect if MA3 isn't going to run properly, and don't run. [Of course, not really simple - but the alternative is to do something unpredictable like "black screen" or "blue screen"] ====================== I agree that a "massive out-of-date table" isn't appropriate as some of part (b). However, this thread may perhaps allow Prolific to more-correctly describe the video requirements. Clearly "Direct3D" isn't sufficient. I don't really expect a lot of people to read and analyze the requirements, but I am confident that Prolific wants them to be clear and comprehensive. For several obvious reasons. |
02-01-2009, 12:33 PM | #32 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
Edgar - no.
Jim Sachs
Creator of SereneScreen Aquarium |
02-01-2009, 03:49 PM | #33 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
OK, after about 2 hours of testing, I've nailed down what is happening with the builtin chipset (haven't tried another card yet, and maybe won't).
This chipset allows two screen resolutions (1024x768 and 800x600) with a standard monitor, and two color qualities (16-bit and 24-bit). [And several different refresh rates, which I didn't test - yet]. And I have 3 driver versions on hand - two Compaq and one Intel. I finally "got a clue" that indicated that I should test all of the permutations. Note that's 12 combinations to test, with reboots, etc. But I'll simplify the results. It's not directly the chipset. Either resolution (1024x768 or 800x600), at 24-bit quality, fails. Either resolution at 16-bit quality WORKS. (Well, "works" is sorta judgmental, but we expected that). The good news, for this particular issue, is that the test which produces the "Could not find any compatible Direct2D devices" message seems to be an exact discrimination. If the message appears when selecting MA3 as screensaver, MA3 will not run in any full-screen mode. (I have not yet tested it in windowed mode, so perhaps it's different with "start in windowed mode"? -- maybe back to the test bench?) Bottom line: if the test fails, don't let it run, and tell the user why. Footnote: it's obviously not exactly correct/sufficient to say it couldn't find a compatible Direct3D device - because the device never changed. |
02-01-2009, 05:10 PM | #34 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
Thanks for all the testing.
The term "Direct3D Device" has an exact meaning in the Microsoft lexicon. People tend to think of it as meaning hardware, but it's really the hardware/software/resolution/bit-depth combination that allows 3D to be displayed. If any part of the software or driver is missing or damaged, the Direct3D Device fails. I've tried to account for just about anything that could go wrong within the program, and instead of just locking up or crashing, I display Mircosoft's recommended bouncing box with text listing the error. If one of these tests fails, it returns an error code, which I run through a Microsoft program to convert it to human-readable text. So, if the message seems cryptic, blame them, not me. Maybe some day I'll have time to go through them all and replace some of these messages with my own wording, but that's about 30 years down on a very long list of things-to-do. I think what you are asking for is that the program not run AT ALL, or immediately shut down if it encounters an error. I'm not sure this is possible. Microsoft is pretty picky about these screenblankers being able to cover up sensitive information on a monitor. If someone leaves his desk at the DMV assuming that the screen blanker is about to come on, it's better if there's at least a black screen with a bouncing box than someone noticing that he'd been playing Solitaire.
Jim Sachs
Creator of SereneScreen Aquarium |
02-01-2009, 10:32 PM | #35 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Sorry to again make this "not fun", but I believe I have been unsuccessful in communicating, once again. Simply put, MA3 crashes in each of the three startup modes.
Originally posted by Jim Sachs:
I've tried to account for just about anything that could go wrong within the program, and instead of just locking up or crashing, I display Mircosoft's recommended bouncing box with text listing the error.
Originally posted by Jim Sachs:
I think what you are asking for is that the program not run AT ALL, or immediately shut down if it encounters an error. I'm not sure this is possible. Microsoft is pretty picky about these screenblankers being able to cover up sensitive information on a monitor. If someone leaves his desk at the DMV assuming that the screen blanker is about to come on, it's better if there's at least a black screen with a bouncing box than someone noticing that he'd been playing Solitaire. Yes, that's what I'm suggesting. But I'm never seeing a bouncing box with text. As you say, switching to some other screensaver would be an acceptable alternative. What I am seeing (in the previously described instances), when the screensaver starts up, is: A. Black screen - no logo. Followed in a couple of seconds with an hourglass. B. About 15 seconds later, the "standard" Microsoft dialog box that says "MarineAquarium3 Beta8 has encountered a problem and needs to close.", followed by the usual invitation to notify Microsoft. In my experience, that dialog box is never deliberately generated by program authors. =========== SECOND: the other 2 startup modes (click on the icon, and preview) - both also operate the same way. Black screen followed by "MarineAquarium3 Beta8 has encountered a problem and needs to close." So, in those two startup modes, you're dealing with the simulation, not the screensaver. ================= From an external (program behavior) viewpoint, it looks to me just like the program crashes. Any way it's started. You clearly have some sort of test that is (at least in the environment I'm testing) absolutely diagnostic. That test runs every time MarineAquarium3 is selected in the Screen Saver tab of the Display Properties dialog box is clicked. I suspect (hard to tell without seeing the code) that the test actually runs each time the MINI-Preview (in the Screen Saver pane) tries to start. That test currently just pops up a dialog box warning about the (claimed) absence of Direct3D. Clicking "OK" allows everything else to just go ahead and happen (for instance, clicking on "Apply" to select this as the default screensaver, regardless of the warning). [And the MINI-preview doesn't run and doesn't crash] But, as far as I can tell, that test is never run when starting MA3 by clicking on the desktop icon, OR by clicking on the Preview button on the Screen Saver panel, OR when the screensaver starts automatically. My suggestion is that perhaps you consider running that test for each of those three starting methods. (Perhaps it's really one place - I can't see the code, of course). If the test fails, do something intelligent at that point - either just pop up the "no Direct3D" dialog box, or (where appropriate) start some other screensaver. That will prevent MA3 from looking like it crashed (whether or not it did). However, there's at least one other issue that I'll detail later - this reply is already long enough, and perhaps it's helpful to make sure one issue is understood before we go on. Note: I'm just trying to make sure the issue is clearly understood. How/if it is fixed, is up to the software author. |
02-01-2009, 10:53 PM | #36 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
That's quite a post. I'll need to wait 'til morning to wade into it.
Jim Sachs
Creator of SereneScreen Aquarium |
02-02-2009, 10:53 PM | #37 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Originally posted by Jim Sachs:
That old Vaio I mentioned only has a 32-meg video card (chip), but it is still able to use the HAL and not fall back to software rendering. Speed is poor - you can tell that the system is paging the textures - and there are occasional video hiccups. But it does run MA3 without errors, so it seems like your 32-meg card should, too. I'll be interested to see if swapping cards has any effect.
Probably not what's happening, but it's worth asking. |
02-02-2009, 11:31 PM | #38 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
No, the old Vaio only has 16 and 32-bit available. The Aquarium runs at 9 FPS in 32-bit and 14 FPS in 16-bit. Like all my other machines, dithering makes the two modes virtually indistinguishable visually, so I always run everything in 16-bit.
Jim Sachs
Creator of SereneScreen Aquarium |
02-03-2009, 09:37 AM | #39 |
Banned
Join Date: Jun 2005
Location: Western Missouri
Posts: 960
|
Originally posted by Jim Sachs:
No, the old Vaio only has 16 and 32-bit available. The Aquarium runs at 9 FPS in 32-bit and 14 FPS in 16-bit. Like all my other machines, dithering makes the two modes virtually indistinguishable visually, so I always run everything in 16-bit.
I presume you've digested my reply #35. As others have indicated, simulation "features" are more important at the moment. I have one other set of problems that is related to this topic. Would you prefer that I describe it in this topic, or in a new topic? [Of course, I could save it for later posting - or never post it - but I prefer to get Beta-testing observations on the record, and move on] |
02-03-2009, 10:04 AM | #40 |
Developer
Join Date: Dec 2000
Location: Southern Oregon
Posts: 9,785
|
Unless they are trivial things to fix, hold off for now. I'm totally swamped.
Jim Sachs
Creator of SereneScreen Aquarium |
|
|
|