25 réponses à ce sujet

[Lady1Aph]

I have a kinda wierd thing going on with the last part of Ilos where u have 40 sec to get to the Conduit. Ive finished the game 5 times so far and this is my 6th time, but this time i cant seem to get to the Conduit on time seems like im out of time even before i get to the second colossus. ive tried it about 20 times now and no matter what i do it seems like im losing all the time just getting to the bottom. Ive tried just driving in a straight line, ive tried zigzaging to not get hit ive tried the booster to jump when shot at, but no matter what i do im at 15 sec ( thats just driving in a straight line, no turns or anything) when i get to the bottom and having to get past those colossus, when i get to the last two colossus i only have 3 secs left of my time.
So is that a glitch or am i doing something wrong, since all the other times i got past it in my second try.

Sorry about the writing im not that good at explaining my self on text.

Modifié par Lady1Aph, 30 septembre 2010 - 03:07 .

[PlumPaul93]

Are you sure you didn't save with time going off the counter? Also I'd say when you get to the first part on the bottom try cutting through instead of turning. Not really much help but basically don't stop for anything and go as fast as possible Good luck .

[Lady1Aph]

i did all of that and i also saved before the cutscene. i even tried a earliere save and not saving before the cutscene, same thing i still lose time fast. The funniest thing is, that i dont even attack or turn at some points, still the same thing when i get to the second colossus im out of time, its like just the trip to the bottom takes all my time even though im driving in a straight line no turning or anything.

Modifié par Lady1Aph, 30 septembre 2010 - 03:13 .

[The Grey Ranger]

There was an issue for people who had a low frame rate. The solution was generally to turn down some of the graphics to improve the frame rate.  There was also a suggestion that you aim your point of view as high as possible to cut down on the number of objects that had to be rendered. 

It might be worth a try.

Modifié par The Grey Ranger, 30 septembre 2010 - 03:58 .

[Lady1Aph]

The Grey Ranger wrote...

There was an issue for people who had a low frame rate. The solution was generally to turn down some of the graphics to improve the frame rate.

i know that but my graphics shouldent be an issue since i have games like half life 2 alpha protocol running on high with no problems, aswell as ME2 and ive never expirienced it before hell ive finished the game 5 times already where it wasent a problem.

Only thing i can think of is that my computer dosent like my trying to be renegade instead of paragon

[The Grey Ranger]

If you still can't get it to work, you might try the following:



Enabling The Console



To enable the console, browse to and open the file Mass Effect\\Config\\BioInput.ini (the full location is mentioned above) in any text editor (Notepad, for example), but not with rich text editor (Microsoft Word, OpenOffice Write, WritePad, and the likes).



In the file you opened, search for [Engine.Console], and add the line ConsoleKey=Tilde just under it.





This will enable the dev console with some codes

1 get out of the mako.

2 use the pause aim to point near the conduit, pull down the console (hit tilde) type teleport.

this will teleport you to the aim point.

3 then use the console to spawn a new mako(SpawnVehicle)

4. drive your new mako through the conduit.



For more info on the dev console try http://masseffect.wi...om/wiki/Console

[Lady1Aph]

ill have to try that out then since ive tried about 40 times now with same result cant only get to the second colossus and my time is totaly out even tried a few time driving full speed made 1 turn and the straight again, and my time was up at the first colossus. lol

Modifié par Lady1Aph, 30 septembre 2010 - 06:35 .

[Admiralce]

this might help

[Lady1Aph]

No need for help anymore seems it was some kind of error with the game cause a reinstall of the game seemed to fix the problem.

[The Grey Ranger]

Well I'm glad something worked.

[Domar]

Well, in case someone else would like to know, I had the same kind of frustrating "impossible" problem there, but eventually discovered, as The Grey Ranger noted, that keeping the camera angled from above the Mako speeded up the run and enabled the company to reach the Conduit in the very knick of time before being blown to pieces. Phew! Probably the sweatiest part of the whole game...

[Lady1Aph]

well i found out that my problem was that my timer just went alot faster than my actual graphics. Kinda wierd that playing ME1 ill have to have all my graphics settings at low, where to the fact that all other games i play they are on high. hell i play Half Life 2/ episode 1&2 on high aswell as ME2 and other games like that without any problems at all. But ME1 seems to tear my graphics down funny enough, even though that wasent the only problem i had, also had somekind of error in a file, helped after an reinstall.

