I can understand how you move the interface elements around by modifying the translateX and translateY values. What I haven't been able to find is information on how the nTranslateBits value figures into modifying these values.

Hopefully one of you with more Flash experience can explain how we have to modify nTranslateBits when modifying the tanslateX & Y values.

Okay, here is another question. Has anyone figured out which sprite displays the Vault Boy animation in the bottom left third of the screen when a successful Charisma check is made when talking to Codsworth (at the beginning of the game, just after you get out of the vault)? I'm talking about the line where they introduce you to the different colored text options NPCs can present.

Just play about and explore, if you're given the answer you'll never have knowledge... you'd be like a parrot that can only say a few phrases in English.

I'm reminded of one of my job interviews, where the interviewer asked what I'd do if I didn't know how to do something - and the answer they really wanted to hear was "I'd ask someone."

They didn't want their staff wasting time re-inventing the wheel (heh, we've even got an expression for it)

Sadly, I know nothing about SWF so I can't help. Sorry.

Someone over at The Nexus pointed me to DialogueMenu.swf. It turns out the animation is in there. Here is what I posted over at The Nexus.


This means that anyone using the New/Full Dialogue mods will have to modify the version of the swf that comes with that mod if they want to do anything about those animations.

This isn't a company, and it's not re-inventing a wheel. This is about teaching someone to fish rather than giving them a fish.

Well I'm glad you found it.

There's also something known as helping someone out when they need it, or ask for it, rather than saying do it yourself.

We learn things by asking. Telling someone to do it yourself is the equivalent of giving them the finger, and not the least bit helpful to the situation.

I seem to remember when Skyrim first came out we had the" Modding The UI" thread around for quite a while (prior to SkyUI). The folks in that thread were asking lots of questions, and even one of the Devs came in and helped out by answering some of those questions. If those folks in that thread had taken your advice to play around, rather than asking questions, we might never have gotten SkyUI in the state it's currently in. Might've taken alot longer to do, if ever.

Thanks in part to that thread, and the helpful developer (forgot his/her name) we (as in not me) came away with a much better understanding of how the UI works now.

Got a problem? Ask away, don't simply try to do it yourself, stumbling around in the dark the whole time.

His problem was easily fixed by investigating the files, it wasn't a complex series of logical problems.

I posted the day the thread became 2 days old, where were the answers for him? He had to come and answer it himself by going somewhere else to find them, so it's nice to come out zealously when the issue is over right? At least I offered something, and it was something that, in the long-term, would have been best.

It would appear as though Fallout 4 is using the Autodesk Scaleform UI toolkit (which is based on Flash) so anything out there (tools, docs etc) that applies to Autodesk Scaleform would probably apply to Fallout 4.

Yeah, asking often does the job...if you keep the question easy...at least that's what I experience. Google is a much better teacher and answerer I figured...though it took me a while.