Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Axem on February 07, 2009, 12:44:21 pm
-
I've noticed new icons for the main FreeSpace exe in newer builds, but alas no FRED ones. I took it upon myself to make some, but if someone else has made some but just aren't in the exe yet, well shoot then.
Anyway I made 3 variants. FRED2, FRED Open and FRED 2 Open. (What is FRED's official name anyway?)
(http://img.photobucket.com/albums/v109/NarfPics/fredicons.png)(http://img.photobucket.com/albums/v109/NarfPics/fredopenicons.png)(http://img.photobucket.com/albums/v109/NarfPics/fred2openicons.png)
(The 48x48 FRED2 one I need to tweak a bit so its like the others.)
They also have a white glow under the FS Emblem so you can see it easily on darker backgrounds (my one complaint about the new FS icons).
EDIT: Link for anyone who wants to try them out (http://www.axemspace.com/files/misc/fredopenicons.rar)
-
Ooh, awesome. :)
-
Good man! It was time :)
Just one thing...Vista/Windows 7 have icon support to....256 I think it was. Might want to look to the future.
-
If anyone knows where the source for the icons came from, I could add in a 256 version for both sets.
-
I like the
FRED
2
Open
design out of the group.
-
Superb!
-
Awesome. I'll have to say that the FRED - 2 - Open design is the best of the group.
-
Looks sharp, but they seem a little rough on the edges. They're far better than what's there for FRED now, but I think the new FS exe ones are a bit nicer looking. Are they 32bit color?
-
Yeah, they're all True Color + Alpha. I extracted the new FS exe icons and put the words over in Photoshop, then resaved them. If you've got any suggestions on how to improve, that'd be awesome.
-
Reminds me of Lolcats. "I can has icon?"
-
I think it was just the words I thought were a little rough, maybe you can anti-alias them with the background?
-
Nth-ing the fred2open design.
As a person who cannot work without the "detail" view in windows, I especially like the increased distinction between the 16x16 FS2O icon.
-
Well the text is anti-aliased. I tried to make it as readable as possible, but cramming 9 characters in a small space while trying to make sure its readable over any background is tricky. Plus Photoshop's AA options all suck for sizes that small. I had to take the one that looked the least worse. I can upload the PSDs I saved if anyone else wants to tweak them a bit.
-
Ok I'll stop being picky then. I still want to see 128/256 versions though :)
-
BUMP!
Icons up to 256 x 256. I also did glow versions of the FS2 icons too. I realize Foxer already made those, but he didn't make up to 256 and I couldn't emulate his glow style perfectly, so I tried the best I could across all of them so they would look consistent.
http://axemspace.com/files/fs2o-256.ico
http://axemspace.com/files/fred2o-256.ico
-
These are committed to trunk, and will probably be the icons for the official 3.6.10 and any RCs before then.
-
:bump:
Lately I've been getting these errors trying to compile any new builds... any solution for this n00b?
--------------------Configuration: Freespace2 - Win32 Release Inferno--------------------
Compiling resources...
F:\FS_Open\FSOcode\code\FREESPACE2\FreeSpace.rc (392): error RC2176 : old DIB in app_icon.ico; pass it through SDKPAINT
Error executing rc.exe.
fs2_open_trunk_r_INF.exe - 1 error(s), 25 warning(s)
--------------------Configuration: Fred2 - Win32 Release--------------------
Compiling resources...
F:\FS_Open\FSOcode\code\fred2\FRED.rc (74): error RC2176 : old DIB in res\FRED.ico; pass it through SDKPAINT
Error executing rc.exe.
fred2_open_trunk_r.exe - 1 error(s), 0 warning(s)
--------------------Configuration: Fred2 - Win32 Debug--------------------
Compiling resources...
F:\FS_Open\FSOcode\code\fred2\FRED.rc (74): error RC2176 : old DIB in res\FRED.ico; pass it through SDKPAINT
Error executing rc.exe.
fred2_open_trunk_d.exe - 1 error(s), 0 warning(s)
--------------------Configuration: Fred2 - Win32 Debug Inferno--------------------
Compiling resources...
F:\FS_Open\FSOcode\code\fred2\FRED.rc (74): error RC2176 : old DIB in res\FRED.ico; pass it through SDKPAINT
Error executing rc.exe.
fred2_open_trunk_d_INF.exe - 1 error(s), 0 warning(s)
--------------------Configuration: Fred2 - Win32 Release Inferno--------------------
Compiling resources...
F:\FS_Open\FSOcode\code\fred2\FRED.rc (74): error RC2176 : old DIB in res\FRED.ico; pass it through SDKPAINT
Error executing rc.exe.
fred2_open_trunk_r_INF.exe - 1 error(s), 0 warning(s)
:nervous:
-
Darn. Reverted until I make sure we can compile with Axem's icons this time. Should compile OK now.
-
Trying it now, brb...
EDIT: well now FS2 and FRED2 compiles fine (yay), but compiling FRED2 debug throws up some random error
Linking...
LINK : error : Internal error during FinalPhase
ExceptionCode = C0000005
ExceptionFlags = 00000000
ExceptionAddress = 00439535
NumberParameters = 00000002
ExceptionInformation[ 0] = 00000000
ExceptionInformation[ 1] = 3FFF029C
CONTEXT:
Eax = 3FFF0000 Esp = 0012F6A8
Ebx = 36B7B000 Ebp = 004964B0
Ecx = 00000A28 Esi = 007ED3AC
Edx = 00A50003 Edi = 01000000
Eip = 00439535 EFlags = 00010212
SegCs = 0000001B SegDs = 00000023
SegSs = 00000023 SegEs = 00000023
SegFs = 0000003B SegGs = 00000000
Dr0 = 0012F6A8 Dr3 = 36B7B000
Dr1 = 004964B0 Dr6 = 00000A28
Dr2 = 00000000 Dr7 = 00000000
Error executing link.exe.
Tool execution canceled by user.
but the way the error looks like, I don't think it's related to the icons and I have to rush off elsewhere, so... be back later :shaking:
-
That looks like a hardware error to me. I compiled a merge of FRED2 trunk today into Wanderer's branch just fine, so any code in trunk should compile FRED2 debug unless he somehow has a fix (unlikely since Wanderer doesn't mess with FRED).
-
Trying it now, brb...
EDIT: well now FS2 and FRED2 compiles fine (yay), but compiling FRED2 debug throws up some random error
Run the compile again. I get that one all the time for some strange reason but running it a second time works just fine.
Yeah, I've got no explanation for that either. :D
-
LOL, coincidences... I did it just before you posted; force-rebooted the comp after some windows update got stuck halfway.
Opened it "the long way" (instead of "Recent Files"), manually compiled the FRED2 debug build by itself (no batch building)... compile...
1 file(s) copied.
0 errors, xx warnings
*blah blah blah could not find FS2PATH*
Earlier when I got the error it was actually my 2nd or 3rd compile.. and it just kept coming up. Don't know how it solved itself. also this isn't chief's new project - rather my own with the SAPI files put in place... somewhere... :nervous:
Definitely strange... :nervous: :lol: XD
-
The FS2Path error is easily solved (and should be solved if you have FS2 anywhere other than C:\Games\Freespace2).
System control panel->Advanced->Environmental Variables->New User Variable->
Call the variable FS2Path and the value is the path to where ever you have FS2.
Now when you compile the FSO exes will be copied to your FS2 folder. :)
-
Cool, I didn't know that. Then all I have to do is rename the old exe's if I needa keep them for anything.
Thanks. :D