Last edited by SneakyToB; 05-10-2010 at 04:50 PM. Reason: Removing outdated tutorial
Thanks for this i was having some issues using nfringe.
Programming is a way of life.
Interesting, that's pretty much the same as I was writing for an UDN document, except that I got stuck with nFringe at "create project".
Here's last night's version of the document I was working on: http://udn.epicgames.com/Three/Devel...ptProject.html
Cool, that UDN document was exactly the type of information I was looking for a few days ago. I couldn't find very much so I just tried to figure it out using what I could find and lots of trial and error. Please, feel free to add anything I wrote here to that UDN doc to make it more complete.
Also, if visual studio won't create a project make sure the folder you are trying to create the project in does NOT already exist.
Last edited by SneakyToB; 11-11-2009 at 04:33 PM.
The quickest way to get this right is instead of naming your project as SuperFunProject as indicated in step 1, name it SuperFunGame. Otherwise, you have to do these corrections:
Step 3.2: ModEditPackages=SuperFunGame should be ModEditPackages=SuperFunProject
Step 4.2: SuperFunGame.SuperFunGame should be SuperFunProject.SuperFunGame
I hope this helps.
Thank you, Death4Hire. I just edited my post above in step 1 to say create a project named "SuperFunGame" instead of "SuperFunProject".
Can you debug/Step through unrealscript code with nFringe?
I'm using WOTgreal now, it works great but a bit slow when edit large script file, and lack of any debugger integration with UDK.
Well I have VS2008 and nFringe setup and my project is compiling fine, so many thanks for this thread!
My question is... Is there anyway of working on scripts within VS2008 at the same time as working in UDK?
I mean, when I compile the solution within VS2008 I get a build error when the core compiles as the UDK is open. When coding I do tend to build and test constantly which means closing and opening UDK every few minutes.
Maybe I've missed something obvious or am a total noon!
I'm glad this thread was useful for you, fallingbrickwork.
To answer your question it doesn't look like what you are trying to do is possible even if you compile using the UDK make system and bypass Visual Studio. To recompile the scripts it has to overwrite the existing ones (.u files), which it can't do because they are currently in-use and opened by the UDK editor (if you are running it). So, it looks like the only way around this is to close the UDK editor every time you compile the scripts.
Last edited by SneakyToB; 11-13-2009 at 04:15 PM.
So got every thing going with nFring up to the pointto do the build solution.
Im using the new beta2 BTw.
For some reason it is not generating the .u file.
Ive down all the above as the tutorial (following this TUT:
THe build says its successful and displays this:
MyGame -> D:\UDK\UDK-2009-11-2\Development\Src\MyGame\MyGame\Unpublished\Cooked PC\Script\MyGame.u
(Note the double MyGame\Mygame ...strange?)
However the MyGame.u never gets made or copied to the UTgame\scripts folder I had specified:
Any ideas? Any one tried with beta2?
Its not because IM using a "non-commercial" version of nFringe is it? I'd imagine most people use that?
Anybody knows how to step in into unrealscript and debug with VS ? I know it was advertised somewhere for UDK.
The build output anounce that :
I specified that in the build setup :SuperFunProject -> L:\UDK\Development\Src\SuperFunProject\Unpublished \CookedPC\Script\SuperFunProject.u
(note : I installed udk without the "\udk-2009-11-2\")L:\UDK\UTGame\Script
Last edited by hide; 11-17-2009 at 01:05 PM.
shame, considering UDK advertised debugging as stock in the engine...
It should be possible to get WoTgreal to work with UDK as UDK is intended to work the same way as the older UT games and not use the odd UT3 mod structure.
It compiles fine but I cannot find my *.u file in the script-folder. I cannot find it anywhere. What's wrong? And on starting it claims, that my scripts where outdated and asks me to rebuild...
Edit: Okay I fixed it. You have to create your solution to the development/src folder.
Last edited by youkai; 11-17-2009 at 04:18 PM.
schizo: actually WOT works fine, but it doesn't understand the INI or log files. I haven't heard from Harmon in at least a year and a half now, since the last development update, so I don't think he has any interest in going there. Maybe he hasn't heard about UDK, though.
It compiles fine but I cannot find my *.u file in the script-folder!!!
I am having the same issue as many of the other people here. It claims to create the file at ..\Development\Src\SuperFunProject\Unpublished \CookedPC\Script\SuperFunProject.u
However, SuperFunProject.u file is MIA - not to be found in the above location or the UTGame/Script folder I specified.
Running Windows 7 Pro - 64bit with UAC Disabled (Read this somewhere saying it may help but no go)
Any thoughts?? =(
When i'm in the properties of visual studio i don't have the build tab, it gives me weird error, anyone know how i can manually change the build path
Fixed my issue. Turns out I was just being stupid. My UTEngine.ini file had "Packages=MyMod" instead of "ModEditPackages=MyMod"
Changed it and problem solved.
Hey for me it says 'Warning - paths may not be valid' in the log. I've triple checked everything, tried with UDK, the second version of it, reinstalled each about 3 times, but it still says that. Anyway I can fix this??
Just in case it helps anyone, at one point I had added the file extention ".uc" to VS2008 to get C++ color coding when viewing scripts. This was then interfering with trying to get things working with nFringe, so if you have problems check for that...
I have solved the not generating the .u file in the UTGame\Script folder issue. To fix this issue I took the following steps:
Make sure the path it is saving looks like that, chances are it probably doesn't. More than likely it looks like this:
You need to remove that duplicate path. Just move all the files so there is only one instance of the \SuperFunProject path. After you've done this, head back into UDK and it should tell you your scripts are not up to date. Let them rebuild, and in should generate your SuperFunProject.u file. Now technically, you can go back to Visual Studio and begin editing, but you may have a dead link to your UTEngine.ini file in your project. Just remove and readd the Existing Item link to the UTEngine.ini file, just like you did it in OPs tutorial.
I know thats not very thorough, go ahead and ask if you are having any problems with this solution.
Last edited by SpoinkX12; 12-21-2009 at 04:55 PM.
^^ that wasn't my problem I checked the paths and they were set correctly. Still cannot see the .u file after building (even though it says the build succeeded). After I put your .uc file in my classes directory and add it to my project should I see anything change on my solution explorer?? That was one thing I thought was odd was that I didn't see the .uc file after I added it.
I've tried to search through the UDK folder and I don't see SuperFunGame.u anywhere. I ran the unreal frontend make-->full recomplie and that made the .u file correctly.... but I don't get why it wouldn't make it in VS.
SuperFunGame's root folder is in the dev/src folder like you asked it to be, I edited the .ini file to 'ModEditPackages=SuperFunGame' also. I read though other people's problems not generating the .u but they dont seem to apply to me... suggestions?
So I was really wondering why my classes folder wasn't showing anything... I tried to add a new class (called SuperFunGame and copy/paste your code into it... which made it appear under classes... however now when I build it'll say the "Ucc" task failed unexpectedly).
Also I noticed even when there were no classes it tried to make a .u file (which is prolly why I never saw the .u file). But I dont get what I did wrong now =/
Last edited by BZB; 01-13-2010 at 01:35 AM. Reason: update
As should be clear by this point in the thread, I haven't had the chance yet to experiment with UDK and thus clean up the cooperation between it and nFringe. The code editing features should work with it currently, but building and debugging scripts won't.
nFringe, like UnrealEngine itself, is free for non-commercial use and paid ("expensive" to some) for commercial use. However, we were careful to keep the cost completely practical for commercial development teams and as low as possible yet still have a reasonable expectation of covering the costs of our 2-year development effort in a niche market.
Before UDK came around, it was easy to rely on Epic's strict mod licensing policy to separate non-commercial use (UT3 mods) from commercial use (anything else). The new policies (pricing and licensing) makes it harder to distinguish between uses with UDK, so before we can offer debugging support under UDK we'll have to resolve the new licensing concerns it brings. While I'd like to say this will be solved by the end of the coming Summer, I think we'll have to just see how it goes.
If the lack of script debugging under UDK is hindering your development efforts, it can't hurt to let Epic know.
Last edited by 280Z28; 01-13-2010 at 11:01 AM.
ne1 have any ideas why I get that UCC error?
Sigh** I figured it out, I set my UCC path to the UDK.exe.config instead of just UDK.exe ... didn't notice
I mean when I set the path I clicked on the UDK.exe (which is really the .exe.config).
Also if you just see that it made the .u file but not giving you an error... make sure you actually have some code in there it can look at... because it'll say that it made a .u file even if there is no code (and thus no .u file will be made).
Last edited by BZB; 01-13-2010 at 07:01 PM.
Any contact information for contacting Epic ? Nice job for nFringe, and nice to know Epic and you are trying to get the debugger available, I must say that the ability to debug is one of the thing I hate about Unity3d. Torque3d is complicated for a C++ engine, compared to Ogre3d and that leaves you to make a difference, the only thing that is still a turn off for UDK is the browser gaming being non available.
Man, I can't even get my files to add to my solution if I use add existing item, it just doesnt appear at all. This is really frustating
I installed nfringe and I can create unreal script projects, but I dont see an option for debugging unreal script. I saw it at my university under debug menu, but i dont know how to configure my installation of VS 2008 to have the same functionality. Can someone give me a hint how to enable different debugging modes in VS? Thanks in advance
i can't Debug it cause my debug choices are greyed out ^^
what should i do ?
Maybe I am being stupid or blind, but there is no UTGame folder in my UDK directory!
I am using the 04.2010 version. I would be very grateful if anyone of you guys helped me to solve this problem.
UPD: Haha, problem solved. It turned out that Epic renamed "UTGame" into "UDKGame"!
The tutorial must be updated soon, so no one else is confused. =)# Renamed to UDKGame
* All the tools now refer to this game as 'UDKGame'
* UDK content directory is now named UDKGame, not UTGame.
Last edited by Mr.CG; 04-25-2010 at 02:36 PM. Reason: Problem solved.
Ok, so everything builds fine, however I'm not getting my .u file anywhere. This is the error message that I get in the output window.
------ Build started: Project: MageWarTD, Configuration: Debug Win32 ------
Could not locate the .NET Framework SDK. The task is looking for the path to the .NET Framework SDK at the location specified in the SDKInstallRootv2.0 value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramewor k. You may be able to solve the problem by doing one of the following: 1.) Install the .NET Framework SDK. 2.) Manually set the above registry key to the correct location.
MageWarTD -> C:\UDK\UDK-2010-04\Development\Src\MageWarTD\Unpublished\CookedPC\ Script\MageWarTD.u
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
EDIT: On a side note I do have .NET Framework 4.0 installed.
Follow the steps under Building Scripts here:
Last edited by 280Z28; 05-08-2010 at 05:35 PM.
I can't change the folder for my solution, I changed all the configurations but the solution is still being build on the march build, instead of april.
Edit: Actually, it's not being build anywhere!
Does it need to be at the development/src folder?
Ok, bunch of errors:
I installed a new fresh UDK, the april build.
I did a new solution at development/src named UdkProject
The Classes folder was being created at development/src instead of development/src/UdkProject
Every time I tried testing, it game me the warning "there is no *.u files at development/src/UdkProject/Classes" but the folder is not even there
Now I removed the line #+EditPackages=UdkProject from DefaultEngine.ini, but when I try to debug I get the hovering game controller, instead of the default UI and player.
Edit3: Forget that, moved the visual studio files to inside UdkProject folder, changed to unreal 3 mod and defined Reference Source and everything is working now
Last edited by Saishy; 05-08-2010 at 11:52 PM.
It's the Only NEET Thing to Do
Programming for non-fiction.
I'm the function of my code. Conditions are my body and calls are my blood. I have input over a thousand lines. Unknown of bugs, nor known to work. Have withstand coffee to create many programs. Yet, those hands will never code anything again. So, as I pray, Unlimited Code Works.