Aces High Bulletin Board
General Forums => Custom Skins => Topic started by: Skuzzy on December 09, 2016, 04:26:46 PM
-
The updated skin submission system is ready to test. It is located at the same URL (http://bbs.hitechcreations.com/skinadmin) as before.
Keep in mind this is for testing purposes. Everything you do might be completely undone Monday. Just use it like you normally would. Both the update and submit should work. If things get wonky, do not worry about it. It is a test.
This is not the final version and still needs some tweaking. Right now, you have to submit ALL the files (you'll see what I mean), which may not have been dumped with the default skin.
For example, if the skin has no power (_P)map, then copy the specular (_S) map to the power map. To create the environment (_E) map, simply take 0.8 of the power map and create it.
-
There is a spelling error in the URL, this is the correct one:
http://bbs.hitechcreations.com/skinadmin
-
What is the purpose of keeping the (_A) maps active?
-
What is the purpose of keeping the (_A) maps active?
Beat me to it.
-
Thanks, Skuzzy.
-
WTG, Skuzzy.
-
There are some vehicles and, at least, one plane which needs the _A (alpha) texture.
One of the things I need to do is to not allow both _P and _A files to be submitted for any given skin. You can have power or alpha, but not both.
Thank you Greebo, for pointing out the typo.
-
I've done some testing on the new submissions page.
First I attempted to update an existing Brewster skin. This gave me the error message: "You must not include "by Greebo" in the BW-393 1/LeLv 24 by Greebo" description. The problem is that there is no way I can edit this description and I believe its not possible to do so anyway short of deleting the skin and resubmitting it. So I'd say this is a bug that will affect any skin originally submitted prior to the old submission page going live.
I'd also like a way of editing the history description file that was originally submitted with the skin. When I wrote these old descriptions I wasn't expecting the text to be shown on a skins web page and wrote it more as a history with a list of sources including web links (probably out of date now) and book references.
When you hit the return to submission button it takes you to the new skins submission page, not the updated skins submission page and there is no link to take you to the updated skins page. Also it would be nice for new or updated skins if hitting this button took you back to the page with your previously submitted data already there. This way I could edit whatever the error was without having to fill out the whole page again.
Next I tried a new TBM-3 skin. This gave me an error message complaining about the lack of the "tbm3_a.bmp" file which I don't have but is listed as required. I was expecting this but thought I'd test it anyway. The error message is a little confusing, it goes:-
Skin Files Verification
TBM3.bmp: TBM3_E.bmp: TBM3_N.bmp: TBM3_P.bmp: TBM3_S.bmp: TBM3_A.bmp: Missing files(s) required from the skin submission
It would be clearer like this:
Skin Files Verification
TBM3.bmp: TBM3_E.bmp: TBM3_N.bmp: TBM3_P.bmp: TBM3_S.bmp: Verified
TBM3_A.bmp: Missing file(s) required for the skin submission
I had a look at the Panzer IV page and spotted an issue. The page lists pz4tred_e.bmp and pz4tred_p.bmp as required files which I don't think they should be. This seems to affect all the other GVs as well.
I then took a look at an AH1-era skin, the Ju-88A-4. This lists the diffuse, _E, _P and _S files as required. My understanding was that only the diffuse and specular files were used on AH1-era skins. So either this is a bug that will likely affect all AH1 skins or I need to add the other files to my skins before I can submit them.
Uploading up to five 2048 bmps can take a while so it would be nice if there was a progress bar to let the skinner know roughly what was going on after hitting "submit".
The page logging you out when the hour changes is kind of annoying.
-
Thank you Greebo. I know where the error with the update is and the return links. Aggressive consolidation.
I'll work on adding history editing.
All skins get the AH3 treatment, even the AH1 skins. HiTech wrote a conversion to convert those. They may only use a generic bitmap, but they are all (_A,_P,_N,_E,_S) being applied where applicable. I say that as most skins do not need an _A file which is something I will address as we go forward with the submission process.
-
In that case the Ju-88 is missing the normal maps from its file listing. I checked a few other AH1-era planes and they all seem to be missing normal maps.
-
Missing from the listing in the submission utility, or missing from the Aces High III saved default?
-
The normal files are missing from AH1 rides on the submissions page, I haven't checked the game or viewer default files.
-
New version installed.
1) Wiped any submissions/updates from the queue.
2) Corrected the erroneous request for the name of the skin during updates.
3) Error message output revised.
4) Miscellaneous missing files added to the definition list.
I will look into adding a history edit box once we get this stable. it is easier to add to stable code than introduce new code while trying to get things stable.
All the file requirements are for every model, across the board, regardless of the age of the model. There will be some adjustments made for the requirement textures. Right now it requires both _A and _P, which are mutually exclusive, for example.
I would like to make sure the mechanics of submitting everything is working before going into "feature" mode. Once you see the "Beta" tage removed from the login page, then we are in official submission mode.
-
There aren't any of my skins listed if I select "Update a skin". I get an empty list.
The back browser button doesn't take me back to the previous screen - I get a "Confirm Form Resubmission" page (using Opera) and if I back out of that, it takes me back to the Login screen.
The Login screen keeps populating the Login ID input box with my BB ID, which is different from my game Login ID. Even after I login successfully with my game ID, if hit the back button I wind up back at the login screen and the input box has my BB ID in it again.
I'm still confused about the requirement of both an _A and a _P file. The P-38J has only the diffuse map (P38J1.bmp) and the Normal and Specular maps. I can create my own Power and Environment maps, but I don't know how to create an _A map.
I tried a New submit using the default P-38L files (plus creating the required _P and _E by copying/renaming the _S map file) and after I hit "Submit", I get this error after a few seconds:
Access denied
Invalid access to this page. Missing information.
It also took me back to the Login screen, populated again with my BB ID, not my Game ID.
-
There aren't any of my skins listed if I select "Update a skin". I get an empty list.
That is due to your game account not being associated with the skinner account. It looks like you deleted the game account associated with the skinner account, so the system cannot recognize you.
When/If you delete your game account, the skinner account is no longer accessible. To get them back you have to contact us with the new login ID for the active account.
Be aware, after six months, or so, of no game account at all, the skins will migrate to "Orphan" status and will be available to be adopted by another skinner. We have not implemented that formally, but it is coming.
In the meantime, I have reattached the skinner account to your current game account.
The back browser button doesn't take me back to the previous screen - I get a "Confirm Form Resubmission" page (using Opera) and if I back out of that, it takes me back to the Login screen.
The Login screen keeps populating the Login ID input box with my BB ID, which is different from my game Login ID. Even after I login successfully with my game ID, if hit the back button I wind up back at the login screen and the input box has my BB ID in it again.
This is your browser doing that. We cannot do anything about that. You have your browser configured to auto-login and it is using the data it is keeping. As to why you cannot reset that data, you would have to check with whoever made the browser.
I'm still confused about the requirement of both an _A and a _P file. The P-38J has only the diffuse map (P38J1.bmp) and the Normal and Specular maps. I can create my own Power and Environment maps, but I don't know how to create an _A map.
The _A and _P maps are mutually exclusive. If you submit a _P map, the _A map will be ignored. Right now, I am asking for all the maps to be submitted so I can make sure that all get downloaded. In reality, you will only be able to submit either the _P or the _A. When we go live the submission screen will reflect that.
I tried a New submit using the default P-38L files (plus creating the required _P and _E by copying/renaming the _S map file) and after I hit "Submit", I get this error after a few seconds:
Access denied
Invalid access to this page. Missing information.
It also took me back to the Login screen, populated again with my BB ID, not my Game ID.
That is also a browser error. It sounds like the browser is tossing out the information. What browser are you using?
-
I successfully uploaded a couple of skins with a blank white alpha file added, bar the reference image file that I accidentally misnamed. It took about 2-3 minutes for the 1024 res skin and 7-8 for the 2048 res one.
Many of the GVs still have some track files incorrectly listed as required, these are the files:
Firefly: a, e, p
Hetzer: e, p
M16: e, p
LVTA4: e, p
M18: e, p
M4A3 75: e, p
Panzer IV H: e, p
Panther: p
T34 1943: a, e, p
Tiger I: e, p
Tiger II: p
-
You did? New skins? Updated? Today? Nothing showed up in submissions for today. I wiped whatever was in there from the weekend.
I knew the vehicles were a bit of a mess. I'll need some help with those, but not right now.
-
OK, I guess the incorrectly named reference images prevented the skins updating. I assumed they had been uploaded because the message said the other files had been verified. I'll try again now I have renamed the reference files.
BTW I have found another issue:
On the A-20G the "marking" files are missing from the page's list. These are patches with alpha maps that display the US markings on only top left and bottom right of the mirrored wings. The FM-2 has a similar arrangement but the "fmstr" files are present on this plane, although the diffuse and specular files are not marked as required.
-
There is multiple levels of verification now.
1) Verify the files actually belong to the submission.
2) Verify the names of the files match the names of the file list.
3) Verify the size (pixels).
4) Verify the bit count and type of file.
If any one of those fail, for any given file, then nothing is uploaded. Although, I was not intending the optional files to be that critical. I'll review that.
I suspect we will find more files missing as we move along. I had to build that entire list by hand.
-
I submitted a new TBM skin and updated an old Brewster skin successfully and they showing as such on the main page. I think the page should reject the submission if the reference file is wrong since there is no way of adding it later, maybe just make the submission failed message a bit clearer.
-
That is due to your game account not being associated with the skinner account. It looks like you deleted the game account associated with the skinner account, so the system cannot recognize you.
When/If you delete your game account, the skinner account is no longer accessible. To get them back you have to contact us with the new login ID for the active account.
Be aware, after six months, or so, of no game account at all, the skins will migrate to "Orphan" status and will be available to be adopted by another skinner. We have not implemented that formally, but it is coming.
In the meantime, I have reattached the skinner account to your current game account.
This is your browser doing that. We cannot do anything about that. You have your browser configured to auto-login and it is using the data it is keeping. As to why you cannot reset that data, you would have to check with whoever made the browser.
The _A and _P maps are mutually exclusive. If you submit a _P map, the _A map will be ignored. Right now, I am asking for all the maps to be submitted so I can make sure that all get downloaded. In reality, you will only be able to submit either the _P or the _A. When we go live the submission screen will reflect that.
That is also a browser error. It sounds like the browser is tossing out the information. What browser are you using?
Thanks for reattaching my skinner account to my current game account. I still see no skins for Oboe though - the page says
oboe's Updated Skins
Total Skins: 0
I was using the Opera web browser - just started recently and it seems fast and I like the design of it, but I'm not tied to it. I found the password management section and it apparently stores one login/password per website, so that's why its always pre-filling my BB ID and password.
I just tried it with Internet Explorer, and when I use the back button from the Skins Update page I get a "Webpage has expired" page. If I refresh this page as it suggests and click the "Retry" button on the message window that pops up, I get taken back to the Skins Admin main page.
EDIT: Just tried the same thing in MS Edge, and when use the Back button from the Updates page, I get this page:
Hmm, we can't reach this page.
Try this
Make sure you’ve got the right web address: http://bbs.hitechcreations.com
Refresh the page
Search for what you want
I refreshed the page and was taken back to the Login page. At this point I have to re-login; the Forward browser arrow is greyed out.
-
I tried again this morning on the outside chance that a database or something needed to be bounced overnight to recognize the changes, but I get the same thing - oboe's skin list is empty.
btw, on the main Skins Administration page, in the Skinner Information page, it is showing
"oboe" as my Game ID. This is my game handle and my BB id, but NOT the "Aces High Game login id" that I must enter in the Skins Admin login, and not the ID I use to login to the game.
EDIT: I was just able to successfully submit the default P-38L skin as a new submit (for testing purposes). I had to create the missing _A, _E, and _P files by copying and renaming the _S file. I understand the _A and _P files are supposed to be mutually exclusive, and if you submit one it will ignore the other, but on my first try I received an error for missing the _A file even though I was submitting a _P file. I had to submit both _A and _P files to get through the verification.
Still no skins listed for oboe on the update page however.
-
The problems started when you signed in before I had a chance to manually link your skins to your new game account. The system simply created a new entry for you as a new skinner. Then I came along and modified your previous account to link to the skins, which meant you had two entries for the same login ID.
This created many issues as I had not prepared the code for this circumstance.
I cleaned it all up now and you should see everything.
Now, as to using the "back" button. The system is deliberately designed to make this difficult, and in some cases, impossible to do. It is a security feature to keep would-be hackers from directly accessing any of the pages in the system.
Properly used, you should never have to use the "back" button of the browser. Now, if there are circumstances I have missed, then I need to know about it, but I am not going to sweat the "back" button not working, when it is not supposed to.
Yes, the system shows your game ID. I am never going to display your login ID, for security reasons.
I see oboe has submitted a skin and Greebo has submitted an update to a skin, in the last 24 hours. Correct?
-
I should have two skins showing, a new TBM and an updated Brewster.
-
I should have two skins showing, a new TBM and an updated Brewster.
Oops, you are correct. I missed it earlier (more coffee needed).
-
The problems started when you signed in before I had a chance to manually link your skins to your new game account. The system simply created a new entry for you as a new skinner. Then I came along and modified your previous account to link to the skins, which meant you had two entries for the same login ID.
This created many issues as I had not prepared the code for this circumstance.
I cleaned it all up now and you should see everything.
Now, as to using the "back" button. The system is deliberately designed to make this difficult, and in some cases, impossible to do. It is a security feature to keep would-be hackers from directly accessing any of the pages in the system.
Properly used, you should never have to use the "back" button of the browser. Now, if there are circumstances I have missed, then I need to know about it, but I am not going to sweat the "back" button not working, when it is not supposed to.
Yes, the system shows your game ID. I am never going to display your login ID, for security reasons.
I see oboe has submitted a skin and Greebo has submitted an update to a skin, in the last 24 hours. Correct?
I see all of Oboe's skins listed now on the Update page.
It's also correct that I have submitted a new P-38L skin this morning (however its a dummy skin for testing only - its just a copy of the default P-38L skin). I note though, that system required both the _A and the _P files to pass the submit verification - my understanding is that they are mutually exclusive and if you submit one, the system will not require the other.
-
Correct, and I am working through that along with some other items Greebo brought up.
-
<snip>I think the page should reject the submission if the reference file is wrong since there is no way of adding it later, maybe just make the submission failed message a bit clearer.
I am a bit confused about this one. Could you clarify?
-
I am a bit confused about this one. Could you clarify?
You said you were reviewing if the optional files needing to be that critical and I was just saying I think the skin should not be passed if the reference files are incorrectly formatted.
All skins get the AH3 treatment, even the AH1 skins. HiTech wrote a conversion to convert those. They may only use a generic bitmap, but they are all (_A,_P,_N,_E,_S) being applied where applicable.
Based on this I have just finished creating all the normal, power and environment files for a Boston skin I have done, but when I went to view them they had no effect, only the diffuse and specular files work. The default files I just downloaded for the Boston only include diffuse and specular files, same with the Ju-88. So either you are wrong about the other files working with AH1 shapes or these effects are not working as they should on AH1 shapes.
-
According to HiTech, the normal maps should work for every skin. Now, has it been tested is the real question. The intent is there, for certain.
Go ahead and submit that Boston skin, and I will get the files to HiTech so he can track down what is going on.
Yes, the optional files are also checked for proper size and type. If I implied they were not, that was my error.
-
Skuzzy,
I will be back at my computer for the next week. I am willing to jump in and help. Any chance of linking back to my original login?
-
I attempted to upload the Boston skin but it didn't work. This is the report I got:-
Welcome to new skins validation page.
Object Name: boston3 Verified
Skin Information: Verified
Skin Name: 88S/RAF by Greebo Verified
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload types and pixel sizes: Verified
thumbnailimg.jpg 128, 128 Verified
fullsizeimg.jpg 1280, 720 Verified
is not the correct file name for the reference1img image. It must be "reference1img.jpg".
The thing is the reference images are named and sized correctly this time, so I am not sure why its complaining about it or why the file is not named at the beginning of the sentence.
I think this error text should say something like: "Your skin could not be uploaded because...." Also "All Required files: Submitted" is misleading, first time I saw this page I assumed the other files had been uploaded.
Looking again at the Boston's submission page file list I can see something wrong. All three normal files for the Boston are listed as "8-bit, unknown" rather than "32-bit, RGB". This seems to be the case for other AH1 skins as well.
Just noticed the reference1img.jpg I submitted has retained an author and tag from the photo I edited to make it, wondering if this could this be the problem.
-
Skuzzy,
I will be back at my computer for the next week. I am willing to jump in and help. Any chance of linking back to my original login?
I cannot find an active game account for you. PM me the login for the account.
I attempted to upload the Boston skin but it didn't work. This is the report I got:-
Welcome to new skins validation page.
Object Name: boston3 Verified
Skin Information: Verified
Skin Name: 88S/RAF by Greebo Verified
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload types and pixel sizes: Verified
thumbnailimg.jpg 128, 128 Verified
fullsizeimg.jpg 1280, 720 Verified
is not the correct file name for the reference1img image. It must be "reference1img.jpg".
The thing is the reference images are named and sized correctly this time, so I am not sure why its complaining about it or why the file is not named at the beginning of the sentence.
I think this error text should say something like: "Your skin could not be uploaded because...." Also "All Required files: Submitted" is misleading, first time I saw this page I assumed the other files had been uploaded.
Looking again at the Boston's submission page file list I can see something wrong. All three normal files for the Boston are listed as "8-bit, unknown" rather than "32-bit, RGB". This seems to be the case for other AH1 skins as well.
Just noticed the reference1img.jpg I submitted has retained an author and tag from the photo I edited to make it, wondering if this could this be the problem.
That may have been due to an error in the database. I missed adding some information when I added in the rest of the normal map requirements.
I am going to spend today re-working the requirements in the database. The current settings do not make sense. That said, I will need some help on some of the vehicles and what should be required.
I'll let you know when it is safe to post skins.
-
Back online again.
Greebo, not sure what caused that error with the Boston submission. It might have been an error in the database. Go ahead and give it another try. You will note, not all files are required.
Still have some database work to do, but it is getting there.
-
I submitted a 109G-6 for testing. No issues with the submission. :aok
-
I submitted a 109G-6 for testing. No issues with the submission. :aok
Except it should have failed. Your primary bitmap is 8 bit, indexed and it is supposed tobe 32 bit, RGB, like the normal map.
Back to the drawing board for me.
-
Fixed. Submit it again Devil before you change it and make sure it does not get accepted.
Thank you!
-
I submitted the Boston with no problems this time.
I'll go through the list of rides over the next few days and see if I can spot any errors in the file listings.
-
I submitted the Boston with no problems this time.
I'll go through the list of rides over the next few days and see if I can spot any errors in the file listings.
Noticed it and HiTech has it now looking at the issue. Thank you Greebo.
-
I made changes to the "required" files as follows:
If there is an _A file, in the default skin, the _P map is not available at all.
If there is not an _A file in the default skin, then _A is not available for that skin and the _P map becomes an option.
The _E map is only required, if it came with the default skin, otherwise it is optional.
The _N and _S maps are required for all skins.
I think that makes more sense.
-
The error with the normal maps (and others as well) and objects which did not have them has been corrected for the next patch.
In the meantime, I am going to as you skinners not to submit skins with normal maps which were not part of the default skin. We have no way of testing them, until the next patch is out and then you will be able to view them in the skin viewer before submitting them.
-
I cannot find an active game account for you. PM me the login for the account.
A public thank you for fixing this. :salute
-
Except it should have failed. Your primary bitmap is 8 bit, indexed and it is supposed tobe 32 bit, RGB, like the normal map.
Back to the drawing board for me.
I'm confused, are we not using 8 bit bitmaps anymore?
-
I'm confused, are we not using 8 bit bitmaps anymore?
Check the file descriptions when you go to submit, next to the "Browse" button. Each line listing shows the number of bits and type. I really need you to resubmit what you had so I can make sure it does fail.
-
Ok Skuzzy, I attempted a submission with same files - no errors this time either
-
I'm confused, are we not using 8 bit bitmaps anymore?
Devil are you using the Bright plugin for photoshop? Bright exports an 8-bit bmp (I don't know if it changes it to Indexed color from RGB - not sure how to find that out). Anyway my primary bmp from Bright looks fine in AH3, but it sounds like we won't be able to use this anymore.
-
I just used the indexed mode right in Gimp. I could never get Bright to work for me. From what Skuzzy is saying, it looks like we're going to a 32 bit bitmap, which at least for me is no problem to make since Gimp gives you the options when saving to a bitmap.
-
I just used the indexed mode right in Gimp. I could never get Bright to work for me. From what Skuzzy is saying, it looks like we're going to a 32 bit bitmap, which at least for me is no problem to make since Gimp gives you the options when saving to a bitmap.
So basically we don't need to convert downward to 8-bit?
:aok :aok :aok
-
No, you do not need to convert the skin down to 8-bit so Bright is superfluous now. The basic skin and normal map are in 32-bit colour while the specular, power and environmental maps are 8-bit greyscale.
There are also no text files needed apart from the naming one used to describe the skin in the offline game's hangar list.
-
Version 3.0C is now online.
1) Fixed the session manager so the skin information is restored when you have to go back to try and submit again.
2) Increased the login timer to 24 hours.
3) Fixed several error messages to make them more clear.
4) Corrected file validation.
5) Added a link back to the main page if the submission fails, along with the submit link.
All submissions have been cleared.
I have one big feature I would like to add, and if nothing else comes up, the final version will be done soon. So bang on it folks. And thank everyone for the help. It is appreciated.
By the way Greebo, normal maps should now (game Patch 14) be working for the skins which never had one.
-
Ok, uploader is kicking out the skins correctly now - won't accept the 8 bit bitmap.
-
I also noticed you have a 24 bit normal map, which should be 32 bit. Technically, 24 bit would work, but we would like to standardize on 32 bit.
-
Yeah, I'm still trying to figure out the normal map bits. PSP did not like the 32 bit bump maps that I was trying to import to convert to normal maps, but would open the same image if it was saved as 24 bit. I'm going to try installing the normal map plugin to Adobe photoshop.
-
Thanks Skuzzy, the lighting effects on the Boston skin now appear to be working correctly.
I have gone through the file listings on the new submission page and found what seem to me to be some bugs. As much of this was checked prior to the latest revision you may have already corrected some of these.
A-20G: Add marking.bmp, plus the e,s,p and n versions of it.
A6M2: Add a6m2a.bmp
A6M5: Add a6m5ba.bmp
B5N2: Add b5n2_1_(e,n and p).bmp
C-47A: Add c47a.bmp
Camel: Add camel_1_(e and p).bmp, camel_2_(e and p).bmp
Remove camel(e and p).bmp
Change camel_(1 and 2)_s.bmp from 32-bits RGB to 8 bits grayscale.
Dr 1: Add dr1_1_(e and p).bmp, dr1_2_(e and p).bmp, dr1_1d_(e and a).bmp and dr1_2d_(e and a).bmp
Remove dr1(e and p).bmp
Change all (a, e, p and s) files from 32-bits RGB to 8 bits grayscale.
F4U-1A: Add f4u1a.bmp
FM-2: Change fmstr.bmp and fmstr_s.bmp from optional to required.
Hetzer: Change hetztrd_a.bmp from required to optional.
Jeep: Change jeep.bmp from optional to required.
Jagdpanther: Change pnthrtrd_a.bmp from required to optional.
Jagdpanzer IV: Change pz4trd_a.bmp from required to optional.
LVTA2: Change lvtrak_a.bmp from required to optional.
LVTA4: Change lvtrak_a.bmp from required to optional.
M16: Change m3a1trd_a.bmp from required to optional.
M18: Change m18trd_a.bmp from required to optional.
M3: Add m3a1in_(e and p).bmp
Change m3a1trd_a.bmp from required to optional.
M4A3/75: Change m4a3trx_a.bmp from required to optional.
M4A3/76: Change m4a3trx_a.bmp from required to optional.
Me163: Change me163sd.bmp and me163sd_s.bmp from optional to required.
Change me163wg.bmp and me163wg_s.bmp from optional to required.
Me262: Add me262a.bmp
Ostwind: Add pzrtrd_(e and s).bmp
Change pzrtrd_a.bmp from required to optional.
Panther: Change pnthrtrd_a.bmp from required to optional.
Panzer IV F: Change pz4tred_a.bmp from required to optional.
Panzer IV H: Change pz4tred_a.bmp from required to optional.
Sd Kfz 251: Change sdktrd_a.bmp from required to optional.
Spitfire Mk I: Add spit1a.bmp
T34-85: Add 34trax_(e and p).bmp (The T-34s' tracks don't seem to use alpha maps)
Tempest: Change tmpside.bmp, tmpstab.bmp and tmpstab_s.bmp from optional to required.
Tiger I: Add tiger1a.bmp
Change pz6tred_a.bmp from required to optional.
Tiger II: Change tig2trd_a.bmp from required to optional.
Wirblewind: Change pzrtrd_a.bmp from required to optional.
-
according to my photoshop it is 2048 x 2048 but below is what is returned.
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
KI61.bmp does not appear to be the correct size (2048.0002441406).
KI61_E.bmp does not appear to be the correct size (2048.0009765625).
KI61_N.bmp does not appear to be the correct size (2048.0002441406).
KI61_P.bmp does not appear to be the correct size (2048.0009765625).
KI61_S.bmp does not appear to be the correct size (2048.0009765625).
-
Well, I am a bit surprised those values are being extended to double floats. I'll look at what I can do to avoid that. Thank you FTJR.
-
No, you do not need to convert the skin down to 8-bit so Bright is superfluous now. The basic skin and normal map are in 32-bit colour while the specular, power and environmental maps are 8-bit greyscale.
There are also no text files needed apart from the naming one used to describe the skin in the offline game's hangar list.
I'm getting some very weird results trying to use 32 bit bitmaps. On the main skin, the colors are shifted about 1/3 on the color wheel (yellow becomes red, etc)
32bit
(http://i241.photobucket.com/albums/ff252/DropkickYankees/Aces%20High/32bit%20BS_zpsvvorvvbj.png~original) (http://s241.photobucket.com/user/DropkickYankees/media/Aces%20High/32bit%20BS_zpsvvorvvbj.png.html)
24bit - How it should look.
(http://i241.photobucket.com/albums/ff252/DropkickYankees/Aces%20High/24bit%20BS_zps3jfwf5kk.png~original) (http://s241.photobucket.com/user/DropkickYankees/media/Aces%20High/24bit%20BS_zps3jfwf5kk.png.html)
Skins are not indexed. 32bit file is 4.00MB and the 24bit is 3.00MB
-
I'm in the same boat as you Devil as I am using PSP which while will only save alpha channels in its native format and until your post I was happily saving diffuse and normal maps as 24-bit bmps. Luckily I have a copy of Photoshop Elements and this has an option to save the bmps in 32-bit, so I'll just do this once per skin prior to submission.
Regarding your colour shift problem. Initially I could not reproduce it, the 32-bit skin and normal maps looked identical to the 24-bit ones in both the viewer and the game. However after playing with Photoshop's advanced settings button on the bmp save menu I managed to get the same colour shift. The default advanced settings used by Photoshop are 16-bit A1 R5 G5 B5 and with that it looked fine. To get the colour shift I had to manually change it to 32 bit X8 R8 G8 B8. So just leave it on standard settings and it should work OK.
-
Got the same issue as FTJR with a 1024 res skin:
File upload bit count, type, or pixel size: Failed Verification
B239.bmp does not appear to be the correct size (1024.0004882812).
B239_N.bmp does not appear to be the correct size (1024.0004882812).
-
Got the same issue as FTJR with a 1024 res skin:
File upload bit count, type, or pixel size: Failed Verification
B239.bmp does not appear to be the correct size (1024.0004882812).
B239_N.bmp does not appear to be the correct size (1024.0004882812).
Still trying to figure out what broke that. Should have it nailed down Monday.
-
Regarding your colour shift problem. Initially I could not reproduce it, the 32-bit skin and normal maps looked identical to the 24-bit ones in both the viewer and the game. However after playing with Photoshop's advanced settings button on the bmp save menu I managed to get the same colour shift. The default advanced settings used by Photoshop are 16-bit A1 R5 G5 B5 and with that it looked fine. To get the colour shift I had to manually change it to 32 bit X8 R8 G8 B8. So just leave it on standard settings and it should work OK.
Yeah that fixed it. Thanks. A8 R8 G8 B8 must be used.
-
Thanks Skuzzy, the lighting effects on the Boston skin now appear to be working correctly.
I have gone through the file listings on the new submission page and found what seem to me to be some bugs. As much of this was checked prior to the latest revision you may have already corrected some of these.
A-20G: Add marking.bmp, plus the e,s,p and n versions of it.
A6M2: Add a6m2a.bmp
A6M5: Add a6m5ba.bmp
B5N2: Add b5n2_1_(e,n and p).bmp
C-47A: Add c47a.bmp
Camel: Add camel_1_(e and p).bmp, camel_2_(e and p).bmp
Remove camel(e and p).bmp
Change camel_(1 and 2)_s.bmp from 32-bits RGB to 8 bits grayscale.
Dr 1: Add dr1_1_(e and p).bmp, dr1_2_(e and p).bmp, dr1_1d_(e and a).bmp and dr1_2d_(e and a).bmp
Remove dr1(e and p).bmp
Change all (a, e, p and s) files from 32-bits RGB to 8 bits grayscale.
F4U-1A: Add f4u1a.bmp
FM-2: Change fmstr.bmp and fmstr_s.bmp from optional to required.
Hetzer: Change hetztrd_a.bmp from required to optional.
Jeep: Change jeep.bmp from optional to required.
Jagdpanther: Change pnthrtrd_a.bmp from required to optional.
Jagdpanzer IV: Change pz4trd_a.bmp from required to optional.
LVTA2: Change lvtrak_a.bmp from required to optional.
LVTA4: Change lvtrak_a.bmp from required to optional.
M16: Change m3a1trd_a.bmp from required to optional.
M18: Change m18trd_a.bmp from required to optional.
M3: Add m3a1in_(e and p).bmp
Change m3a1trd_a.bmp from required to optional.
M4A3/75: Change m4a3trx_a.bmp from required to optional.
M4A3/76: Change m4a3trx_a.bmp from required to optional.
Me163: Change me163sd.bmp and me163sd_s.bmp from optional to required.
Change me163wg.bmp and me163wg_s.bmp from optional to required.
Me262: Add me262a.bmp
Ostwind: Add pzrtrd_(e and s).bmp
Change pzrtrd_a.bmp from required to optional.
Panther: Change pnthrtrd_a.bmp from required to optional.
Panzer IV F: Change pz4tred_a.bmp from required to optional.
Panzer IV H: Change pz4tred_a.bmp from required to optional.
Sd Kfz 251: Change sdktrd_a.bmp from required to optional.
Spitfire Mk I: Add spit1a.bmp
T34-85: Add 34trax_(e and p).bmp (The T-34s' tracks don't seem to use alpha maps)
Tempest: Change tmpside.bmp, tmpstab.bmp and tmpstab_s.bmp from optional to required.
Tiger I: Add tiger1a.bmp
Change pz6tred_a.bmp from required to optional.
Tiger II: Change tig2trd_a.bmp from required to optional.
Wirblewind: Change pzrtrd_a.bmp from required to optional.
Thank you for the list Greebo. Finally got them all done.
-
Uploaded a new version. Added some debug output to the verification screen and changed the way the sizes are calculated for verification.
If you get a submission error, it will show what the file size should be so you can compare it to yours. It those numbers match, then the file size is changing before it is written to the server, and after it is read from your drive. I hope that is not the case, but let's see if it is.
This is going to be the last error to correct and then we can go live. I still have some work to do, but it will not impact submissions and updates.
-
I attempted to submit a N1K2-J skin but got the following error message:
Welcome to new skins validation page.
Object Name: n1k2 Verified
Skin Information: Verified
Skin Name: 343FG/301FS by Greebo Verified
Skin Files Verification
All Required files: Submitted
File upload names: Verified
size: 4194360
size: 1049654
size: 4194360
size: 1049654
size: 1049654
File upload bit count, type, or pixel size: Failed Verification
N1K21.bmp does not appear to be the correct size (should be: 4194358 currently is: 4194360).
N1K21_N.bmp does not appear to be the correct size (should be: 4194358 currently is: 4194360).
I'm loading the 24-bit BMPs produced by Paint Shop Pro into Photoshop and saving them as 32-bit BMPs before submission. Not sure if that is causing the error or the page is wrong.
-
That is what I needed Greebo. For some reason your files have a couple of extra bytes in them. It could be the header. Different paint programs can do some different things with the header which will not break things.
It only impacts the 32 bit files, it seems.
I'll adjust.
-
Ok, try it now (Version 3.0D.1)
-
The N1k-2 uploaded with no problems and I also successfully updated a 2048 res B-24 skin.
-
Well, let's bang on it some more today and tonight. If no more errors hit, then I'll officially turn it on tomorrow.
-
Submitted a 109K-4 with no issues.
-
Tried to submit a Sopwith Camel and got the following error report:
Welcome to new skins validation page.
Object Name: camel Verified
Skin Information: Verified
Skin Name: 28S/RFC by Greebo Verified
Skin Files Verification
All Required files: Submitted
w1gpilot.bmp appears to be incorrectly uploaded as .
That file is correctly listed as optional in the file list and I did not include it with the submitted files.
-
Ok, that is just strange.
I have added more debug output to try and figure out why that is happening. If you Greebo, just post that output. Thank you.
-
I just attempted to upload a Tiger I skin and got the error text shown in the attached file. The problem seems to be that the tank track files are all listed as a 256 x 256 on the page but are actually 256 x 128 files. Also the alpha file is still listed as required. Won't that stop submissions that don't include tank track files from working?
I'll have another go with the Camel.
-
Not good. This is a delay. I have to add another column to the database and then find all those odd sized textures. Thanks Greebo.
Still need to know what happened with the Camel submission.
-
I have attached the Camel error text, same result as before.
I had a look through all the different types of GVs I have skinned (all the German GVs except the flakpanzers) and they all have 256 x 128 size track bmps but on the web page all the GVs I looked at showed 256 x 256 size for the track files. I haven't looked at every GV but I'd guess they are all meant to be 256 x 128, Waffle would probably know. So I think it would just be a question of changing the track file size to 256 x 128 in the script.
-
Same as Greebo.
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
-
Same as Greebo.
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
That whole thing is messed up. Those files are 8 bit, gray scale, and are 1/4 the size being reported in the error. I have no idea how you got that error message.
Even if you submitted them as the incorrect bit count, it would have printed an error before this. Assuming the bit count is correct, there should be no way for that size to show for a 32 bit file.
Makes me crazy.
Are you sure the login screen was showing "Version 3.0D.2 (Beta) 12/21/2016"?
-
That whole thing is messed up. Those files are 8 bit, gray scale, and are 1/4 the size being reported in the error. I have no idea how you got that error message.
Even if you submitted them as the incorrect bit count, it would have printed an error before this. Assuming the bit count is correct, there should be no way for that size to show for a 32 bit file.
Makes me crazy.
Are you sure the login screen was showing "Version 3.0D.2 (Beta) 12/21/2016"?
I am about to submit a test skin to see what happens. Can I get a confirmation on what size the files *SHOULD* be for aircraft (in this case P-51D and B)?
I understand the primary is 32-bit. The others are all 8-bit?
-
If you take a look at the P-51D skins submission page it tells you all the required and optional files, their sizes and bit counts. For the P-51D and most skins though, the basic skin and normal file are 32-bit and the other files are 8-bit greyscale.
Skuzzy, are you aware the Ki-61 is a 2048 res skin?
-
Yes, and the database has the size correct, but the numbers reported by FTJR are not correct. Makes me crazy.
Working on a program to go through all the files and make sure all those values are correct (bits, format, width and height). Had to add two more columns to the database.
Greebo, I think the problem you saw with the Camel was a PHP timeout on the upload. I have extended it for the next series of tests.
-
I figured if anything would break the page it would be the Camel with its twenty bmps. Would it help if I tried to submit a Ki-61 skin?
-
I figured if anything would break the page it would be the Camel with its twenty bmps. Would it help if I tried to submit a Ki-61 skin?
TORTURE TEST!!!!!!!!!!!!!!!!! :lol
-
New version up!
Ok, let's give it a go.
Keeping my fingers crossed.
Might try one of those skins which has the different height and widths as well. Yes, the WW1 planes are quite intense.
I altered the timeout (doubled it).
Added two more columns to the database to take into account those asymmetrical bitmaps.
Reworked some more messages.
Reworked the size calcs, again.
-
sorry...
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
-
Tried to submit the Tiger I again but got this error message:
Welcome to new skins validation page.
Object Name: tiger1 Verified
Skin Information: Verified
Skin Name: s. Pz Abt 503 by Greebo Verified
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
PZ6TRED_E.bmp is smaller than the default allowed pixel size width (1024).
PZ6TRED_E.bmp is smaller than the default allowed pixel size height (1024).
So I tried a Jagdpanther, the only other AH III-format GV skin with track files I have done. This one uploaded successfully so the Tiger issue may be specific to that shape and not related to all GVs.
I also successfully submitted the Camel skin and a Ki-61 skin. My Ki-61 E, P and S files show a size of 4,195,382 bytes however.
-
sorry...
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
This should now be corrected.
Tried to submit the Tiger I again but got this error message:
Welcome to new skins validation page.
Object Name: tiger1 Verified
Skin Information: Verified
Skin Name: s. Pz Abt 503 by Greebo Verified
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
PZ6TRED_E.bmp is smaller than the default allowed pixel size width (1024).
PZ6TRED_E.bmp is smaller than the default allowed pixel size height (1024).
So I tried a Jagdpanther, the only other AH III-format GV skin with track files I have done. This one uploaded successfully so the Tiger issue may be specific to that shape and not related to all GVs.
I also successfully submitted the Camel skin and a Ki-61 skin. My Ki-61 E, P and S files show a size of 4,195,382 bytes however.
The PZ6TRED_E.bmp database entry was incorrect. Should now work.
-
By the way, I would not be surprised if there were some more database entries which need fixing.
-
I managed to submit the Tiger I skin without any problem this time and also submitted a Boston skin. The page has accepted just about every type of skin now, AH1, 2 and 3 , 1024 and 2048 res, WW1 and GVs so I think all the major bugs have been sorted now.
-
Well, I think it is worth going ahead and, officially, turning it on.
I have cleared any submissions or updates submitted.
Anything submitted after the date of the post will be considered an official submission.
I want to thank everyone for helping. A special thanks to Greebo who went above and beyond in finding the errors in the database. <S> all!
-
Still getting the error
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
For what its worth, when I clicked the submit button the wheel spun for 25 minutes before I stopped and resubmitted the page, the error was returned inside 5 minutes.
-
Ok, that is bizarre. Could you send me one of those files so I can figure out why yours are failing? Just ZIP it up and email it.
-
its on the way
-
I just noticed that the file sizes of the P-38J files I am working on are all 2 bytes larger than the corresponding original game files.
I use Photoshop CS6.
In an earlier post, Greebo says the file sizes and bit counts are available for the p51D submission page. I didn't see bit counts for the '38J files - are just compared the properties of my files to the properties of the original skin files to find out the counts.
-
Yes, there are image editors which append 2 extra bytes of data to the images. Does not hurt anything as they are not loaded due to the header containing the correct amount of data. I just have to manually check for the extra bytes, which I do.
-
What I meant in my earlier post was that the submissions page says what type the file should be: 32-bit RGB or 8-bit grayscale. Sorry if I phrased it badly.
I have submitted most of my skins now but ran into a problem with the Panzer IV H where I got this message:
Welcome to update skins validation page.
Object Name: panzr4h Verified
Skin Name: 24th Panzer Division by Greebo Verified
Skin Files verification
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
PZRSKRT_E.bmp is smaller than the default allowed pixel size height (1024).
PZRSKRT_P.bmp is smaller than the default allowed pixel size height (1024).
The PZRSKRT.bmp files are 1024 x 512 in size.
Also my Ju-88A-4 skin (ref: JU88A40112252016) uploaded OK but in the viewer the shape seems to have an issue with the normal and other maps not working. HT fixed a similar problem on the Boston so perhaps he can use these files to check out the Ju-88A-4.
-
OK, good.
It seems to be the validation error that FTJR is getting though - his submission files are 2 bytes larger than the submission verification is looking for.
-
OK, good.
It seems to be the validation error that FTJR is getting though - his submission files are 2 bytes larger than the submission verification is looking for.
Yes, but I coded for that.
What I meant in my earlier post was that the submissions page says what type the file should be: 32-bit RGB or 8-bit grayscale. Sorry if I phrased it badly.
I have submitted most of my skins now but ran into a problem with the Panzer IV H where I got this message:
Welcome to update skins validation page.
Object Name: panzr4h Verified
Skin Name: 24th Panzer Division by Greebo Verified
Skin Files verification
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
PZRSKRT_E.bmp is smaller than the default allowed pixel size height (1024).
PZRSKRT_P.bmp is smaller than the default allowed pixel size height (1024).
The PZRSKRT.bmp files are 1024 x 512 in size.
Also my Ju-88A-4 skin (ref: JU88A40112252016) uploaded OK but in the viewer the shape seems to have an issue with the normal and other maps not working. HT fixed a similar problem on the Boston so perhaps he can use these files to check out the Ju-88A-4.
This is a database error. I'll fix the panzer tred tomorrow.
The fix for the normal map should have gone across the board. I'll have to get HiTech to look at it.
-
Just to be clear it is the Panzer IV H skirt files that are the problem, not the tread files.
-
Right. Misspoken on my part.
-
Greebo, the PZRSKRT* files should work now.
-
Still getting the error
Skin Files Verification
All Required files: Submitted
File upload names: Verified
File upload bit count, type, or pixel size: Failed Verification
KI61_E.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_P.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
KI61_S.bmp does not appear to be the correct size (should be: 4195382 currently is: 4195384).
For what its worth, when I clicked the submit button the wheel spun for 25 minutes before I stopped and resubmitted the page, the error was returned inside 5 minutes.
This should be fixed now.
-
Just to let you know I submitted the Panzer IV H skins with no problems.
-
Welcome to update skins validation page.
Object Name: p51d Verified
Skin Name: 52FG/4FS by Vraciu Verified
Skin Files verification
File upload names: Verified
File upload types and pixel sizes: Verified
Thumb nail image: Not Submitted
Full size image: Not Submitted
Reference image 1: Not Submitted
Reference image 2: Not Submitted
Congratulations! Your skin updates have been accepted!
:rock :aok :cheers: :salute
-
This should be fixed now.
Congratulations! Your skin has been submitted!
thank you