cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Nvidia Quadro FX1700 & Pro/E Wildfire 2.0 and 3.0

ocorten-2
8-Gravel

Nvidia Quadro FX1700 & Pro/E Wildfire 2.0 and 3.0

Just like Paul we also have issues with the FX1700 but here we have it
with Wildfire 2.0 and 3.0.

The Dell T3400 with an FX1700 and WinXP ProSP2 is a certified
combination, but we see strange graphical issues in shaded mode.

It's easy to reproduce: Turn off all misc graphics stuff like datums,
coordsys, axes, spin center, etc. and shade your model.
When only 3D shaded geometry is on screen now zoom. And there you are,
your entire model becomes one solid dark color.
Just as if someone turned out the light.

We tried several drivers including the latest from Dell and the latest
from Nvidia.
The driver version listed on the PTC supoort page is nowhere to be
found.
Also tried all sorts of config options. Nothing helped.

The only workaround for now is to always leave the spin center on. Then
it will not happen.

I'm having trouble convincing the PTC helpdesk in Europe that there is a
problem.
Since this is a certified workstation there is a problem in my opinion.

If anyone has the above configuration please try it out for yourself and
let me know if you see the same.



Olaf Corten - CAD / PLM Supervisor - Engineering
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
9 REPLIES 9

Greetings...

This is not strictly an issue with the FX1700 card. Although it is more
sporadic, I have seen the exact same issue on a Dell Precision Workstation
690 with the FX3450 card.



Not trying to muddy the waters, but thought that the additional information
would be useful to the troubleshooting efforts...



Take Care,

Mark



_____

We recently had an issue which at first appeared to be graphics card
related when the NVidia driver would either cause a lock-up (or even
sometimes a bluescreen) when attempting to view a model in ProductView.
After much testing, I came to the conclusion that two items could be to
blame (whether it's one or the other, or the combination of both, I'm not
sure).

1. Turning down hardware acceleration to slider-notch #2 under Display
Properties/Advanced Settings/Performance (which effectively disables
certain DirectX 3D acceleration features, but does not appear to impact
OpenGL performance). This is the workaround we chose to use.

2. Turning off the 2nd core (and any subsequent cores if using Quad core
processors) from within the BIOS.

I believe there is a compatibility issue with some display drivers and
their use of DirectX on Multi-Core Intel processors. I do not know if
this also occurs on the comparable AMD brands of processors. But the
blue-screen error seemed to point to these two items as the culprit.

You might try one of these methods to see if the problem somehow magically
goes away.
JOES
1-Newbie
(To:ocorten-2)

We recently purchased some Dell Presision 3400s with the FX1700 cards. I
can't reproduce Olav's or anyone else's issue. So far the problem we have
is flashing & it is not limited to Pro or Intralink 3.4.

We have a call currently open with PTC on the flashing issue & the fact that
the certified driver is unclear. The certified driver is called 6255 on
PTC's site & that equals nothing on nVidia's site. However, digging around
on Dell's site I found version# 6.14.11.6255 which must be the
certified driver. The IT guy that actually loaded this machine up used that
particular driver.
Found here:

Honestly, in our case we weren't seeing this issue in ProE, but rather
ProductView. And assigning it to one of the cores is actually how I
determined this, but I wasn't going to ask the users to launch the
application and then go to task manager and then manually assign them. I
also didn't want to go to the trouble of using wish to do this either.

There were only 2 users of ProductView and they are not ProE users,
whereas our actual ProE users are not using ProductView. We first saw
this when we received out new HP xw6400 workstations (ProductView machines
are 32 bit XP with 2 Gb of memory, and the ProE machines are 64 bit XP
with 8 Gb of memory). I did actually try running the ProductView test on
one of the 64 bit machines and it exhibited the same problem. I also saw
it on one of our Dell workstations (32 bit XP dual core machine), but not
on another Dell (also 32 bit XP, but non-dual core - older model).

Are these problems specific to the Dell system use of the FX1700 cards or
are people seeing similar problems with the cards in other systems such as
HP?

