Access Violation?

[LaSeandre]

I keep getting "Access Violation : 0044...." "Error Location: Unknown" when I try to select items from the BR pack in Scenario Editor. Any help again?

[Plastikman]

You touched it in its naughty bits!

Are you sure it was BR and not the highspeed pack?

it might already be a known bug that I am not aware of. I find the BR set stable myself. perhaps it might help the BR dev's out if you listed the train that was breaking.

(the patch to fix the HSpack is in the HS pack support thread)

[rdrdrdrd]

think it's the 314 (strythacade)

[Plastikman]

the orange one? weird it works for me.

When I repacked the BR 4.5a set, I tested it fully.

I am sure duckman and andelena have more info on this.

[MjD]

As far as I know both are fine. Which one is it? The orange and black or the cream and carmine?

MjD

[rdrdrdrd]

the second one, whenever the mouse touched it it crashed the scenario editor,(it might have been the 414) so i deleted it and no more broblems

[gmonkeyboy]

my computer does that every once and a while

and when it does i've haven't saved in 20 min

mine only does it when i get to many vehicals in one area(around 20)

[LaSeandre]

It wasn't the 314, I hadn't selected that. I had selected: BR Green Gold Stripe 110 (? may have been 114), RR 150, Arriva 153, First 156, SWT 158, NSE 159, Ex-MM 170 (2 and 3 cars), Arriva 175 (2 cars), First 175 (3 cars), Virgin 220 (sep. cars), Virgin 221, First 222, C&C 303, Blue-Grey 310, Silverlink 313. Then it crashed.

[Plastikman]

wait, back up. it did not crash until you hit save the scenario?

[Doorslammer]

Hmmm, I think I have a similar problem to LeSeandre. Only way to avoid it was to not select anything from 300 to 319 (as I couldn't remember the exact loco causing it). This happens when selecting the trains to be present in the scenario (in the menu).

[Plastikman]

If I understood what You said.....


The problem is not the BR set itself. the problem is what is missing.

~What is missing you say?~

Yup, what is missing....

Known bug.

When you go to save a scenario in Lomo, for some stupid ass reason it reads into every other scenario in the scenarios folder and creates a database. If any of those scenarios need certain items in the scenario that is not in your objdata folder, ~Access violation!~. It thinks it has some sort of corrupt database. I am not 100% sure what it is looking for but trigger items tend to be industries, commodities, and possibly buildings, tracks and bridges.

The fix is to remove all scenarios from the scenario folder that is not game default. then your BR set will work fine.

If you accidentally remove a default scenario it also gets mad. I have learned this bug the hard way and I get it constantly as i am always erasing bits of my objdata folder.

Sometimes, once you get this crash, Lomo will not restart, even if you uninstall and reinstall. you have to do the above fix.

[LaSeandre]

Right, I'll give that a go when I get on my PC (on PS3 atm).

[Supermint]

I have had that problem occasionally but its very rare. I have A LOT of mods i my folder. I must have close to 1500 items. I konw the scroll bar is so tiny I have to use the wheel on my mouse. But 99.9% of the time they are all stable. I know an old acela train keeps causing it to crash so I just dont use it.

[LaSeandre]

It worked! Thanks Plastik. Also, I found this out when trying it: you can hold the RMB down and drag up and down and it'll move the scroll box.