Hello, tis the pest again
Been looking at the UK squadron codes and found three where you have the pre war letters rather than the codes used during the BoB.
79 Sqdn you use "AL" and should be "NV"
152 Sqdn you use "UM" and should be "SN"
229 Sqdn you use "RE" and should be "KE"
The bit that puzzles me is that you have the correct codes in the .ms file for all three units, strange.
ie:
use MultiSkin\MultiSkinTextures\UM.dds,2048, 2048, 0.11, 0.055, 1100, 768 if unit == Sq"SN" # No 152 Sq.
Cheers Ron
Multiskin UK code errors
Re: Multiskin UK code errors
I checked the initialization data for all three units. That data is correct. NV, SN, KE
The error happens after base data read into engine.
The error happens after base data read into engine.
Re: Multiskin UK code errors
I agree with that but multiskin then gave them the prewar codes and thats what they show. Your timing is spot on again as I've just made up all three correct codes and altered my MS lines for them.
Is there anywhere I can send these .dds files now so that MS can be updated?
Is there anywhere I can send these .dds files now so that MS can be updated?
Re: Multiskin UK code errors
I am guessing that you should PM Cherkassov54 who is working on multiskin atm. Also, in the PM, place a link to your file. If you don't have a place yet to post files, then I recommend mediafire.com (It's what I use.). Free account will handle most needs.
Randy
Randy
Re: Multiskin UK code errors
Right, Cherkassov54 is our current MultiSkinner. Best that he compiles his and your work together.
He is finished with his ME110 multisikns, and most of the LW Lehr Gruppe multiskins, which are these units:
I/LG2 for III/JG52
EG210 for I/ZG76
V/LG1 for III/ZG2
IV/LG1 for III/StG2
II/LG1 for III/KG54
All are finished I think except maybe II/LG1 which is still ongoing.
I have his work on all the other Lehr units and the new ME110 multiskins, but have not yet fully tested all units,
as I am busy with my Anti-Aircraft Command Project and remaking some Targets historical.
New Sheerness Docks, Eastbourne "Docks" and a new Newhaven Docks placed where it should be.
PV made new real terrain for these places, too.
Anyway.. we could use a MultiSkin tester to see that all MS units are OK. Me and two27 are the only ones that briefly have looked at it.
I found one fatal fault (a typo error in one .ms line where a t was inappropriately inserted) which has been corrected.
Also someone like you that sees faults that should be corrected and seems to read the MS lines well enough to make corrections.
Are you interested in joining the BDG to work with us and do some testing and/or modifications?
He is finished with his ME110 multisikns, and most of the LW Lehr Gruppe multiskins, which are these units:
I/LG2 for III/JG52
EG210 for I/ZG76
V/LG1 for III/ZG2
IV/LG1 for III/StG2
II/LG1 for III/KG54
All are finished I think except maybe II/LG1 which is still ongoing.
I have his work on all the other Lehr units and the new ME110 multiskins, but have not yet fully tested all units,
as I am busy with my Anti-Aircraft Command Project and remaking some Targets historical.
New Sheerness Docks, Eastbourne "Docks" and a new Newhaven Docks placed where it should be.
PV made new real terrain for these places, too.
Anyway.. we could use a MultiSkin tester to see that all MS units are OK. Me and two27 are the only ones that briefly have looked at it.
I found one fatal fault (a typo error in one .ms line where a t was inappropriately inserted) which has been corrected.
Also someone like you that sees faults that should be corrected and seems to read the MS lines well enough to make corrections.
Are you interested in joining the BDG to work with us and do some testing and/or modifications?
Re: Multiskin UK code errors
It's interesting: it looks like the Multiskin letter code .ms files
were partially updated, but the replacement image files weren't
created, so the file pointers remained unchanged. I guess
Bader had it scheduled to do but never completed it.
were partially updated, but the replacement image files weren't
created, so the file pointers remained unchanged. I guess
Bader had it scheduled to do but never completed it.
Re: Multiskin UK code errors
Hi stickman
Yes I'm happy to help where ever I can.
I know nothing about the Luftwaffe colours or code but I'm sure google and his friends can help where required.
Thanks Randy,
Have to pop out for a few hours but I'll do the PM when I get back, think I've got somewhere to hold the files (which I have tested and are OK. The only fault I can see on the British side is the 85/263 and as we discussed I can't find the problem which we both believe is in the original software and not multiskins.
Cheers Ron
Yes I'm happy to help where ever I can.
I know nothing about the Luftwaffe colours or code but I'm sure google and his friends can help where required.
Thanks Randy,
Have to pop out for a few hours but I'll do the PM when I get back, think I've got somewhere to hold the files (which I have tested and are OK. The only fault I can see on the British side is the 85/263 and as we discussed I can't find the problem which we both believe is in the original software and not multiskins.
Cheers Ron
Re: Multiskin UK code errors
I am no MultiSkin expert, but given a user editable text file,
I can pour my eyes over it and spot some things that look out of place, and do not match the pattern of the usual rules.
This one I found in the Me110_MainSkin file. That Bill was hacking->
use MultiSkin\MultiSkinTextures\bf110_trans.dds if unit == Gruppe"2SL" and planeid == 8 and date >= Sep5tht1940] #Stab
The errant t that Bill put in for his recent make of of a Lehr unit was killing me.
After I removed the bad typo t, and game worked, I posted my test result.
Bill replied that he also found and fixed his errant t typo at the same day that I did.
OK.. 4 eyes are always better than 2 eyes. I love over-sight & confirmation!
At work at the oil refinery I usually prefer to work alone.
Then.. all too often I wish that I had a mate to hold a flashlight over my shoulder so as to shine a light onto what the fakk I am doing!
I hate to stick a flash light (torch for UK folks?) into my mouth to illuminate my workings!
and tell him that I have a man that I wish to recruit.
When the British captured and broke the German code, and the Germans did know that it happened, then the war was over.
Just a matter of time and how much more blood be lost 'til the thing is done.
US Americans broke the Japanese code, too, in 1942. We knew everything that they were doing that we could hear on the radio!
Just a matter of time, production, and blood.
I can pour my eyes over it and spot some things that look out of place, and do not match the pattern of the usual rules.
This one I found in the Me110_MainSkin file. That Bill was hacking->
use MultiSkin\MultiSkinTextures\bf110_trans.dds if unit == Gruppe"2SL" and planeid == 8 and date >= Sep5tht1940] #Stab
The errant t that Bill put in for his recent make of of a Lehr unit was killing me.
After I removed the bad typo t, and game worked, I posted my test result.
Bill replied that he also found and fixed his errant t typo at the same day that I did.
OK.. 4 eyes are always better than 2 eyes. I love over-sight & confirmation!
At work at the oil refinery I usually prefer to work alone.
Then.. all too often I wish that I had a mate to hold a flashlight over my shoulder so as to shine a light onto what the fakk I am doing!
I hate to stick a flash light (torch for UK folks?) into my mouth to illuminate my workings!
OK, I will write to Buddye, whom is the BDG Beta Testing forum moderator,Hi stickman
Yes I'm happy to help where ever I can.
and tell him that I have a man that I wish to recruit.
Always know your enemies colors and codes!I know nothing about the Luftwaffe colours or code but I'm sure google and his friends can help where required.
When the British captured and broke the German code, and the Germans did know that it happened, then the war was over.
Just a matter of time and how much more blood be lost 'til the thing is done.
US Americans broke the Japanese code, too, in 1942. We knew everything that they were doing that we could hear on the radio!
Just a matter of time, production, and blood.
Re: Multiskin UK code errors
Jeez, don't you have an LED headlamp for your hardhat?stickman wrote:
Then.. all too often I wish that I had a mate to hold a flashlight over my shoulder so as to shine a light onto what the fakk I am doing!
I hate to stick a flash light (torch for UK folks?) into my mouth to illuminate my workings!
They're all the rage. I use 'em whenever I'm crawling around
in the pit in Japan. OK, I admit at times it's hard to get
the lamp to point onto the work when the brim is in the way...
Re: Multiskin UK code errors
Yeah, I have a good LED hard hat light. Works OK and the LED light is great.
It doesn't always point just where I want it though, and my fingers in the way.
My point is that is always to better to have 4 eyes than 2, plus, 2 lamps than 1.
Speaking of work..
This 5 year Turn-around planned total shut down has been the worst of all of them at the refinery.
I went thru four of them.
Three weeks behind schedule even though the place was packed with 600 contractors on day shift.
Scaffolding, cleaning machines, and cranes every where so that a guy has a hard time walking anywhere, let alone driving.
The piping contractors took forever to get new valves installed, and one company bunch was asked to leave.
The Chevron engineering and parts ordering was (not surprising considering some engineers we have) atrocious.
Only good thing was we only had about fours of heavy rain.
Anyway.. I'm exhausted and still have the start up phase to go through with the same 12 hour day shifts 6 or 7 days a week
until maybe the middle of June, depending on how many problems pop up, and there likely will be many!
A joke in the Instrument & Electrical shop last week:
"Well we now can see the light at the end of the tunnel."
"Yeah, that's a train wreck headed your way!"
It doesn't always point just where I want it though, and my fingers in the way.
My point is that is always to better to have 4 eyes than 2, plus, 2 lamps than 1.
Speaking of work..
This 5 year Turn-around planned total shut down has been the worst of all of them at the refinery.
I went thru four of them.
Three weeks behind schedule even though the place was packed with 600 contractors on day shift.
Scaffolding, cleaning machines, and cranes every where so that a guy has a hard time walking anywhere, let alone driving.
The piping contractors took forever to get new valves installed, and one company bunch was asked to leave.
The Chevron engineering and parts ordering was (not surprising considering some engineers we have) atrocious.
Only good thing was we only had about fours of heavy rain.
Anyway.. I'm exhausted and still have the start up phase to go through with the same 12 hour day shifts 6 or 7 days a week
until maybe the middle of June, depending on how many problems pop up, and there likely will be many!
A joke in the Instrument & Electrical shop last week:
"Well we now can see the light at the end of the tunnel."
"Yeah, that's a train wreck headed your way!"
Re: Multiskin UK code errors
The light at the end of the tunnel has been an oncoming
train for many decades now...
train for many decades now...
- Cherkassov54
- Staff Sergeant
- Posts: 345
- Joined: 01 Sep 2005, 15:54
- Location: Dundee
Re: Multiskin UK code errors
Whopee!
And thanks.
And thanks.
- Cherkassov54
- Staff Sergeant
- Posts: 345
- Joined: 01 Sep 2005, 15:54
- Location: Dundee
Re: Multiskin UK code errors
Re the cure for the 85/263 problem. Is it something I can do myself for my own copy or was it a bit more than that and I'll have to wait for an update to come out?
Who is online
Users browsing this forum: No registered users and 19 guests