I'm currently specifying some new HP systems and that is the card I was
planning on using. I will avoid it if it has problems with ProE.

Regards,



Todd Stahlhut
CAE Administrator, Mechanical Design
Raytheon Technical Services Company LLC



Indianapolis, IN
317 306-2254 office
-








"Joe S."
<joedetroit@gmail <br="/> .com> To
Olaf Corten <->
04/04/2008 11:14 cc
AM -
Subject
[proecad] - RE: Nvidia Quadro
Please respond to FX1700 & Pro/E Wildfire 2.0 and 3.0
"Joe S."
<joedetroit@gmail <br="/> .com>








We recently purchased some Dell Presision 3400s with the FX1700 cards.I
can't reproduce Olav's or anyone else's issue. So far the problem we have
is flashing & it is not limited to Pro or Intralink 3.4.

We havea call currently open with PTC on the flashing issue & the fact
that the certified driver is unclear. The certified driver is called 6255
on PTC's site & that equals nothingon nVidia's site. However,digging
around onDell's site I found version#6.14.11.6255which must be the
certifieddriver.The IT guy that actually loaded this machine up used
that particular driver.
Found here:
kkja
1-Newbie
(To:ocorten-2)

We are having multiple issues with the NVIDIA Quadro FX 4600 running on
Dell 490 with 32 bit XP. These are dual processor quad core machines.
We are unable to find a video driver that will enable us to utilize the
3gb switch.



Some of our issues:

1. Flashing windows when they are refreshed or brought to the
front. This issue happens with and without the 3gb switch.
2. 3gb switch causes the display to dumb down to 800 x 600 and only
one monitor is supported (we all use dual displays).
3. For a while I could use the 3gb switch but it would eventually
become jumpy on spins similar to Win32. I could reboot multiple times
and it would eventually start working again. Now it is always jumpy so
I have the 3gb switch off. Which causes us to get the dreaded "out of
memory error" which is almost always followed by a Pro/E crash.



Our current workaround is to turn off the 3gb switch and to just enjoy
the screen flashing while avoiding seizures. 🙂



Jeff <><

See "Driver May Not Be Loaded with the /3GB Switch"
I used USERVA=2900 to resolve that issue

Support
Solution Details - TPI
Solution #
111330
Type
TPI
Created Date
01-Nov-2001
Last Updated
09-Feb-2007
Title
Increasing The Per-Process Memory Limit in Windows XP Professional
(32-bit) for Pro/ENGINEER via Microsoft's /3GB switch.
Details
Description
This document describes the PTC-supported Microsoft procedure for enabling
larger process memory addressing under Windows XP Professional (32-bit).
This procedure outlined in this document for Windows XP Professional
(32-bit) can be used with Pro/ENGINEER 2001 Datecode 2001440 and later.
This may be important for some very large assemblies and other situations
with high memory requirements.

32-bit operating systems are limited to a maximum of 4 gigabytes (GB) of
memory addressing. The actual amount of memory that a single 32-bit
application running on a 32-bit operating system can access is generally
less than 2GB and closer to 1.5GB (as reported by Windows Task Manager Mem
Usage). For an accurate measurement, monitor the xtop.exe process Virtual
Bytes counter with the Windows Perforamance Monitor (perfmon.exe). The
procedure outlined in this document will enable nearly 3GB to be used for
a single application.

64-bit operating systems do not have this same memory limitation and are
therefore a more permanent alternative for very large memory requirements.
Windows 64-bit architectures are supported beginning with Pro/ENGINEER
Wildfire 2.0 M160.