[hamtyl07]

that never seemed to happen to me i just basically floored it the hole way and made it my timer always around 14 to 15 sec left to make i dont think i've ever fired any of the guns on the last run through the trench

[Domar]

@hamtyl07 - I guess your PC-figuration is much more powerful than mine (3 GHz Pentium 4, 3 GB RAM and GeForce 9600 GT). Spending time aiming and firing at the four Colossi was never an option for me, just run for my dear life. Still did not make out of the water often (this with display resolution at 1680 x 1050 and all graphics settings on max).



@Lady1Aph - Yes, I've wondered if that timer always really gave me 40 seconds. Never checked it though. ME1 also does drop strangely in frame rates sometimes. ME2 runs much better somehow, never giving me this kind of problem. But I have the Steam version of ME1 whereas I kept ME2 Steam-free. I suspect this has some part in explaining the differences in frame rates.

[Lady1Aph]

@Domar well i dont have the steam version of ME1&2 they are digital downloads, but i do know steam since i have Half Life2 and Half Life episode 1&2 on steam. but i dont think it has anything to do with steam that the framerate suddenly drops, cause it seems to happen no matter wich version of the game u have.

[PnXMarcin1PL]

simply rush through the river avoiding any road bumps and dont fight those 4 colossus (they will be eliminated later by citadel expeditionary forces on ilos)

[Either.Ardrey]

I am playing at the lowest possible settings, and my frame rate is still shot to about 5-10 fps, which is completely screwing with this part of the level. I'm going to go with the console for this one part because there's nothing else I can do in this situation. I think you have to have a pretty hardcore near-modern(late 2009 or so) computer to even run it seamlessly on all low settings. When they put the minimum specs on the box, the game should have been at least fully playable on low AND casual.

[Either.Ardrey]

Recommendation for frame rate problem: Change the view so that you're looking down directly at the Mako only. I found the tip while searching for help on this part and it drastically helped the framerate, because it was only rendering the ground and the Mako. The difference was over 10 seconds of improved time on a laggy computer.

[Gexora]

Folks, I am sorry for basically bumping long-dead thread, but I am pissed and I guess its better than creating the new one.
So here I was making my ideal pre ME2 playthrough happen and then this situation screws me up. I tried all the above solutions, INCLUDING console - but it doesnt work for me (I cannot teleport while in Mako, I cannot get out of Mako to teleport until I get to the bottom of the trench thingy because the surface ain't level enough for that son of a b**ch tank, and since with the lowest possible graphics it still takes about 35 sec to just get down, when we are on the level terrain, there is no time to teleport!).
Is there any other way to pull through? Like disabling the clockdown via console or using superspeed command... like ANYTHING? Pleeease tell me there is

[Bogsnot1]

Sounds like your hardware is too underpowered to be able to handle all the action ofthe trench run adequately. All I could suggest is using the StasisAll console command to freeze everything, then once through the conduit, save and then load to re-enable the NPC's movement.

Note that if you have problems with the trench run, you are going to have problems with other sections of the Citadel.

[Gexora]

The weird thing is I have played the game to the end several times already (it's my Insanity plthr), and I have never had any problems...
Stasis All is useful against Colossus, thnks. But I can't even make it to Colossuses!*supreme frustration*I will try now going back and then teleporting forward...

[Gexora]

Ok never mind me I did it)
Alternate solution shall anyone need it - speed up via console, run up to the conduit (takes like ten sec) spawn car and own it

[Mr Zoat]

Could try looking straight up.

[Thor10]

 So this is my first time playing, and I'm having the exact same issue. The console won't work, I've tried putting it on lower settings and even zooming in/putting the target up. NOTHING IS WORKING AND IT'S MAKING ME NUTS!
Could someone please help me? It's a PC game, my computer works fine for Dragon Age Origins and DA2, but this part in ME is frustrating.

[Cortyman]

Well, here is what happens if you are just milliseconds too late for the conduit:

Modifié par Cortyman, 22 mars 2012 - 02:50 .