A.J.

  I bet five bucks it's the vertex color. Did you try to set Has Vertex Color to No under the NiTriStripData?

Inside the Material Property of that node, did you already check things like Emittance and Glossiness? I would also check if it has the same shaders inside the BSShader

Here too people were saying it's a fake, and that pic was some photoshopped Anthology.   When I see these news I always hope they're true... but I admit I more hope to see FO4 before TES 6...

  Yeah I played that one too. Memories are very blurry. I remember the giant ant with a lot of small ants, and you were taking the quest from the major of this big town. I think it was this one:   http://www.nexusmods.com/fallout3/mods/7705/?

  It's a custom script, try to send him a pm and see if he wants to give it to you

Thank you very much!

As expected, English version solved the issue, and now I have a QWERTY...

I think I found it. I can't test it since my Steam is re-downloading NV and it will have to do that for maaany days. However, fortunally I can still launch the GECK...   Aaaand... browsing all these strings (where I've found all my AZERTY mapping), I also found one of the strings was translated in french... this would confirm me thinking that they did a mess mixing countries and languages...

Odessa, to make my tries, I already mapped via script the keyboard differencies (so you can set some var which chooses the keyboard). Anyway,  I still think it doesn't make completely sense, this damn bug, I guess you can see my point of view... who can really say how many countries have this "issue"? My english NV is at half download on steam, if it will solve my issues I'm going to screw and forget IT version. Let's see pros and cons. Pros: it probably will solve that, it will solve the misplaced IDs vs american people, I'll be able to install TTW... Cons, I won't be able to hear anymore those annoying wrong translations of dialogues. Oh, that should stay in the Pros yeah, I guess that's a good moment to stop being patriotic!!!

Yeah I told you If it was NVSE, I wouldn't feel so sick. It is the game, since I have the same exact wrong mapping when I manually decide the key mapping inside the options of the game (there's a specific sub-menu, something like main menu - Controls - Decide your keys: I press Y and Z appears...). English version is already downloading, I really bet it will solve this... And I think the game stills take some setting from Windows, because in console I write correctly, if you think. But not in game. But console IS in game. But not that part of the game. Insane... PS I also tried my old keyboard (PS2 instead of USB), just to be sure, but it's the same. Also, I just had confirmation from another IT player: he too had to take items in containers with A instead of Q.

