Forum Replies Created
January 14, 2016 at 10:45 pm in reply to: [Bug Fixed in 22.214.171.124] Recruited lords not fighting #848
I have sent you my savegame by email where I’ve found a couple of bugs. First of all, it does not seem all that important but if Luxor picks up a Wolfslayer Sword, he drops the Moon Ring! I think he’s not supposed to do that, is he? The funny thing is that, even though the text says the Moon Ring is dropped, he does not lose his powers of Vision and Command. You can see where Luxor dropped his Moon Ring near where he is located right now.
Second, and most important, comes the fact that some battles are bugged. Check for instance my Lord Blood and my Lord Shimeril. They are both in keeps surrounded by hostile forces, but they don’t fight! You can press Night and you will see some battles (Morkin’s, for instance) but Shimeril and Blood keep in good friendship and share mead with the Doomsguard!
Hope it helps! Good job, though! It’s exciting playing and adventuring again. I would be looking forward for new maps or campaigns ?
January 14, 2016 at 10:46 pm in reply to: [Bug Fixed in 126.96.36.199] Recruited lords not fighting #850
Short update: I managed to get to the bottom of your reported issues above, which are in fact directly related! The dropping of the moonring was key to the fact that recruited lords were then not being seen in the battle locations, therefore they did not fight in the battle algorithm! This has now been fixed in 188.8.131.52 which is in preparation…
January 14, 2016 at 10:46 pm in reply to: [Bug Fixed in 184.108.40.206] Recruited lords not fighting #849
Let me see if I can recreate your reported issues which is >50% towards solving them.
In 220.127.116.11 I have added the ability to continue an existing campaign from the main menu screen. It will recognise if the entered campaign name exists already and give the option to continue rather than start a new campaign…
This is only a temporary update… finally you will be able to select from a list of the saved campaigns stored on disk… something for a future release.
After checking in the code it appears to be deliberate (if the recruiter is in battle, then they are not able to approach any other character in the same location – presumably they are preoccupied with their own imminent threat!). The logic was inherited here and it would be interesting to know whether other remakes still have the same logic… I’ll leave this open to other feedback for the moment…
January 14, 2016 at 9:41 pm in reply to: [Bug Fixed in 18.104.22.168] Recruited lords not fighting #836
I will try to recreate what you have experienced there – something doesn’t seem quite right with the battle algorithm from what you are describing.
Mmmm, ok I will do some more testing on this at the weekend and see if I can reproduce it.
In the lom\scenarios\default\saves directory, for the campaign you are running there is a .mdb database file which actually contains the results of all the indiviudal battle rounds that occur each night.
As a self confessed nerd, you might like that 🙂
It might also prove useful to try and locate what is happening in a bit more detail.
Many thanks for reporting it.
Thanks Kevin, my initial thoughts:
(1) I have no clue whatsoever about this issue. I even had to look up what is PlayTV! Let’s see if others report similar issues ?!?
(2) This was a quick improvement on the initial situation but as noted in the release notes, will be further improved with more time. I will add a page which shows existing campaigns in graphical format from which you will be able to choose one. But that needs more than a quick fix!
(3) Patience dear Kevin! Patience! I’m focussing on the gameplay issues with 1st priority rather than the nuisance from pressing Ctrl+X instead of an icon.
(4) Interesting one. I never experienced that. I think we need to gather some other experience and see if it’s a common issue…
The above changes are now incorporated into the patch release 22.214.171.124
I tried to elevate some of the more significant locations eg blood, ushgarak, xajorkith… just to try and break the flat terrain and make it a little more realistic… glad you like it.
There is only one pair of files per campaign now.
Yes if the reported bug is repeatable then to send me the campaign files just prior to the night where it happens would be very helpful.
Next best would be from the night after it happened.
Depends how repeatable it is for you… I can’t seem to make it happen !
Thanks for your feedback
Upon opening your save game, I was presented with your armies of the free having just taken Ushgarak, what a sight ! I never saw that many free armies in one location… 🙂
However to try and find your reported bug, I need a save game from the night before your reported increase in army size if possible ?
Ditto, struggling to reproduce it…
Please send through a save game if you can.
Glad you like the audio 🙂
Hi, I’ve tried a few times to reproduce this behaviour, but with no success…
If you are able to reproduce it, perhaps you could send me the save game position the night prior to it occuring, then I can reproduce it here.
To send the save game, in the \lom\scenarios\default\saves directory you will find 2 files with the campaign name (1 .mdb and 1 .mes). If you can email those to me at firstname.lastname@example.org, then I will be able to continue from where you last saved…
I have noticed that it has an annoying habbit of reverting to the start screen and running through thr setup routine if you switch to full screen via the windows full screen icon.
Yes going between fullscreen and windowed mode/changing to another monitor/starting or stopping certain other applications whilst running ==> all these actions trigger a reset of the Direct3D device and I currently handle that by reloading all resources. Suggest to avoid doing that for the moment if it’s annoying!
4) The buttons on mine disappear when I’m playing, but moving cursor over them brings them back, space sends me to second set, but none flick back and fore.
The icons at the bottom of the screen are designed to auto-hide when the mouse moves out of close vertical proximity on the main view screens! On other screens they are visible all the time due to the need for action.
Main reason: I wanted the option to take screen shots with minimal overlay objects