Have you considered activating web colors on the Photoshop color picker? I found it helpful to pick a fairly color close to the one I used in the livery.
Oh yeah, been doing that. The shade never quite matches, but I’m trying again using only the R slider for RGB and using the hexadecimal color for that. We’ll see.
Now if “we” can just get rid of that stupid white “box” the registration go on, OR at least change the color from white to transparent, we would be SO much better off!
TB2
1 Like
Brillant.
Thank you
1 Like
Does this not work a SU11?
painting00=Registration/Registration.html?font_color=black&stroke_size=25&stroke_color=0xc09d57&, 107, 27, 606, 147
only the black shows up not the gold outline.
Still can’t get this to work!
I can’t get it to work either.
Shouldn’t the .css file bottom line be changed from:
registration.css.map
to:
registration_cob.css.map
?
Its a 2 years since I looked at this. So I have no idea if the .map file needs to be updated. However I think I did all the changes without it.
Did you see the solution in devsupport?
Essentially, Carenado has co-opted the default Livery Registration CSS’s, so you have to create your own version. I’m kind of getting it to work. By making a registration CSS local to your own package, you can copy the default livery registration stuff to your own livery and get stroke to work. And, if you’re good at CSS, probably do anything you want… Within the bounds of the decal upon which the Registration.css is acting…
I used the the latest C152 from WBSim as an example of how to make registration your own and bypass the Carenado screw up.
1 Like
I think this is what got broken at SU9
painting00=Registration/Registration.html?font_color=9a0000&stroke_size=50&stroke_color=0x6392A5&fomt_style=Bold, 0, 0, 1024, 256
They seem to have overwritten the base registration.css with their own "old: version, and then made a new new_registration.css, which the actually use !!
They should NEVER have overwiten Asobo’s base registration.css – BUT they may have realized that later and hence created their own new_registration.css … but they seem to have FORGOTTEN / FAILED to no longer include their modified original registration.css in their package, which is now still overwriting the base one, even through they are not actually using it. - but it is messing up almost ever other plane in the sim !!
a real Cluster “mess up”
1 Like
As I said, there is a fix. Carenado (and possibly other vendors) broke it by using the old default code that didn’t have the stroke information in it. Asobo’s code still works, unless you have an addon that did what Carenado did. Review the Devsupport thread all the way to the bottom. I’ve gotten it working again in my liveries.
I’m trying to figure out how to add a “stroke-linecap: square;” tag to the css so I don’t get rounded corners on the stroke line.
1 Like
#1 thing to do is to delete the rogue registration.css from the Carenado planes, and then re-build their layout.json.
Then MSFS planes will be using the current Asobo Official registration.css, unless a plane has its own version that it references.
This is what I have done - but have to keep doing it every Carenado Update, till they get it right.
1 Like