Before using this procedure, one should be aware that there are many
techniques within Pro/ENGINEER for reducing the memory requirements of
large assemblies, such as simplified representations. These techniques can
be found within the Pro/ENGINEER Help documentation, within this PTC TS
knowledge database, or through PTC Global Services (by contacting your
local PTC Sales representative). Using these techniques is usually a
preferable approach because they can significantly improve Pro/ENGINEER's
performance (that is, reduce the time to regenerate or perform other
operations).
Alternate Technique
64-bit operating systems do not have this same memory limitation and are
therefore a more permanent alternative for very large memory requirements.
Windows 64-bit architectures are supported beginning with Pro/ENGINEER
Wildfire 2.0 M160.
Additional Information
Procedure
-------------
The following describes the Microsoft's recommended procedure for
increasing the per-process memory limit to 3 GB.
Before starting, please read the following Microsoft knowledge base
articles:
"Driver May Not Be Loaded with the /3GB Switch"


For those with flashing issues, especially with Intralink check to see if you are running the Microsoft Intellipoint mouse driver. If you are this is most likely your culprit. We had to revert back to Intellipoint 5.2 or earlier (off the top of my head- I can confirm tomorrow morning) to get Intralink to not blink. We also had this show up in other apps. If you do not need the features of Intellipoint you can remove it and use the generic Windows driver.

Jeff Zemsky
  • -

Hello,

I had the same issue with Dell and FX1700 and have no problems in Proe
when setting the latest nvidia driver to 3D App - Default Global Settings
in . In ProductView I had to disable advanced rendering functions to get
it working. The only issue I have is that ProductView does not load all
.ol file and this will I let PTC support look at.

Hope it helps you.

Magnus Persson

Part of the Atlas Copco Group




"Vaughn McDaniel" <->
2008-04-04 18:08
Please respond to
"Vaughn McDaniel" <->


To
"Cool, Jeff" <->
cc
-
Subject
[proecad] - RE: Nvidia Quadro FX1700 & Pro/E Wildfire 2.0 and 3.0







See "Driver May Not Be Loaded with the /3GB Switch"
I used USERVA=2900 to resolve that issue

Support
Solution Details - TPI
Solution #
111330
Type
TPI
Created Date
01-Nov-2001
Last Updated
09-Feb-2007
Title
Increasing The Per-Process Memory Limit in Windows XP Professional
(32-bit) for Pro/ENGINEER via Microsoft's /3GB switch.
Details
Description
This document describes the PTC-supported Microsoft procedure for enabling
larger process memory addressing under Windows XP Professional (32-bit).
This procedure outlined in this document for Windows XP Professional
(32-bit) can be used with Pro/ENGINEER 2001 Datecode 2001440 and later.
This may be important for some very large assemblies and other situations
with high memory requirements.

32-bit operating systems are limited to a maximum of 4 gigabytes (GB) of
memory addressing. The actual amount of memory that a single 32-bit
application running on a 32-bit operating system can access is generally
less than 2GB and closer to 1.5GB (as reported by Windows Task Manager Mem
Usage). For an accurate measurement, monitor the xtop.exe process Virtual
Bytes counter with the Windows Perforamance Monitor (perfmon.exe). The
procedure outlined in this document will enable nearly 3GB to be used for
a single application.

64-bit operating systems do not have this same memory limitation and are
therefore a more permanent alternative for very large memory requirements.
Windows 64-bit architectures are supported beginning with Pro/ENGINEER
Wildfire 2.0 M160.

Before using this procedure, one should be aware that there are many
techniques within Pro/ENGINEER for reducing the memory requirements of
large assemblies, such as simplified representations. These techniques can
be found within the Pro/ENGINEER Help documentation, within this PTC TS
knowledge database, or through PTC Global Services (by contacting your
local PTC Sales representative). Using these techniques is usually a
preferable approach because they can significantly improve Pro/ENGINEER's
performance (that is, reduce the time to regenerate or perform other
operations).
Alternate Technique
64-bit operating systems do not have this same memory limitation and are
therefore a more permanent alternative for very large memory requirements.
Windows 64-bit architectures are supported beginning with Pro/ENGINEER
Wildfire 2.0 M160.
Additional Information
Procedure
-------------
The following describes the Microsoft's recommended procedure for
increasing the per-process memory limit to 3 GB.
Before starting, please read the following Microsoft knowledge base
articles:
"Driver May Not Be Loaded with the /3GB Switch"


Announcements