I still have this issue. Prideslayer, you know what I think? this is a bad mistake they did.   Here's the absurd assumption I'm having right now: The game uses scancodes to handle the controls, like if you press scancode 17 you are walking forward (then has a sub-table which attribs controls to scancodes etc. but it's not interesting). However, the game has an internal table which uses for text, and it is different from languages. So, they somewhat think to a message box like "Press <scancode 17> to walk" and then it's translated to "Press W to walk" for a UK and "Press Z to walk" for a French. I'm not referring to the actual tutorials / messages boxes, I'm more referring to something they did during the development, like using some placeholder that was then automatically replaced during the translation. Yeah, that could even have been a nice idea, if you think that one day you'll translate it in different languages: you load different keyboards, then when you translate the game the keys specified inside the tutorials are translated too based by the keyboard you are supposing to use. Anyway, somewhat I finished inside the francophones group, and this is the first issue. The second issue is they messed up with the AZERTY table, mixing the values with QWERTZ, so that there are two Z. But as I said, it's just text, because the scancode still returns correct, you only see the wrong letter on video (so GetKeyName function IS ok, but the result on video is wrong).   Is this assumption insane? sure, but how many insane things there are in NV?... If I had the Wild Wasteland perk, probably I would hear the jingle right now... wo-hooo-hooooo...   I'm not going to re-map my keyboard with a third party software since it still won't solve the Z issue.   I'm going to switch language via Steam tonight, in few days I will download the english version. If ithen I won't have this issue, then my absurd conspiracy theory is true: they don't like us

Oh god no *laughs* I think there's a lot of misunderstandings here I continue to not understand, and I don't get why.   Your key tweak software answers with 16 (NOT 30) when I press the first letter (Q). If I check the NVSE scancode list, it says that at 16 there's Q. In game, if I open console and I press Q, it writes Q. In game, if I do GetKeyPress (Q) it answers 30.   Every IT game sets the keyboard automatically correct, I never touched it. I think they get general settings of windows (which is IT language - IT keyboard - QWERTY) Still, in the game there could be some setting, in some ini, which forces it to AZERTY, sure. But then, why game console writes correctly? Isn't it IN GAME? ...   Last, I don't think it mixes the two keyboard, as I said the specific issue with Y comes from the NVSE function, but I've seen you didn't read it.   EDIT: ok I give up, since what I found disconcerts me too much. I remembered there's the possibility to change keys in the menu, so I did. All my keys are mapped BY NEW VEGAS as if I have a AZERTY, EXCEPT the Y which appears as a Z (SO I HAVE TWO Z, FOR NEW VEGAS, ONE OVER THE W AND ONE OVER THE Y) but it has a different code. In fact the Z over the W doesn't act like the Z over the Y I think this is the first time I feel to say they did cr*p, they did a huge amount of cr*p. Even when I found about the misplaced IDs I didn't think that, I thought "oh hey, it can happen...". But this is way too much. Damn Beth/Obsidian/whatever.

My scancode is correct, Pride, the first row answers these numbers since it's a QWERTY. It's only ingame that answers bad. GetKeyPress (my Q) returns 30 which is A etc. It returns all the scancodes like if I had an AZERTY.   The only exception is the Y, which returns Z like the W. This is because of GetKeyName acting strange.   GetKeyPress (My W) >>> 18 GetKeyName 18 >>> Z (because it's AZERTY in game) But: GetKeyPress (my Y) >>> 21 GetKeyName 21 >>> Z (which is simply wrong)

Ok, I think I'm on the bottom of the thing then, nice Excluding the GetKeyName possible issue on scancode 21, I guess there's nothing else than what Pride already told

I attached above the script I'm using:     Let iCharIndex := GetKeyPress 0     if iCharIndex == -1     else         Let sCurrString := GetKeyName iCharIndex         Print sCurrString     endif When I press the keys, it prints me on console the scancode. When I press Y it prints Z   EDIT: I actually used a workaround:         if iCharIndex == 21             Let sCurrString := "Y" But I tracked it down, it seems that GetKeyName translates wrong when Index is 21   And this is the difference from the two keyboards, the "translation" I did from my IT keyboard and the resulting ingame scancode. At least for what concerns letters which is what I care. if iCharIndex == 16 ; Q Let iCharIndex := 30 ; A elseif iCharIndex == 17 ; W Let iCharIndex := 44 ; Z elseif iCharIndex == 30 ; A Let iCharIndex := 16 ; Q elseif iCharIndex == 17 ; W Let iCharIndex := 44 ; Z elseif iCharIndex == 44 ; Z Let iCharIndex := 17 ; W elseif iCharIndex == 51 ; Comma Let iCharIndex := 50 ; M

I can understand that, it is cool. Now still there are those two details that are not explained: why there are two Z, one over the Q and one over the Y, and why Jaam with an AZERTY keyboard has a QWERTY answer from the scancode.

Odessa, I think you misunderstood the issue. The keyboard writes fine in console, while doesn't write fine in game. I think this is how the game interprets the scancodes, but it's actually sets to work with the right keyboard. So it's not even a windows setting   I write Q, it is a Q because on console I see Q, but scancode returns 30 which is A (it emulates like an AZERTY, but not really, because it makes AZERTZ) Also, read how Jaam has the opposite, he has AZERTY and scancode returns as it has QWERTY...

I play with italian keyboard which is qwerty. it is different by US but only for symbols. EDIT: I play with italian NV version. you confused me more, you have azerty and it gives qwerty? but on console you still write with azerty? oh god...   jaam I thought about the first line I mapped, the fact I have two "z" (one over q and one over y). Could it be that one of the two NVSE functions I use makes a mistake and puts a z instead of a y? this is what I'm doing:     Let iCharIndex := GetKeyPress 0     if iCharIndex == -1     else         Let sCurrString := GetKeyName iCharIndex         Print sCurrString     endif

SCANCODES   Since I started playing NV (but same happens in Skyrim), I noticed there are differencies on the keys. At start I thought it was because of the differencies of a US keyboard with a IT keyboard, but then I looked for pictures and I saw it's not in this way. We both use QWERTY and the differencies are more on the symbols, like you have {} while I don't have them etc.   So the problem essentially was that the ingame keys weren't those described in the menus. For example, if it says "Press Q to take all", I must press A instead. As player, I didn't have big issues, I thought it was a bug on the things written in menus, so I automatically was presisng A when it was asking for Q etc.   But now, on a script, I just realized that maybe it's something else, maybe it involves scancodes. That's somewhat disconcerting. If I press Q, it returns the scancode of A and viceversa. Still, you could say "it's the keyboard", but hey, my Q is in the same position of yours, how can I know that... I thought these things were pretty much standard for languages, that the differencies were more linked to QWERTY / AZERTY etc. but it's not in this way so I would love to understand better. I looked for some hypotetic IT scancode table to compare with a US scancode table (if it's silly, also think I know nothing about this subject) but I didn't find anything, I always find a single standard scancode table, in hex, I convert it in dec and I find the same NVSE scancode table, and it tells me that Q is 16 while for me is 30.   So... please, can someone who knows about it explain me this?   EDIT: I mapped what scancode gives me back My keyboard                  Scancode result qwertyuiop                     azertzuiop asdfghjkl                         qasfghjkl zxcvbnm                         wxcvbn,   the most weird is the first line, it has "z" twice, one over q and one over y if it wasn't for that double letter, I would have said it is an azerty keyboard. But still, why console writes letters ok? why in game commands are not ok? why scancode gives me results similar to azerty? I can't get this all...