| T O P I C R E V I E W |
| kklobe |
Posted - Dec 17 2007 : 09:28:04 AM
I'm having an error compiling the Spacewar sample from the XNA GS 2.0 starter kit with VA 1624 installed. This thread suggests some other VA users are having the issue as well:
http://forums.xna.com/36330/ShowThread.aspx
To replicate:
1) Install XNA Game Studio 2.0 (http://www.microsoft.com/downloads/details.aspx?FamilyId=DF80D533-BA87-40B4-ABE2-1EF12EA506B7&displaylang=en)
2) Create a new project based on the Spacewar Windows Starter Kit (2.0).
3) Try to build the solution. Should get an error in p1_pencil.fbx: Building content threw InvalidOperationException: The FPU is set to the wrong precision. The FBX SDK requires double precision to function properly.
4) Uninstall VA and repeat #3 - works just fine.
Running on Vista + SP1 RC, vs2k5 SP1 + Vista update
Thanks,
- Kirk |
| 16 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - May 14 2008 : 08:53:24 AM
You can simply install VA 1635 over the top of VA 1638 if you want to go back to this version. However if this is working for you in VA 1638 then there is no need to bother.
It is odd that VA 1635 did not seem to fix the problem, it fixed the problem for me when I tested it. However the key thing is that the problem has been fixed. |
| hotzenplotz |
Posted - May 14 2008 : 07:29:46 AM
What I did was basically the same as kklobe, installed XNA 2.0, created the project from the template, tried to compile.
And I'm 99% positive it was 1635.
I switched from 1626 to 1635 weeks ago, and VAX' own version info showed 1635. However I can try to install 1635 again, see if I can reproduce it.
Should I uninstall VAX before "downdating"? (And should I uninstall before updating VAX - at least that's one thing I never do)
|
| sean |
Posted - May 13 2008 : 9:56:19 PM
Are you sure you had 1635 installed? The problem was addressed in 1632. There were no changes between 1635 and 1638 that would have any bearing on the known conflict that existed.
This seems to have been skipped:
case=10703 fixed in build 1632
|
| hotzenplotz |
Posted - May 13 2008 : 9:47:26 PM
I just saw the same thing happening with 1635. Installed 1638 -> problem solved. :)
|
| feline |
Posted - Apr 07 2008 : 08:35:50 AM
There is a work around in the next beta build, which should be posted in the next couple of days. |
| Kasu |
Posted - Apr 05 2008 : 1:44:41 PM
Has this problem been resolved yet? If so, when can we expect the update to be released? |
| sean |
Posted - Mar 31 2008 : 10:28:06 PM
A workaround for this will be in our next beta build. Any day now...
|
| WoodyIS |
Posted - Mar 31 2008 : 4:34:29 PM
Same problem here on WinXP Pro 64bit SP2, DX SDK March 2008, VS 2005 SP1, C#, XNA GS 2.0, VAX 1626. I had to uninstall VAX to repair my content build. |
| feline |
Posted - Mar 03 2008 : 07:54:09 AM
Interesting, someone who does not have VA installed is also seeing the problem:
http://forums.xna.com/38820/ShowThread.aspx
This problem is still in our list of things to look at, but unfortunately I do not have any progress to report. |
| Scythen |
Posted - Feb 29 2008 : 10:56:34 PM
Im also having this problem.
Please fix this. |
| gjoel |
Posted - Feb 02 2008 : 10:35:54 AM
...just to chime in, I'm experiencing this problem too, and had to disable visual assist :(
Help. |
| metzger |
Posted - Jan 31 2008 : 10:37:09 AM
Problem and resolution confirmed.
If I uninstall VX I can compile the content too. seems like it is only the fbx files which causes compilation problems.
I miss my VX. Please make a fix for us. |
| feline |
Posted - Jan 10 2008 : 08:36:36 AM
That is unexpected. I cannot make this fail under winXP.
I have put a note about this on the bug report. Hopefully this will make a bit more sense when the bug is found. |
| testalino |
Posted - Jan 09 2008 : 02:58:16 AM
I'm having the very same problem under Windows XP Prof, so this is not Vista specific.
After uninstalling VA it worked immediately. |
| feline |
Posted - Dec 18 2007 : 2:49:43 PM
It turns out this is an OS specific problem. There is no problem if you do this under winXP, it only fails in Vista:
case=10703
For now you can leave VA installed and just stop if from loading when you are working on XNA. See the registry key here:
http://docs.wholetomato.com?W306 |
| mittens |
Posted - Dec 17 2007 : 10:37:14 AM
Yes, I was having the same problem under VS2005 which was all patched up under Vista. |
