frankieorabona

actually 'A UNA' is correct in Italian. It is preferable to use it when there is a meeting between two identical vowels, or rather, 'ed' and 'ad' are only used when the word that follows starts with the same vowel.

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: I7 12700KF | GPU: NVIDIA GeForce RTX3070 | RAM: 32 I was entering some actions in the ACTIONS GROUP section and realised a translation that did not render the meaning well in Italian. In KSP, in the Italian language, GEAR was translated as "ATTERRAGGIO". Which rendered the idea of the ACTIONS GROUP much better. Now it is referred to as DEVICE, which is a very generic translation. I think it should be changed to 'ATTERRAGGIO' as in the first chapter of KSP Included Attachments: .ipsImage { width: 900px !important; }

How can I help you with the translation of the file? On the github repository there is no folder to create the various files with the Italian translation...could you add them? (https://github.com/KSP-CKAN/CKAN/tree/master/GUI/Localization)

Great! Just what I needed!

Thanks for the suggestion, but I don't use a VPN.

is there any way of creating 2d blueprint of my rocket, similar to this one:

Thank you for reporting this ... the problem also occurs in the forum when I quickly open two or more forum links within a few seconds. Same problem...

I'm trying to add some Italian page to the wiki, but every time I try to edit the page I have to wait for hours and hours because I get this error: It's really very frustrating, because as soon as you've done all the editing you get this error, with the risk maybe that you've spent almost an hour translating the page and you lose everything. The only way around this is to copy the changes and wait for the temporary ban to end (or log in from another network with a different IP and make the changes). Is there any way to limit this error? Also because not only do I get temporarily banned from the wiki, but also the whole forum.

I'm trying to translate some Wiki pages into Italian. The annoying thing of this wiki is that many components / planets / technologies are linked and displayed with the relative word and the suffix /it (for example Kerbin/it) Most of these problems I solve with the link, adding to the linked page the link with the Italian word Example: [[Electricity/it|Elettricità]] Another problem is the title of the page that is always displayed with the suffix! So KErbin translated into Italian will be "Kerbin/it". To this unfortunately I have not found solutions (and I do not know if there are). I hope in your advices Moreover I saw that there are many Dict templates, so there is already a dictionary of those words (for example parts) and inserting the word in English and calling the DICT template, it is translated automatically. In fact, yesterday I tried to translate the page KerbNet. In this page there is a template of a table where are listed all the parts related to Kerbnet. In this table all the parts are always displayed in English so it was "annoying" (or let's say not very accurate) to see the original names in English searching them in the game with other language (especially for parts for example without the siglas) So I used the {{if lang}} function with {{Dict/part name|xxxx}} E.g. [[M4435 Narrow-Band Scanner{{if lang}}|{{Dict/part name|M4435 Narrow-Band Scanner}}]] In the above case Wikipedia should directly display in the name taking it from the dictionary and pull out the translated name that should be: Scanner a banda stretta M4435 As soon as it was modified it worked, but this morning I reopen this page (italian version) and I see that it doesn't work anymore. Do you have any advice?

The main problem was the wheels...I unlocked the LY-10 and now it doesn't drift or veer any more

Removing the rudder/stabilizer it no longer turns left but right (LOL), in addition to that after 100 m/s it continues to drift. With SAS on, things get worse...I can't even reach 100 m/s. Doing so makes the aircraft unmanageable. I had already tried to tilt it, but straight remains the best solution with some takeoffs

Thanks for the advice...I have followed some of your advice but the situation seems to have gotten worse. In particular, I straightened the two rear wheels and moved the front wheel aft so that the plane is slightly tilted up. I have turning Rigid Attachment on for the landing gear I moved back the three upper flaps, but it did not improve at all, on the contrary now it is not only heeling but also veering to the left.

I need a plane to do surveys above 17000mts. I have designed this aircraft with a rocket, but on the runway when I exceed 100m/s the aircraft starts to drift left and right until it crashes off the runway.... Only rarely have I been able to get it off the ground. Do you have any advice? I post the file of the aircraft and some photos. My File - High Altitude Jet MKI

I have translated the few strings of the mod into Italian. How can I add them to the Github-repository?(I tried through github but it doesn't let me create a new file in localization folder)

@sarbian I built myself a controller for kerbal. As the KSP interface did not recognise some joysticks, I installed the Advanced Fly-By-Wire mod. I'm afraid this is responsible for the engines not turning on. Because uninstalling everything and reinstalling this mod, MechJeb doesn't work. Do you know of any incompatibility with the mod AFBW and MechJEb? Edit: I thought it might be because I use the slide potentiometer with my custom controller. But thinking about it, the Gravity Turn mod should have the same problem. Instead with this mod it can still handle acceleration smoothly. So I can't understand why I can't get the throttle to work (and therefore start the engines).

First of all, thank you for your reply... The solution could be to uninstall all the other mods (few to tell the truth) and reinstall them 1 at a time to understand which one conflicts with MechJEB?

Sorry, I thought that the .log should only be attached in the event of a crash. Here it is: https://www.dropbox.com/s/c4p7insdu8viuol/Player.log?dl=0

I have some problems with the mod. With any function (ascent guidance, maneuver planner, landing guidance etc) it does not turn on the engines. For example, with the landing guidance I set the target where I want to land, then I click on "land at target" ... but nothing happens, or rather it gets into position but does not turn on the engines (obviously also by clicking on "land somewhere" the same thing happens). Even if I try to circularise an orbit, it doesn't turn on the engines. It arrives at the node with the time warp and then nothing happens, and the same happens with ascent guidance. What's wrong?

It works now. I had to rename the file as you told me to it-it.cfg, but that alone didn't work. Also within the file I had to replace the string localization en-us with it-it. Now it works. When I'm done do a pull request on github?

Thank you for your suggestion... I'll try to create the it-it.cfg file, but shouldn't editing the en-us.cfg file work anyway, since it reads the English language? Also, I'm sure of what I'm translating, because I took the word Settings as a reference...it only appears twice individually (I used the search function with notepad++) but even though I translated it, it doesn't appear in Italian...

I would like to try to translate the mod into Italian language. I'm trying to edit the en-us.cfg file in the MechJeb2/Localization folder, but nothing happens if I restart the game. How can I proceed to test the translation?

The encoder does not need a drive and is recognised as a simple HID joystick. I have however solved (partially) by installing AFBW

Thank you for your help, but I see that unfortunately I am not the only one with this problem. And it is a problem that has never been solved from what I read. My joystick is this one: Connected to an encoder (A-PAC). Powered on. BUT it is not a power supply problem.

It was recommended to me for another problem with the joystick....I suppose it is really important to download it... I wonder how a game with such a large following can still have such bugs, which have not been fixed! I don't know what you mean by powered and plugged, but if other games recognise them I don't see why KSP wouldn't. I've restarted KSP at least 50 times today... and disconnected and reconnected the joystick to all the USB ports on my PC. The same thing always happens...

I have a problem with the joystick axis assignment. I have 2 joysticks but it does not allow me to map them. Let me explain better. When I go to configure the joystick the pitch axis for example, it recognises joy1.0 (axis 0 joystick one), but when I click on accept it gives me Joy0.0, so when I enter the KSP game it does not see the joystick. Same thing with joystick 2... it always accepts it as joy0.0. The problem is similar to this: Is it possible that this problem has not been solved since 2016? Do you have any suggestions?