Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: phreak on January 30, 2007, 01:17:09 pm
-
The MSVC 2005 projects are extremely out of date, a bunch of files and libraries aren't included. However, I'm working on them since I got MSVC 2005 for free through school. I've rebuilt the project file by hand for Freespace2 debug, code debug, liblua debug, libjpeg debug (and it runs!). Still need to work on the release versions of the previous projects as well as both versions for fred2.
-
I just imported the 2003 ones
-
hehe. I should have done that, but I think i cleaned out all of the old stuff by building it by hand.
also, is it safe to build FSO using /fp:fast as opposed to /fp:precise (default): http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/floapoint.asp
-
It would be fine as far as I know, assuming that it works fine for you. Most of the :v: code is tailored more for speed over accuracy anway so I don't see it being that big of a deal. I think that there are a few places where accuracy is a little more important, but I don't think that the optimization will actually affect those places that much.
-
If you don't mind, update or delete the MSVC2005 files in CVS...there's not much point to having them in CVS if they don't compile at all.
I don't have 2005 installed.
-
yea i will update the project files once i add the fred2 project and get it to run.
-
i've just committed what i had and i'll do fred2 when i get around to it. Didn't want the old project files accidentally overwriting the new ones
-
Excellent!
Let me know if you get speech or voice recognition working. I had it working with 2003, but 2005 doesn't like the SDK or something.
-
I'm going to bump this into the main SCP forum because a couple of people have been asking
-
yeah, like me :D
-
Any news on this?
-
well when i posted my message, the build was working, but goober's added some additional files since then so i'll need to update the project files. i also think fred is working as well.
-
updated project files
+1
-
On which branch? I keep downloading 3.6.9 and always getting the same old not working project file.
Is it on the HEAD branch? Or what do I need?
-
yes its on the head branch. i may want to fix the project files for 3.6.9, but i rarely work on that branch.
-
I resurect this thread...
Any work on getting the Voice SDK to work? I discovered that problem a long time ago when I got the professional version.
-
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=147257&SiteID=1
-
on the topic of code, how do you code in a SEXP?
-
http://www.volitionwatch.com/articles/ArticleDisp.php?ID=53
-
that guide is sort of old since a few changes to the sexp files have been made, but overall its similar.
redmenace: I have the voice sdk installed, but i never enable the compiler flag to turn it on.
-
oh sorry. When if ever you try and use speech sdk, changes to the actual code must be made to make it work.
-
what kind of changes?
-
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=147257&SiteID=1
It affects VS2005 only.
-
Hey, I am working with a pull from November 2006. I fixed most of the issues with the speech sdk. But the speech.cpp is choking on this line:
return SUCCEEDED(Voice_device->Speak(Conversion_buffer, SPF_ASYNC, NULL));
I got the error below:
1>..\..\code\sound\speech.cpp(160) : error C2664: 'ISpVoice::Speak' : cannot convert parameter 1 from 'unsigned short [10000]' to 'const WCHAR *'
Some help would be appreciated.
-
You should just be able to change Conversion_buffer[] from "unsigned short" to "WCHAR" and that's it. The types are the same as far as I know, but MS may have changed it a little, or they are just dealing with type-specific error conditions properly now (which is pretty much required for 64-bit platform support).
-
what kind of changes?
- You can also choose from a variety of SEXP subcategories to show your SEXP in.
- Sexp_help[] has been moved to code/parse/sexp.cpp (So you only have to change code/parse/sexp.cpp and code/parse/sexp.h to add a new SEXP)
-
I am not sure how we want to handle the custom header file from the sdk. Any thoughts?