Option Bot Automates Binary Options - video dailymotion

Differences between LISP 1.5 and Common Lisp, Part 2a

Here is the first part of the second part (I ran out of characters again...) of a series of posts documenting the many differences between LISP 1.5 and Common Lisp. The preceding post can be found here.
In this part we're going to look at LISP 1.5's library of functions.
Of the 146 symbols described in The LISP 1.5 Programmer's Manual, sixty-two have the same names as standard symbols in Common Lisp. These symbols are enumerated here.
The symbols t and nil have been discussed already. The remaining symbols are operators. We can divide them into groups based on how semantics (and syntax) differ between LISP 1.5 and Common Lisp:
  1. Operators that have the same name but have quite different meanings
  2. Operators that have been extended in Common Lisp (e.g. to accept a variable number of arguments), but that otherwise have similar enough meanings
  3. Operators that have remained effectively the same
The third group is the smallest. Some functions differ only in that they have a larger domain in Common Lisp than in LISP 1.5; for example, the length function works on sequences instead of lists only. Such functions are pointed out below. All the items in this list should, given the same input, behave identically in Common Lisp and LISP 1.5. They all also have the same arity.
These are somewhat exceptional items on this list. In LISP 1.5, car and cdr could be used on any object; for atoms, the result was undefined, but there was a result. In Common Lisp, applying car and cdr to anything that is not a cons is an error. Common Lisp does specify that taking the car or cdr of nil results in nil, which was not a feature of LISP 1.5 (it comes from Interlisp).
Common Lisp's equal technically compares more things than the LISP 1.5 function, but of course Common Lisp has many more kinds of things to compare. For lists, symbols, and numbers, Common Lisp's equal is effectively the same as LISP 1.5's equal.
In Common Lisp, expt can return a complex number. LISP 1.5 does not support complex numbers (as a first class type).
As mentioned above, Common Lisp extends length to work on sequences. LISP 1.5's length works only on lists.
It's kind of a technicality that this one makes the list. In terms of functionality, you probably won't have to modify uses of return---in the situations in which it was used in LISP 1.5, it worked the same as it would in Common Lisp. But Common Lisp's definition of return is really hiding a huge difference between the two languages discussed under prog below.
As with length, this function operates on sequences and not only lists.
In Common Lisp, this function is deprecated.
LISP 1.5 defined setq in terms of set, whereas Common Lisp makes setq the primitive operator.
Of the remaining thirty-three, seven are operators that behave differently from the operators of the same name in Common Lisp:
  • apply, eval
The connection between apply and eval has been discussed already. Besides setq and prog or special or common, function parameters were the only way to bind variables in LISP 1.5 (the idea of a value cell was introduced by Maclisp); the manual describes apply as "The part of the interpreter that binds variables" (p. 17).
  • compile
In Common Lisp the compile function takes one or two arguments and returns three values. In LISP 1.5 compile takes only a single argument, a list of function names to compile, and returns that argument. The LISP 1.5 compiler would automatically print a listing of the generated assembly code, in the format understood by the Lisp Assembly Program or LAP. Another difference is that compile in LISP 1.5 would immediately install the compiled definitions in memory (and store a pointer to the routine under the subr or fsubr indicators of the compiled functions).
  • count, uncount
These have nothing to do withss Common Lisp's count. Instead of counting the number of items in a collection satisfying a certain property, count is an interface to the "cons counter". Here's what the manual says about it (p. 34):
The cons counter is a useful device for breaking out of program loops. It automatically causes a trap when a certain number of conses have been performed.
The counter is turned on by executing count[n], where n is an integer. If n conses are performed before the counter is turned off, a trap will occur and an error diagnostic will be given. The counter is turned off by uncount[NIL]. The counter is turned on and reset each time count[n] is executed. The counter can be turned on so as to continue counting from the state it was in when last turned off by executing count[NIL].
This counting mechanism has no real counterpart in Common Lisp.
  • error
In Common Lisp, error is part of the condition system, and accepts a variable number of arguments. In LISP 1.5, it has a single, optional argument, and of course LISP 1.5 had no condition system. It had errorset, which we'll discuss later. In LISP 1.5, executing error would cause an error diagnostic and print its argument if given. While this is fairly similar to Common Lisp's error, I'm putting it in this section since the error handling capabilities of LISP 1.5 are very limited compared to those of Common Lisp (consider that this was one of the only ways to signal an error). Uses of error in LISP 1.5 won't necessarily run in Common Lisp, since LISP 1.5's error accepted any object as an argument, while Common Lisp's error needs designators for a simple-error condition. An easy conversion is to change (error x) into (error "~A" x).
  • map
This function is quite different from Common Lisp's map. The incompatibility is mentioned in Common Lisp: The Language:
In MacLisp, Lisp Machine Lisp, Interlisp, and indeed even Lisp 1.5, the function map has always meant a non-value-returning version. However, standard computer science literature, including in particular the recent wave of papers on "functional programming," have come to use map to mean what in the past Lisp implementations have called mapcar. To simplify things henceforth, Common Lisp follows current usage, and what was formerly called map is named mapl in Common Lisp.
But even mapl isn't the same as map in LISP 1.5, since mapl returns the list it was given and LISP 1.5's map returns nil. Actually there is another, even larger incompatibility that isn't mentioned: The order of the arguments is different. The first argument of LISP 1.5's map was the list to be mapped and the second argument was the function to map over it. (The order was changed in Maclisp, likely because of the extension of the mapping functions to multiple lists.) You can't just change all uses of map to mapl because of this difference. You could define a function like map-1.5,such as
(defun map-1.5 (list function) (mapl function list) nil) 
and replace map with map-1.5 (or just shadow the name map).
  • function
This operator has been discussed earlier in this post.
Common Lisp doesn't need anything like LISP 1.5's function. However, mostly by coincidence, it will tolerate it in many cases; in particular, it works with lambda expressions and with references to global function definitions.
  • search
This function isn't really anything like Common Lisp's search. Here is how it is defined in the manual (p. 63, converted from m-expressions into Common Lisp syntax):
(defun search (x p f u) (cond ((null x) (funcall u x)) ((p x) (funcall f x)) (t (search (cdr x) p f u)))) 
Somewhat confusingly, the manual says that it searches "for an element that has the property p"; one might expect the second branch to test (get x p).
The function is kind of reminiscent of the testr function, used to exemplify LISP 1.5's indefinite scoping in the previous part.
  • special, unspecial
LISP 1.5's special variables are pretty similar to Common Lisp's special variables—but only because all of LISP 1.5's variables are pretty similar to Common Lisp's special variables. The difference between regular LISP 1.5 variables and special variables is that symbols declared special (using this special special special operator) have a value on their property list under the indicator special, which is used by the compiler when no binding exists in the current environment. The interpreter knew nothing of special variables; thus they could be used only in compiled functions. Well, they could be used in any function, but the interpreter wouldn't find the special value. (It appears that this is where the tradition of Lisp dialects having different semantics when compiled versus when interpreted began; eventually Common Lisp would put an end to the confusion.)
You can generally change special into defvar and get away fine. However there isn't a counterpart to unspecial. See also common.
Now come the operators that are essentially the same in LISP 1.5 and in Common Lisp, but have some minor differences.
  • append
The LISP 1.5 function takes only two arguments, while Common Lisp allows any number.
  • cond
In Common Lisp, when no test in a cond form is true, the result of the whole form is nil. In LISP 1.5, an error was signaled, unless the cond was contained within a prog, in which case it would quietly do nothing. Note that the cond must be at the "top level" inside the prog; cond forms at any deeper level will error if no condition holds.
  • gensym
The LISP 1.5 gensym function takes no arguments, while the Common Lisp function does.
  • get
Common Lisp's get takes three arguments, the last of which is a value to return if the symbol does not have the indicator on its property list; in LISP 1.5 get has no such third argument.
  • go
In LISP 1.5 go was allowed in only two contexts: (1) at the top level of a prog; (2) within a cond form at the top level of a prog. Later dialects would loosen this restriction, leading to much more complicated control structures. While progs in LISP 1.5 were somewhat limited, it is at least fairly easy to tell what's going on (e.g. loop conditions). Note that return does not appear to be limited in this way.
  • intern
In Common Lisp, intern can take a second argument specifying in what package the symbol is to be interned, but LISP 1.5 does not have packages. Additionally, the required argument to intern is a string in Common Lisp; LISP 1.5 doesn't really have strings, and so intern instead wants a pointer to a list of full words (of packed BCD characters; the print names of symbols were stored in this way).
  • list
In Common Lisp, list can take any number of arguments, including zero, but in LISP 1.5 it seems that it must be given at least one argument.
  • load
In LISP 1.5, load can't be given a filespec as an argument, for many reason. Actually, it can't be given anything as an argument; its purpose is simply to hand control over to the loader. The loader "expects octal correction cards, 704 row binary cards, and a transfer card." If you have the source code that would be compiled into the material to be loaded, then you can just put it in another file and use Common Lisp's load to load it in. But if you don't have the source code, then you're out of luck.
  • mapcon, maplist
The differences between Common Lisp and LISP 1.5 regarding these functions are similar to those for map given above. Both of these functions returned nil in LISP 1.5, and they took the list to be mapped as their first argument and the function to map as their second argument. A major incompatibility to note is that maplist in LISP 1.5 did what mapcar in Common Lisp does; Common Lisp's maplist is different.
  • member
In LISP 1.5, member takes none of the fancy keyword arguments that Common Lisp's member does, and returns only a truth value, not the tail of the list.
  • nconc
In LISP 1.5, this function took only two arguments; in Common Lisp, it takes any number.
  • prin1, print, terpri
In Common Lisp, these functions take an optional argument specifying an output stream to which they will send their output, but in LISP 1.5 prin1 and print take just one argument, and terpri takes no arguments.
  • prog
In LISP 1.5, the list of program variables was just that: a list of variables. No initial values could be provided as they can in Common Lisp; all the program variables started out bound to nil. Note that the program variables are just like any other variables in LISP 1.5 and have indefinite scope.
In the late '70s and early '80s, the maintainers of Maclisp and Lisp Machine Lisp wanted to add "naming" abilities to prog. You could say something like
(prog outer () ... (prog () (return ... outer))) 
and the return would jump not just out of the inner prog, but also out of the outer one. However, they ran into a problem with integrating a named prog with parts of the language that were based on prog. For example, they could add a special case to dotimes to handle an atomic first argument, since regular dotimes forms had a list as their first argument. But Maclisp's do had two forms: the older (introduced in 1969) form
(do atom initial step-form end-test body...) 
and the newer form, which was identical to Common Lisp's do. The older form was equivalent to
(do ((atom intitial step-form)) (end-test) body...) 
Since the older form was still supported, they couldn't add a special case for an atomic first argument because that was the normal case of the older kind of do. They ended up not adding named prog, owing to these kinds of difficulties.
However, during the discussion of how to make named prog work, Kent Pitman sent a message that contained the following text:
I now present my feelings on this issue of how DO/PROG could be done in order this haggling, part of which I think comes out of the fact that these return tags are tied up in PROG-ness and so on ... Suppose you had the following primitives in Lisp: (PROG-BODY ...) which evaluated all non-atomic stuff. Atoms were GO-tags. Returns () if you fall off the end. RETURN does not work from this form. (PROG-RETURN-POINT form name) name is not evaluated. Form is evaluated and if a RETURN-FROM specifying name (or just a RETURN) were executed, control would pass to here. Returns the value of form if form returns normally or the value returned from it if a RETURN or RETURN-FROM is executed. [Note: this is not a [*]CATCH because it is lexical in nature and optimized out by the compiler. Also, a distinction between NAMED-PROG-RETURN-POINT and UNNAMED-PROG-RETURN-POINT might be desirable – extrapolate for yourself how this would change things – I'll just present the basic idea here.] (ITERATE bindings test form1 form2 ...) like DO is now but doesn't allow return or goto. All forms are evaluated. GO does not work to get to any form in the iteration body. So then we could just say that the definitions for PROG and DO might be (ignore for now old-DO's – they could, of course, be worked in if people really wanted them but they have nothing to do with this argument) ... (PROG [  ]  . ) => (PROG-RETURN-POINT (LET  (PROG-BODY . )) [  ]) (DO [  ]   . ) => (PROG-RETURN-POINT (ITERATE   (PROG-BODY . )) [  ]) Other interesting combinations could be formed by those interested in them. If these lower-level primitives were made available to the user, he needn't feel tied to one of PROG/DO – he can assemble an operator with the functionality he really wants. 
Two years later, Pitman would join the team developing the Common Lisp language. For a little while, incorporating named prog was discussed, which eventually led to the splitting of prog in quite a similar way to Pitman's proposal. Now prog is a macro, simply combining the three primitive operators let, block, and tagbody. The concept of the tagbody primitive in its current form appears to have been introduced in this message, which is a writeup by David Moon of an idea due to Alan Bawden. In the message he says
The name could be GO-BODY, meaning a body with GOs and tags in it, or PROG-BODY, meaning just the inside part of a PROG, or WITH-GO, meaning something inside of which GO may be used. I don't care; suggestions anyone?
Guy Steele, in his proposed evaluator for Common Lisp, called the primitive tagbody, which stuck. It is a little bit more logical than go-body, since go is just an operator and allowed anywhere in Common Lisp; the only special thing about tagbody is that atoms in its body are treated as tags.
  • prog2
In LISP 1.5, prog2 was really just a function that took two arguments and returned the result of the evaluation of the second one. The purpose of it was to avoid having to write (prog () ...) everywhere when all you want to do is call two functions. In later dialects, progn would be introduced and the "implicit progn" feature would remove the need for prog2 used in this way. But prog2 stuck around and was generalized to a special operator that evaluated any number of forms, while holding on to the result of the second one. Programmers developed the (prog2 nil ...) idiom to save the result of the first of several forms; later prog1 was introduced, making the idiom obsolete. Nowadays, prog1 and prog2 are used typically for rather special purposes.
Regardless, in LISP 1.5 prog2 was machine-coded subroutine that was equivalent to the following function definition in Common Lisp:
(defun prog2 (one two) two) 
  • read
The read function in LISP 1.5 did not take any arguments; Common Lisp's read takes four. In LISP 1.5, read read either from "SYSPIT" or from the punched carded reader. It seems that SYSPIT stood for "SYStem Paper (maybe Punched) Input Tape", and that it designated a punched tape reader; alternatively, it might designate a magnetic tape reader, but the manual makes reference to punched cards. But more on input and output later.
  • remprop
The only difference between LISP 1.5's remprop and Common Lisp's remprop is that the value of LISP 1.5's remprop is always nil.
  • setq
In Common Lisp, setq takes an arbitrary even number of arguments, representing pairs of symbols and values to assign to the variables named by the symbols. In LISP 1.5, setq takes only two arguments.
  • sublis
LISP 1.5's sublis and subst do not take the keyword arguments that Common Lisp's sublis and subst take.
  • trace, untrace
In Common Lisp, trace and untrace are operators that take any number of arguments and trace the functions named by them. In LISP 1.5, both trace and untrace take a single argument, which is a list of the functions to trace.

Functions not in Common Lisp

We turn now to the symbols described in the LISP 1.5 Programmer's Manual that don't appear in Common Lisp. Let's get the easiest case out of the way first: Here are all the operators in LISP 1.5 that have a corresponding operator in Common Lisp, with notes about differences in functionality where appropriate.
  • add1, sub1
These functions are the same as Common Lisp's 1+ and 1- in every way, down to the type genericism.
  • conc
This is just Common Lisp's append, or LISP 1.5's append extended to more than two arguments.
  • copy
Common Lisp's copy-list function does the same thing.
  • difference
This corresponds to -, although difference takes only two arguments.
  • divide
This function takes two arguments and is basically a consing version of Common Lisp's floor:
(divide x y) = (values-list (floor x y)) 
  • digit
This function takes a single argument, and is like Common Lisp's digit-char-p except that the radix isn't variable, and it returns a true or false value only (and not the weight of the digit).
  • efface
This function deletes the first appearance of an item from a list. A call like (efface item list) is equivalent to the Common Lisp code (delete item list :count 1).
  • greaterp, lessp
These correspond to Common Lisp's > and <, although greaterp and lessp take only two arguments.
As a historical note, the names greaterp and lessp survived in Maclisp and Lisp Machine Lisp. Both of those languages had also > and <, which were used for the two-argument case; Common Lisp favored genericism and went with > and < only. However, a vestige of the old predicates still remains, in the lexicographic ordering functions: char-lessp, char-greaterp, string-lessp, string-greaterp.
  • minus
This function takes a single argument and returns its negation; it is equivalent to the one-argument case of Common Lisp's -.
  • leftshift
This function is the same as ash in Common Lisp; it takes two arguments, m and n, and returns m×2n. Thus if the second argument is negative, the shift is to the right instead of to the left.
  • liter
This function is identical in essence to Common Lisp's alpha-char-p, though more precisely it's closer to upper-case-p; LISP 1.5 was used on computers that made no provision for lowercase characters.
  • pair
This is equivalent to the normal, two-argument case of Common Lisp's pairlis.
  • plus
This function takes any number of arguments and returns their sum; its Common Lisp counterpart is +.
  • quotient
This function is equivalent to Common Lisp's /, except that quotient takes only two arguments.
  • recip
This function is equivalent to the one-argument case of Common Lisp's /.
  • remainder
This function is equivalent to Common Lisp's rem.
  • times
This function takes any number of arguments and returns their product; its Common Lisp counterpart is *.
Part 2b will be posted in a few hours probably.
submitted by kushcomabemybedtime to lisp [link] [comments]

Heritage (4)

First Chapter
Previous Chapter
The view of Sanctuary was made even more impressive as An’Ra and his team waited in the V-Lift. Through the window, they can see the ornate streets curving through resplendent pools underneath, dotted by the occasional fountain.
“I hate this.” Vora groaned, dressed in a soldier’s standard battle uniform. “Why are we here, Commander?”
“We were investigating genocide and possible use of bioweapons,” Sonak explained, “Even without the first part, Strain Y is going to scare a lot of people. I think it’s reasonable for the Council to take a personal interest in this. Besides, I think the real issue here is the fact you might actually have to speak to the Council.”
“But...ugh, fine. Yes, I wasn’t mentally prepared for it when An’Ra came along and went, Party’s over, ass to the Council, now.”
“Hey now.” An’Ra feigned offense, “I didn’t say it that way, did I?”
“Kind of close, Commander.” Sonak chuckled.
“But still, I think that this isn’t about keeping the galaxy safe.” Vora sighed. “I think the Council’s keeping an eye open for any opportunity to to convince the galaxy they’re still in charge.”
“Or maybe they genuinely want to make sure that we’re not at risk of dying a horrible death by watching our own bodies melt.” Sonak shrugged. “Strain Y doesn’t care if you’re an officer or infantry.”
“That assumes the Council cares about what’s going on outside of these walls.” Vora glanced over, wariness in her look.
“Either way, we’re going to get our answer. Eyes open.” An’Ra said as the V-Lift doors parted ways, revealing the same ornate architecture within. Trees and grasses stole the eye as they walked through the hallways, various government officials from the myriad races conversing and conducting whatever business they were doing. After walking up some steps, they arrived at the large double-doors that lead to the Council Chambers. Standing on each side were the guards constantly on watch for any potential attack. Both of them Anaran, as expected. On approach, the guards opened up the doors to allow An’Ra and his team in.
When they entered, the room was probably more magnificent than they expected. A grand, curved window dominated the view. An unintrusive look into the beautiful splendor of Sanctuary. Directly in front of An’Ra and his team was a pathway that led to a semi-circular desk, standing in front of the raised platform that the Council sat, who had just now noticed the arrivals and are settling themselves in.
And it was there An’Ra got a good look at the Council. Four of them, half Esti, half Huak. An’Ra secretly never liked the Esti, the way he could see menacing fangs when their flat mouths opened, or those flaps of scale that expands outward into a hood. It just unnerved him, a reason he could never really find out. As soon as he sensed that they were ready, he walked up to the desk, wearing his officer’s dress uniform, comprised of a fine, smooth fabric shirt, adorned with a fluffy sash that went from his right shoulder down to his left side, shoulder pads accented with shining studs and finished with awards placed on his top-left chest, awards hard earned back in the Great War.
“Commander An’Ra.” The Huak councilor on the far right side, Neual, began, thick fingers interlaced together as he rested his hands on the desk. “Thank you for agreeing to this unusual request, we are very appreciative.”
“It’s no trouble, Councilor.” An’Ra gave a slight bow. “How can I help?”
“We’ll start at the beginning.” The first Esti councilor, Zhur, stated, holding up a secure datapad to ensure the information is easily accessible. “Strain Y. Your report says that while there is confirmation it was used, it was not used in significant quantities. Can you elaborate on that for us?”
“Previous uses of Strain Y all had one thing in common,” An’Ra began, “The amount deployed saturated the atmosphere of the planets they were used on. This is because, despite its lethality, is not actually that infectious. In order to guarantee the total elimination of a planet’s population, you will need to deploy it in such large numbers that everyone will be infected within minutes of deployment. In this case, for Planet 3, there simply wasn’t enough to reach that threshold.”
“At which you go on to state that thermal weapons were used in a state of panic,” Yhiz, the second Esti councilor, added, “Can you explain your reasoning for us?”
“As established before, Strain Y was used on the planet. My working theory is that, when they discovered that they grossly underestimated the amount needed, they panicked and used thermal weapons to both try and burn out the supplies used and finish the genocide they started.”
“But if thermal weapons were indeed used, how did you confirm Strain Y was deployed?” Zhur spoke up.
“We found pieces of Strain Y’s genetic material on the planet’s surface.” An’Ra glanced over to Zhur’s direction. “And as I arrived back in the system, I received a quantum packet from the expedition, stating that they have confirmed that Strain Y was indeed used. Adding that with the obvious use of thermal weaponry, I concluded that the attackers didn’t use enough of the weapon to guarantee extinction.”
Zhur leaned back in her seat, scarlet eyes fixated on the desk. An’Ra couldn’t tell if she was trying to find a counter argument or just processing the information.
“Have you found any evidence that can tell us if there’s more of the strain out in the galaxy?” Neual asked after giving a sigh through his wide nostrils.
“I’m afraid not, sir. All I can definitively say is that this planet fell victim to a biological Cruel Weapon.”
“I’m more concerned about the native life.” Ghala, the final and second Huak councilor, stated after being silent. “Are you absolutely certain that none of the planet’s indigenous life survived?”
“The scientific team said that there’s a very low chance of that.” An’Ra’s ears flattened. “And after seeing the surface myself, I must agree. I don’t think we should wait for a miracle.”
“Ah...I see.” Ghala leaned back in his chair, obviously disheartened. “Even if the planet is now incapable of supporting life, we still wish to move forward with a more symbolic gesture and statement by declaring Planet 3 of System AQ 115-4A illegal for colonization.”
“But let’s move onto what I believe is the most pressing issue: the identity of the attackers.” Neual leaned forward. “Based on your report, you and the team have found nothing that neither confirms nor clears any potential suspect?”
“That’s correct, Councilor.” An’Ra nodded. “We’ve found nothing, within the system and on the planet itself, that tells us anything about who did it.”
“Are there any surviving infrastructure on the planet?” Ghala asked, straightening his posture. “Even if there isn’t much, maybe the natives’ equipment has something we can use?”
“As established before, the planet was devastated terribly. There are indeed ruins of their civilization, but whether or not we can salvage anything from them is a different story.” An’Ra answered with a sigh.
“So in that case, the Qu’Rathi are still the likely aggressors then.” Zhur stated.
“I’m not convinced.” An’Ra shook his head. “Everything we have so far is just circumstantial, nothing solid.”
“Yes, that proves they did it. But looking at it from a different perspective, nothing that proves they didn’t do it either.” Zhur countered, her eyes squinting some.
“I don’t think it’s a good idea to press forward with what I think you’re planning, Councilor.” An’Ra leaned forward on the table, ears flattening back. “If you do, and we uncover evidence that clearly proves their innocence, you will be pushing an innocent race away.”
“But if we uncover evidence that proves their guilt, then the trial will be much more expedient.” Yhiz joined in, his eyes also squinting slightly.
“With respect Council, I still think that’s the worst decision you can make.” An’Ra’s teeth began to bare as he spoke. “We can’t make any decision until we acquire more evidence.”
“Nothing we have proves that Strain Y is permanently removed as a future threat.” Zhur started, “Nothing we have proves that the Federation did not do anything. Right now, we have the threat of a Class 4 Cruel Weapon looming over everyone’s heads. People will start becoming scared, start wondering if their shadows will melt them at any time.”
“I know that Councilors!” An’Ra raised his voice. “Give me time! I’m not saying this is over yet, just let me keep looking!”
“We aren’t stopping your investigation, Commander.” Neual said, holding his hand up slightly. “We’re just informing you that you may not have the time you thought you had.”
“What does that mean?” An’Ra’s ears stuck out at an angle, mixed between stiffening and anger.
The councilors looked at each other for a few moments before Zhur stood up and took in a deep breath. “Commander, based on both the collected evidence so far, and lack of any other evidence, the Council has decided to proceed with charging the Qu’Rathi Federation on counts of Genocide, possession of a Cruel Weapon, and deployment of Cruel Weapons with intent for malicious harm. Out of respect for your efforts, Commander, we will give you eight months to continue your investigation. Beyond that, we will close your investigation to allow the courts time to process and review what has been collected.”
“Are you insane?!” An’Ra shouted. “Do you even realize what would happen if you’re wrong?!”
“We do, Commander.” Zhur nodded. “But the risk is just too high. The safety of the galaxy and justice for the inhabitants of System AQ 115-4A must be our top priority. This debrief is over.”
An’Ra stood in complete and stunned silence, watching the Council casually get up from their seats and dispersing to their own private offices. It wasn’t until that they have fully left the chambers that An’Ra finally found the will to move and regroup with Sonak and Vora, both of whom are also equally stunned.
“Those ekas!” Vora exclaimed. “It’s bad enough to be quick at accusing someone, but how dare they claim this is for those humans!”
“And here I thought all those things the news were saying was just to get people to watch them.” Sonak muttered softly. “Commander, obviously this is bad.”
“I know, Sonak.” An’Ra crossed his arms, ears now pointing straight back and teeth fully bared. “We can’t let them do this.”
“But what can we do?” Sonak exclaimed. “What options do we have?”
“Alliance Enforcement!” Vora declared. “Commander, what if you filed a complaint to the Lord-Enforcer? Tell him what’s going on?”
“That’s a good idea actually.” Sonak nodded. “If we convince the Lord-Enforcer that the Council is being too hasty with our investigation, which shouldn’t be hard, he just might deny the Council’s request for prosecution!”
“I can’t imagine the Lord-Enforcer approving this even without our complaint.” An’Ra replied. “Still, never hurts to be prepared. Come on, let’s get to it.”

Jur’El leaned back in the puffy seat he was assigned to. The restaurant he entered had a calm and relaxed atmosphere. The lighting was dimmed, which complimented the dark but cozy ambiance of the room. The walls and floor each had a dark-themed color scheme, the seats were of a different scheme but not too different to oppose the goal set by the designer. And although the building was packed with customers, their conversations did not threaten to turn anyone deaf. It was a quiet and relaxed experience, something he needed desperately.
Even now, as hard as he tried to focus on how delicious his food was, how balanced the flavor and texture of it was, he was still forced to relive what happened on Planet 3. He could hear the sudden screams of his colony group. The scientists who were first awoken that wanted to find out why their Life world was so different to the data they were given. To the families and menial workers who were just talking amongst themselves and organizing the supplies when those machines stormed the ship. And what still terrifies him, still sends his heart racing, was when that one machine entered the control room, blood drenching its chassis. Bits and pieces of Qu’Rathi innards on its cold mechanical manipulators. How it just stared at him, lifelessly, with a rifle aiming right at his chest. And those drills. Those ghenning drills.
He was forced out of his torment by the rough poking of his shoulder. When he looked, it was another Qu’Rathi. “Captain Jur’El, right?”
“Uh..yes, who are you?” He nodded in confusion.
“Jhen.” She introduced herself, quickly taking a seat opposite from him. “I need to talk to you.”
“About what?”
“The expedition to that system deep in the Dead Zone.” She glared at him, mandibles tense. “The same system who’s Life world had a native population, the very same world being investigated as a genocide site, where your expedition went to settle.”
“Jhen, please, we had no idea what was going on.” Jur’El leaned back, hands raised in a defensive posture. “All we were told was that this was the most pristine and beautiful Life world ever discovered in a system rich with stellar bodies.”
“I don’t care about that. What I care is how you seem to be the only one who came back.” Jhen started raising herself from her seat. “I’m pretty sure that anyone who attempts to colonize a freshly cleansed world is forcibly removed from that planet and returned to their respective people. So where is everyone?”
Jur’El’s eyes went wide. He knew exactly where this was going. “I...I can’t tell you.”
“Don’t you dare.” Jhen snarled, now leaning over the table. “I’ve heard enough of that from the company, I’m not here to be force-fed more of it!”
“Just...trust me,” Jur’El spoke softly, shakily leaving his seat, “You don’t want to know.”
“Don’t you ghenning walk away from me!” Jhen shouted, grabbing Jur’El’s shoulder firmly, the other patrons now locking eyes to the two. “Two of my sons were on that mission! What happened to them?!”
Jur’El clutched his head with a hand firmly, feeling tears exploding out of his eyes. His mind rushing back to those scenes. The sounds, the smell, the fear. Everything crashed into him all at once. And they’re not just memories now. They’re all coming back to him as if he was transported in time and placed back to the exact moment it started. Back to the moment where he was screaming for his wife and son to hide, to find a corner of the ship that was hard to see and to stay there until the shooting stopped. How he felt his heart give out when he heard them beg for their life when they were found, cut short by the merciless cracks of their alien weapons. How every possible feeling melted away when the clanking of the machine’s walking approached him, when he realized there was no nowhere in the control room to hide, not with how thorough those things were being. The frantic, mindless begging he got into when he saw the blood covered machine hold that weapon to him.
“You’re safe!” A voice rang out. It wasn’t much, but it was enough for him to come back. That scene melting away back into the restaurant. All those smells and sights to be gone. When he was certain that it was over, he looked around. There was Jhen, face beaten and currently being restrained by a blue-furred Anaran. And in front of him was another, gray-furred one. “You hear me? You’re safe now!”
“I...wh-what happened?”
“We saw what was going on. The Qu’Rathi over there? She was just screaming down your throat, all while you were just on the floor. Ken’A there nearly caved her face in by the time we got some distance between you two.”
“Th...thank you.” Jur’El muttered, shakily getting himself back on his feet with the help of the gray Anaran. Jur’El was just about to walk away when the Anaran firmly, but not threateningly, gripped his shoulder.
“I know the signs, friend.” He began softly. “Your soul is badly wounded and is bleeding heavily. Just like a doctor if you’re shot or cut, you need to find someone to talk to, get your soul back together.”
“As long as I don’t run into another person like her, I’ll be fine.” Jur’El countered, trying to walk away still.
“No, you won’t.” The Anaran still held his grip. “I need you to trust me. With how bad your soul is right now, doing anything other than talking to someone will just make it worse. And when your soul dies, well...believe me, it’s not a good experience, for anybody.”
Jur’El stared into the gray Anaran’s orange eyes for a moment before he let out a sigh. “You’re not going to give up, are you?”
“I’ve seen what happens too many times. Good Battle-Brothers, completely different people. Either they’re just shadows of themselves, or doomed to forever relive their horrors. If I have the chance to prevent it happening again, I’m giving it my all.”
Jur’El looked aside for a few moments, internally fighting himself as to whether he should comply or keep resisting. He finally reached his decision when he became certain that the Anaran would most likely hunt him down as a life mission if he didn’t seek therapy. “Fine, I’ll do it. Got anyone in mind?”
“A dear friend of mine. He’ll get you back on track, promise.” The Anaran patted Jur’El’s shoulder a few times before proceeding to lead him, motioning for Ken’A to let go of Jhen and follow.

Michael, accompanied by his newly founded Praetorian Guard, continued his leisurely stroll down the surprisingly spacious corridor. The hallway itself was typical. All-metal construction with evenly spaced rows of blue-white lights.
The Praetorian Guard themselves are comprised of those Servants who display both extreme scores in combat efficiency and effectiveness in defensive situations. Armed with the absolute best in magnetic-ballistics, the most impenetrable of armor designs and the highest optimized combat-frames, even a squad of these guards can hold off a virtual army, provided they aren’t subjected to bombardment or heavy ordinance.
Just as Michael was about to enter the main command center of the station he was touring, Central contacted him on a private channel.
“Master? Your new administration is ready.” He declared proudly.
“Alright, let’s begin the introductions.” Michael replied, signaling the guardsmen that he’s about to enter a meeting. Although unneeded, the Guard promptly took up a defensive formation around him. He assumes this is mostly to keep unwelcome guests from interrupting him.
The scenery of the tranquil design of the corridor melted away into the virtual world built by neon-blue blocks, the same visual that he witnessed when he first received the interface. After a few moments, several other Servants materialized and stood attention in a semi-circle in front of him.
“My Lord.” The first Servant bowed, its voice deep, if gruff. “I’m Supreme Commander Schwarzkopf, in charge of managing our armed forces and overseeing the grand strategy of the Imperium.”
“I am Secretary Elizabeth.” The second spoke with a calming, soothing feminine voice. “I’m responsible for ensuring our economy runs perfectly. In short, I make sure every project gets the hammers and resources it needs.”
“I’m Foreign Minister Edward, at your service m’Lord.” The third, with a distinct British accent and of a composed, controlled voice. “While regretfully I’m useless at this stage, the moment we initiate contact with xeno species, I’ll handle diplomatic affairs and achieving our goals through negotiations when possible.”
“No offense, but I thought every Servant wants to see aliens dead?” Michael spoke up with slight confusion.
“Oh, of course. The very idea of ripping out the entrails of a xeno and suffocating them with it brings such joy it’s therapeutic.” Benjamin replied. Michael was unsure if he was joking or not. “I was appointed because I displayed the most effective ability at hiding such feelings.”
“Ah...good to know.” Michael nodded dryly, not exactly assured. “Back to where we were?”
“Yes, Lord. I’m Director Mansfield.” The fourth spoke with an eloquent-sounding voice. “I’m in charge of Imperial Intelligence, running operations abroad and managing counter-intelligence on the homefront. I give you my word that we will know everything about the aliens and they will know nothing about us.”
“And that leaves me, Master.” Central began. “As a result of this delegation, I now possess more processing cycles towards research and development. That means that I’ll be in charge of ensuring Imperial dominance in technology. I will also act as your adjutant, filtering out information that does not need your attention.”
“Well...shit, this sounds like an actual government I’m in charge of.” Michael gave out a nervous chuckle. “All the more reason to get down to business though. Let’s start with the first matter. Schwarzkopf, how’s our military coming along?”
“It’s growing rapidly, your majesty.” He answered with distinct pride. “Already we have several hundred frigates, fifty light cruisers and twenty heavy cruisers, with the first wave of battleships due to exit the drydocks within a few days. Additionally, we have established four different army groups with fifty divisions each.”
“I thought we’d take a lot longer.” Michael stated with no hidden amazement.
“There’s great benefit in our workforce able to operate at a hundred percent every hour of the day.” Elizabeth commented, her emotion-flags also indicating pride. “And speaking of which, our population of Servants grows geometrically. That benefits both our economy and the military. Our economy by providing more workers in skilled and unskilled labor, and the military by providing more crew members and soldiers.”
“So in short, it won’t be long before we become a virtual powerhouse.” Michael said, arms crossed.
“Especially if we continue expanding.” Elizabeth nodded. “On that note, we have already claimed several dozen more systems.”
“With Rigel and Betelgeuse selected as naval bases.” Schwarzkopf chimed in.
“So we’re expanding in all the ways, got it.” Michael nodded. “Now the second matter. Terraforming Mars.”
“At present, there are two issues that must be resolved.” Central answered. “The first problem is the planet’s lack of a magnetosphere. Without that, any and all organic life would perish under lethal bombardment of the Sun’s solar wind, in addition to any sustainable atmosphere being lost to space. The second problem is Mars’ inability to retain heat, the cause for it’s known low planetary temperature.”
“And knowing you, you already have possible answers?” Mansfield shrugged.
“Correct. The heat issue is rather trivial to solve. Mars already has an abundant amount of carbon-dioxide within the atmosphere, a well known greenhouse gas. Combined with even more of the gas locked planet side, once temperatures begin to rise, we will set off a snowball effect. However, that is all for naught if the atmosphere is allowed to escape into space by solar wind.”
“So basically the key here is the magnetosphere.” Michael added. “Build that and everything becomes simple.”
“Exactly.” Central affirmed. “Already there are two main methods. One is to build superconducting rings around the planet and drive them with direct current. With enough power, we can generate magnetic fields strong enough to form a virtual magnetosphere.”
“And what’s the second?” Elizabeth said.
“The second is to construct a station at the L1 Lagrange Point that will generate a dipole magnetic field, diverting the solar wind around the planet instead of into it. Although it was simulated using slower, binary processing, the results indicate that Mars would gain half the atmospheric pressure of Earth’s within a few years.”
“So then, the main focus is building that magnetic shield.” Michael spoke firmly. “Elizabeth? Let’s get the ball rolling. Coordinate with Central as needed.”
“At once, my Lord.” Elizabeth bowed.

Unlike the Council chambers, the office of the Lord-Enforcer was much less opulent and more pragmatic. After going through the receptionist area, An’Ra and his team were escorted into the main office itself. However, just like the chambers, a large window dominated the view on entry, granting another view of a city district on Sanctuary.
And sitting in the more rectangular desk was the Lord-Enforcer himself, Dura. Blue eyed, with a fur of dull-orange it reminds of a sunset. As soon as An’Ra and his team walked into the office, the Enforcer sat up, tail wagging.
“Commander An’Ra, in my office!” He exclaimed, arms out to his sides. “Forgive me sir, but I never thought I’d see the day!”
“A pleasure to meet you, sir.” An’Ra replied warmly, greeting the Enforcer with their fists clasped together and pulling themselves inward, shoulder to shoulder.
“Please, no need to be formal with me.” Dura chuckled. “Sit down, what brings you here?”
After taking their respective seats, An’Ra looked at Dura grimly. “I’m here to file a delay on a request for prosecution against the Federation.”
Dura’s ears angled themselves in a mixture of stiffening and lowering. “I just got the paperwork from the Council. And I can tell you that won’t be needed. I’ve already submitted my rejection.”
“With respect, sir.” Sonak spoke up. “I get the feeling that the Council might fight that.”
“Don’t worry, I’m not going to present my back to them just because they ask.” Dura gave off a grin. “I might be some paper-tosser now, but that just means the battlefield is different. Don’t worry Commander, as long as I’m here, you’ll get the chance to finish this investigation properly.”
“Thank you, Enforcer.” An’Ra smiled as he got up from his seat. “With any luck, you won’t have to fight long.”
“Oh, take your time!” Dura replied with an inflection of humor. “This is the most exciting thing I’ve had in years. Was just about to smash my head on this desk any day now actually.”
“Wait, really?” Vora asked, ears stiffened.
“It’s just a joke, Vora.” Sonak assured dryly.
“Oh...” Her ears flattened as the team exited the office.
When they arrived in the main plaza where the Enforcer’s office is located, they congregated in a small collection of benches nearby an ornate fountain that commemorated the Anaran defense of Felaal IV, largely considered the turning point of the Great War, which further enhanced the beauty of the surrounding scenery of floating walkways above crystal-clear waters.
“Well, that’s a relief, hopefully.” An’Ra began, letting out a decompressing sigh.
“I meant what I said earlier, An’Ra.” Sonak said. “If the Council are determined to charge the Federation, which I’m sure they made abundantly clear, they’re not going to let the Enforcer drop mines in their path just like that.”
“Which just means we can’t lose our focus.” Vora replied sternly. “So, what are our options? We can’t exactly go back to Planet 3, there’s really no leads there.”
“What about that Detective we met when we arrived?” Sonak suggested. “He was handling that whistle blower. Maybe that’s something worth looking into?”
“There’s also the Nav-Net.” Vora said. “All we got right now is that the Feds were at that location, but what if we look at the rest of the network? Try and trace their path?”
“The network doesn’t extend into the Dead Zone.” Sonak countered.
“No, not like that. We look at the network across Alliance space. We start with the logs that end at the Dead Zone, and we try to backtrack their route.”
“We’ll need to obtain legal authorization for that, Vora.” An’Ra stated.
“Actually, if I could add something.” Sonak said with his arms crossed. “If the Federation didn’t actually do it, then that questions the credibility of those codes. I think there’s a question that hasn’t been asked yet. And that is, are those codes faked?”
“That’s...a good point actually.” Vora acceded. “If we get the legal permission to examine the NavNet logs, then if the Federation didn’t do it, the logs across the network won’t support it. Think about it. You need a big fleet to do what just happened, and that fleet has to come from somewhere.”
“And that would mean if this was a frame job, they need a way to account for that.” An’Ra continued, confidence flaring. “It’s one thing to trick a single Nav-Buoy, but I really doubt anyone is capable enough of affecting the network itself.”
“We still need the Enforcer’s help to get access to the network.” Sonak reminded.
“Let’s go get it then.” An’Ra stated firmly. With that, the team left their meeting spot and began returning to the Enforcer’s office.
With confidence in their step, the walk back to the office was much shorter compared to before. However, things took a turn when An’Ra and the team noticed a large gathering of officers around the office entrance. They didn’t have to time to wonder when a group exited the office, dragging a combative Dura out with them.
“Commander, this isn’t good.” Sonak growled under his breath.
An’Ra simply stepped forward and grabbed one of the arresting officers. “What in Arenar’s Sword is going on here?”
“Dura’s under arrest on suspicion of corruption.” The officer replied flatly. “Lil’Al has been appointed as acting Lord-Enforcer.”
“The Council’s behind this, Commander!” Dura shouted, his feet literally dragging along the floor as four officers were taking him away. “Don’t believe a word they say about me!”
An’Ra and his team just stood there in stunned silence, watching and hearing the Anaran official being dragged virtually kicking and screaming. By the time they returned to their senses, hushed conversations was populating both the room and outside.
“We’re not going to get in the network, are we?” Sonak asked, still recovering.
“We still have to try, come on.” An’Ra said, already moving. When the team returned to the office, standing next to the desk was a slender Esti. No doubt Lil’al. She was looking out the window when she turned around upon hearing the encroaching footsteps.
“Yes, may I help you?” She began.
“Acting Lord-Enforcer Lil’Al?” An’Ra began, trying the diplomatic route first. “I’m Commander An’Ra, investigating the genocide by use of Strain Y. We’d like to request legal authorization to examine the logs of the Nav-Net.”
“For what purpose?” She replied, taking her seat.
“We believe that it may hold evidence that either confirms or disproves the Federation’s alleged involvement in the attack.”
Lil’Al leaned back in her seat, staring at them. “The Nav-Net is the lifeblood of, well, everything. Commerce, tourism, law enforcement. It holds great information about who has gone where, and in what ship, Commander. You realize that, don’t you?”
“I do, and what you’ve said precisely states how important that is, how important the potential evidence is.”
Lil’Al stayed motionless for a few moments, her long, lithe fingers twiddling about that indicates her thought. “Very well, I’ll start the paperwork to get you authorization, just be mindful of what you’re about to analyze.”
“Thank you.” An’Ra gave a slight bow. “In addition, I’m not sure if it’s been passed along, but Dura has rejected the Council’s request for prosecuting the Federation. Can I assume you’ll uphold that?”
“I’m afraid not, Commander.” Lil’Al replied flatly. “The galaxy has suffered a great loss through the genocide of a race who’ve suffered the universe’s cruel sense of humor by being placed both far away from us and deep within an almost uninhabitable region. I have overturned Dura’s rash decision and accepted the Council’s request.”
“Then I’d like to file a delay on that decision, immediately.” An’Ra replied, ears flattened back.
“On what grounds?”
“Lack of decisive evidence, to start.”
“Same could be said on your side, Commander.” Lil’Al let out a sigh. “Yes, all the evidence collected thus far is not...ideal. However, the most significant points at this time are that a young race who was just about to leave their homeworld was exterminated through the most horrible of all options. We cannot ignore that.”
“But we also can’t rush to conclusions. We need to continue investigating and only go after someone if we have at least one crucial piece of information.” An’Ra countered, arms crossed and his teeth starting to bare.
“And I agree, that’s how it should be done.” Lil’Al replied. “But if we do, we risk dragging out an investigation to such a length we may end up forgetting this tragedy. We cannot allow such an insult to Planet 3’s memory. I’m sorry, but I must reject your petition for judiciary delay.”
Next Chapter
AN: Every single time I paste this in, Reddit is just determined to put it in some code block. Anyways, As of now, I've finally completely locked in the plot for this story, just one major question that could've changed a lot was on my mind for a while. Enjoy!
submitted by SynthoStellar to HFY [link] [comments]

The Division 2 - Episode 1: D.C. Outskirts - Patch Notes

Patch Notes: Episode 1 - July 23rd, 2019

 

New Main Mission: Manning National Zoo

Emeline Shaw, the leader of the Outcasts, has fallen back from her defeat on Roosevelt Island and barricaded herself deep in the Manning National Zoo. To get to her, you will need to fight through the blockades and the Outcasts who protect her to put an end to her violence.
 

New Main Mission: Camp White Oak

The Black Tusks and their leader have set up a strategic position close to an estate nestled deep in the woodlands, and your assignment is to take them down and capture him in the new Camp White Oak mission.
 

New Feature: Expeditions

Expeditions are free events that bring players to unexplored locations around D.C. to discover new narrative and gameplay opportunities. These sites offer unique challenges and lore not found anywhere else: new collectibles, treasure rooms, environmental puzzles, unique boss mechanics, and more await every Agent who embarks on our Expeditions!
New Classified Assignment: Central Aquarium New Classified Assignment: NSA Site B13
 

Shepherd Reward System – Call for Backup

  • Added the ability to earn the “Shepherd” title by responding to call for backups and earning endorsements. An agent who received help will be able to endorse the helping agent.
 

Raid

  • Added Discovery Mode difficulty for the Operation Dark Hours raid.
  • Added Raid Completion Time to Clan Leaderboards. This leaderboard ranks clans based on how quickly they were able to complete the raid as a clan-only party.
 

Exotics

New Exotic: Diamondback Exotic Rifle
  • Lever action rifle
  • 5 round magazine
  • 100 RPM
  • Talents:
    • "Agonizing Bite"
      • Diamondback randomly marks an enemy. Hitting that enemy consumes the mark, guaranteeing a critical hit with +20% total damage. A new random enemy is marked afterwards, and whenever you reload.
    • "Deep Fangs"
      • After hitting 5 marked enemies, gain +50% reload speed, +20% total damage and all shots fired are guaranteed critical hits for 10s.
    • "Shedding Skin"
      • While drawn, each time a round is loaded, gain +20% bonus armor for 3s. While holstered, each time you reload or cycle your current weapon, gain +8% bonus armor for 2s
 

New Exotic: BTSU Exotic Gloves

  • Black Tusk gloves
  • Talents:
    • "Elemental Gadgetry"
      • Skills that apply status effects gain +50% status effect duration and +50% skill haste
    • "Energy Infusion"
      • Whenever you apply a status effect, your gloves become infused with that for 60s. While infused, you gain +10% skill damage, +10% skill healing and repair and +10% skill duration for each Utility (yellow battery) on your gear.
    • "Charged Proxies"
      • Whenever you throw a skill, 1.25s after landing, it creates an explosion applying the infused status effect to all enemies within 6m. Enemies affected by the infused status effect take 50% more damage from your skills.
  • Heroic Bosses now drop Exotics
    • Only exotics that the player is qualified for.
      • For world drop exotics it requires that the player has the drop previously
      • For crafted exotics, it requires that the player has the blueprint
      • Eagle Bearer remains exclusive to the Operation Dark Hours Raid
    • The purpose of dropping these is to allow a chance to get GS 500 variants without upgrading, or get materials to upgrade other exotics
    • These exotics can be team shared to other players.
  • Exotic items no longer have a random range on their damage/armor roll. All exotics are set to the previous highest possible value. This also affects existing exotic items.
 

Weapons

New Assault Rifle: Carbine 7
  • 30 round mag
  • 790 RPM
  • By default rolls with a new talent:
    • "Overflowing"
      • Every 3 reloads from empty increases your magazine capacity by 100%
 
New Light Machine Gun: Stoner LMG
  • 580 RPM
  • 200 Mag capacity
  • By default rolls with a new talent:
    • "Overwhelm"
      • Suppressing an enemy, that is not currently suppressed, grants +5% weapon damage for 10 seconds. Max stack is 5.
 
  • Increased the base damage of Shotguns in PvE.
    • M870: +36% damage
    • AA12: +29% damage
    • Super 90: +33% damage
    • SASG-12: +33% damage
    • SPAS12 +8% damage
 

Weapon Mods

  • Added Flashlight attachments for pistols
 

Skills

Developer Comments: We took a hard look at the current meta. The builds that are fun, effective and popular. We knew that skill builds, while it being something people want to play with, was nowhere near competitive. We knew there was an explosives damage build that was on the fringe of popularity, but none that actually relied on really good skill mods driven by skill power.
We analyzed the best damage builds and survivability builds out there and looked at their efficiency - how fast they kill, how fast they can clear content, how fast they can take down enemies - and mapped that to our skills. How much more power do skills need to get from 3K skill power (our current maximum requirement on skill power mods) to compensate for all the damage bonuses the player is "giving up" on gear to reach that skill power?
Then we looked at each skill and what it should be good at (burst, sustain, single target damage, survivability etc) and went to work tuning the mods to make a skill build approach the efficiency of a "red" damage build or a "blue" tank build. To that effect, here are the current changes to skill mods power levels, and in some cases base numbers, on skills.
 

Skill Haste

Cooldown Reduction has been replaced with skill haste. Skill haste works equivalent to speed. So 100% skill haste reduces cooldown by 50%, like a car speeding up by 100% getting to it's destination in half the time. This means that the player can invest in more than 100% Haste and still get something back. It also means there's a diminishing return to Skill Haste, as opposed to cooldown reduction where each point was actually worth more than the last one. This allows us to have a good amount of Skill Haste possible from gear, but even larger amounts granted by high skill power Skill Mods, granting skill builds more frequent access to their souped up skills.
To that effect, these are the changes to Haste (formerly Cooldown Reduction)
  • Removed the 90% Cooldown Reduction hard cap
  • Lowered the minimum Cooldown cap for all skills from 10 seconds to 3, except for the Chem Launcher which is now 8
  • Renamed all instances of Cooldown Reduction on existing gear to Skill Haste, with a 50% increase to their base values
  • Eg: +10% Cooldown Reduction will become +15% Skill Haste
  • Increased Surge talent Skill Haste bonus from +10% to +20%
  • Increased Alps Summit Armament 1-piece Skill Haste bonus from +10% to +20%
  • Increased China Light Industries Corporation 3-piece Skill Haste bonus from +10% to +30%
  • Increased Petrov Defense Group 3-piece Skill Haste bonus from +10% to +30%
  • Increased Tip of the Spear 3-piece Skill Haste bonus from +20% to +40%
 

Specialization Skill Mods (granted from each spec tree)

  • Removed all Skill Power requirements
  • Bonuses greatly improved to provide a strong initial boost to the skill platform
  • Demolitionist
    • Cyclone Magazine - Extra Mortar Ammo bonus increased from +1 to +3
    • SHD CPU V.2 - Damage increased from +7% to +100%
  • Survivalist
    • Magnetic Disc - Skill Haste increased from +9.7% to +80%
    • Larrea Tridenta Infusion - Healing bonus increased from +14.5% to +50%
  • Sharpshooter
    • Graphene Battery - Duration increased from +14.5% to +80%
    • Carbon Fiber Frame - Skill Haste increased from +9.7% to +80%
  • Gunner
    • Microwave Amplifier - +30% Banshee Pulse Confuse Duration
    • Directional Transmitter - +30% Banshee Pulse Cone Size
 

Skill Platform Changes

Pulse
  • Scanner
    • Scanner Pulse will now begin its cooldown after a 3 second delay on activation, rather than at the end of the Pulse effect's duration
    • Lowered Scanner Pulse base radius from 52m to 50m
    • Lowered Scanner Pulse cooldown from 90s to 40s
  • Remote
    • Lowered Remote Pulse cooldown from 120s to 60s
  • Jammer
    • Lowered Jammer Pulse cooldown from 120s to 90s
Turret
  • Assault
    • Increased Assault Turret base damage by 22.5%
    • Increased Assault Turret base duration from 120s to 300s
    • Lowered Assault Turret cooldown 120s to 60s
  • Incinerator
    • Lowered Incinerator Turret base damage by 60%
    • Increased Incinerator Turret base burn damage by 60%
    • Lowered Incinerator Turret base burn duration from 5s to 4s
    • Increased Incinerator Turret base duration from 120s to 300s
    • Lowered Incinerator Turret cooldown from 120s to 90s
  • Sniper
    • Increased Sniper Turret base ammo from 5 to 6
    • Lowered Sniper Turret cooldown from 240s to 60s
  • Artillery
    • Lowered Artillery Turret cooldown from 240s to 60s
  • Increased Turret platform base health by 100%
Hive
  • Restorer
    • Increased Restorer Hive base healing amount by 50%
    • Increased Restorer Hive base health by 20%
    • Lowered Restorer Hive cooldown from 240s to 90s
  • Stinger
    • Stinger Hive damage is no longer affected by Explosive Damage modifiers
    • Increased Stinger Hive base health by 50%
    • Lowered Stinger Hive cooldown from 240s to 90s
  • Booster
    • Increased Booster Hive base health by 33.3%
    • Lowered Booster Hive cooldown from 240s to 90s
Chem Launcher
  • Firestarter
    • Increased Firestarter Chem Launcher base burn damage by 60%
    • Lowered Firestarter Chem Launcher base burn duration from 5s to 4s
  • Riot Foam
    • Increased Riot Foam Chem Launcher base radius from 1.5m to 3m
Firefly
  • Blinder
    • Lowered Blinder Firefly base blind duration from 8s to 6s
  • Burster
    • Lowered base damage of Burster Firefly by 20%
    • Lowered Burster Firefly cooldown from 90s to 60s
  • Demolisher
    • Lowered base damage of Demolisher Firefly by 25%
    • Lowered Demolisher Firefly cooldown from 90s to 60s
Seeker Mine
  • Explosive
    • Increased Explosive Seeker Mine base damage by 42.8%
  • Airburst
    • Increased Airburst Seeker Mine base burn damage by 60%
    • Lowered Airburst Seeker Mine base burn duration from 5s to 4s
  • Cluster
    • Increased Cluster Seeker Mine base damage by 33.3%
    • Increased Cluster Seeker Mine explosion radius from 3m to 4m
    • Lowered Cluster Seeker Mine cooldown from 90s to 40s
  • Mender
    • Increased Mender Seeker Mine base duration from 120s to 300s
    • Lowered Mender Seeker Mine cooldown from 180s to 60s
Drone
  • Striker
    • Increased Striker Drone base damage by 7.1%
    • Increased Striker Drone base duration from 120s to 300s
    • Lowered Striker Drone cooldown from 180s to 60s
    • Lowered Striker Drone base health by -20%
  • Defender
    • Lowered damage reduction from 100% to 80% (20% in PvP)
    • Increased Defender Drone base duration from 20s to 40s
    • Increased Defender Drone base health by 100%
  • Bombardier
    • Lowered Bombardier Drone cooldown from 120s to 60s
    • Lowered Bombardier Drone base health by -46.6%
    • Increased Bombardier Drone base bomb blast radius from 3 to 4 meters
  • Fixer
    • Increased Fixer Drone base health by 60%
    • Increased Fixer Drone base duration from 180s to 300s
    • Lowered Fixer Drone cooldown from 180s to 60s
  • Tactician
    • Increased Tactician Drone base duration from 180s to 300s
    • Lowered Tactician Drone cooldown from 180s to 60s
    • Lowered Tactician Drone base health by -73.3%
Ballistic Shield
  • Ballistic Shield base health regeneration is now percentage based and scales with the total health of the shield
    • 5% HP/s Holstered Regeneration
    • 2.5% HP/s Active Regeneration
  • Bulwark
    • Increased Bulwark Ballistic Shield base health by 33%
    • Lowered Bulwark Shield cooldown from 240s to 40s
  • Crusader
    • Lowered Crusader Shield cooldown from 240s to 40s
  • Deflector
    • Lowered Deflector Ballistic Shield base health by 6.6%
    • Lowered Deflector Shield cooldown from 240s to 40s
 

Skill Mod Changes

All numbers based on maximum (3000 skill power) mod attribute rolls
Hive
  • Extra Payload - Damage bonus increased from +30% to +100%
  • Experimental Blend - Changed from flat value to percentage based increase of base Healing amount (+50%)
  • Experimental Blend - Stim Efficiency bonus increased from +20% to +50%
  • Experimental Blend - Buff Duration bonus increased from +20% to +50%
  • Nitroglycerin Mixture - Damage bonus increased from +30% to +100%
  • Nitroglycerin Mixture - Healing bonus +50% variant added
  • Cooling Vents - Skill Haste bonus increased from +20% to +100%
  • Internal Storage - Charges bonus increased from +30% to +100%
  • Swarm Control - Charges bonus increased from +30% to +100%
  • Radar Signal Antennas - Duration bonus lowered from 60% to 50%
  • Network Firewall - Radius bonus increased from +60% to +100%
  • Network Firewall - Duration bonus lowered from 60% to 50%
  • Steel Harness - Health bonus lowered from 60% to 50%
  • Polycarbonate Wiring - Health bonus lowered from 60% to 50%
Turret
  • Magnetic Rail - Damage bonus increased from +30% to +150%
  • Lubrication Gel - Duration bonus increased from +60% to +100%
  • Lubrication Gel - Incinerator Turret Burn Strength +100% variant added
  • Cyclone Magazine - Extra Mortar Ammo +8 variant added
  • Cyclone Magazine - Extra Sniper Ammo +12 variant added
  • Spare Parts - Skill Haste bonus increased from +20% to +100%
  • Organic Circuits - Duration bonus increased from +60% to +100%
  • Ammo Box - Extra Sniper Ammo bonus increased from +3 to +12
  • Ammo Box - Extra Mortar Ammo bonus increased from +2 to +8
  • Ammo Box - Mortar Radius +50% variant added
  • SHD CPU V.2 - Damage +150% variant added
  • Multi-tool - Skill Haste bonus increased from +20% to +100%
  • Weather Coating - Health bonus lowered from +120% to +100%
  • Carbon Fiber Barrel - Health bonus lowered from +120% to +100%
Pulse
  • Nickel-Chromium Wire - Skill Haste bonus increased from +60% to +200%
  • Nickel-Chromium Wire - Remote Pulse Skill Haste +300% variant added
  • Silicon Carbide Coil - Charging Speed bonus increased from +30% to +50%
  • Exploded Blueprint - Skill Haste bonus increased from +60% to +200%
  • Heating Mantle - Charging Speed bonus increased from +30% to +50%
  • Distributed Architecture - Radius bonus lowered from 60% to 50%
  • Super Glue Pulse - Radius bonus lowered from 60% to 50%
  • Unstable Oscillator - Effect Duration bonus lowered from 55% to 50%
  • Atmospheric Analyzer - Effect Duration bonus lowered from 55% to 50%
Seeker Mine
  • Mini Electric Motor - Skill Haste bonus increased from +40% to 200%
  • Delivery System Upgrade - +100% Damage variant added
  • Ball Bearings - Damage bonus increased from +30% to 100%
  • Magnetic Disc - Skill Haste +200% variant added
  • Phosphorus Ingredient - Healing bonus increased from 60% to 100%
  • RDX Pellet Payload - Damage bonus increased from +30% to +100%
  • RDX Pellet Payload - Airburst Burn Strength +100% variant added
  • Larrea Tridenta Infusion - Healing +100% variant added
  • Brushless DC-motor - Health bonus lowered from 60% to 50%
  • Sturdy Piston - Health bonus lowered from 60% to 50%
Chem Launcher
  • Piranha Solution - Damage bonus increased from +30% to +100%
  • Piranha Solution - Firestarter Burn Strength +100% variant added
  • Chromatics Training - Radius bonus increased from +30% to +50%
  • Slip Fit Tube - Skill Haste bonus increased from +30% to +100%
  • Cell Penetrating Peptide - Healing bonus increased from +60% to +100%
  • Hydrochloric Infusion - Damage bonus increased from +30% to +100%
  • Ultra-Thin Cartridges - Radius bonus increased from +30% to +50%
  • Liquid Nitrogen Cooling System - Skill Haste bonus increased from +30% to +100%
  • Pharmacokinetic Enhancer - Healing bonus increased from +60% to +100%
  • Imbued Metal String - Ensnare Health bonus lowered from +60% to +50%
  • Polypropylene Recipe - Ensnare Health bonus lowered from +60% to +50%
Drone
  • Graphene Battery - Duration +100% variant added
  • Electric Soldering Tool - Skill Haste bonus increased from +40% to +100%
  • Gimbal Vibration Damping - Health bonus increased from +60% to +100%
  • Blitzkrieg Blasting Powder - Striker Damage +600% variant added
  • Blitzkrieg Blasting Powder - Radius bonus lowered from 60% to 50%
  • Freedom Package - Radius bonus lowered from 60% to 50%
  • Carbon Fiber Frame - Skill Haste +100% variant added
  • Reinforced Rotor Blades - Health bonus increased from +60% to +100%
  • Terminal Ballistics - Damage bonus increased from +30% to +200%
  • Trauma Analyzer - Healing bonus increased from +30% to +50%
  • Trauma Analyzer - Deflector Duration +50% variant added
  • Gaffer Tape - Duration bonus increased from +60% to +100%
  • Hollow-point Bullets - Damage bonus increased from +30% to +200%
  • Micropulsing Stimuli - Healing bonus increased from +30% to +50%
  • Micropulsing Stimuli - Fixer Skill Haste +100% variant added
Shield
  • Adaptive Insulation Foam - Skill Haste bonus increased from 60% to 100%
  • Synthetic Mineral Frame - Skill Haste bonus increased from 60% to 100%
  • Titanium Reinforcement - Health bonus increased from +45% to +100%
  • Shape-memory Alloy - Deflected Damage bonus increased from +20% to +100%
  • Cementitious Material - Holstered Regeneration bonus increased from +60% to +100%
  • Weaved Aramid Fiber - Health bonus increased from +45% to +100%
  • Supramolecular Networks - Active Regeneration bonus increased from +20% to +100%
  • Liquid Metal Microdroplets - Holstered Regeneration bonus increased from +60% to +100%
  • Thermoresponsive Polymer - Deflected Damage bonus increased from +20% to +100%
  • Smart UHMWPE Lexicon - Active Regeneration bonus increased from +20% to +100%
  • Smart UHMWPE Lexicon - Ballistic Shield Health +100% variant added
Firefly
  • Alignment Valve - Damage +100% variant added
  • Tungsten Compound - Damage +100% variant added
  • Propantriol Adhesive - Skill Haste bonus increased from +40% to +200%
  • Microfiller Resin - Skill Haste bonus increased from +40% to +200%
  • Hardened Casing - Health bonus lowered from 60% to 50%
  • Tungsten Compound - Max Targets bonus increased from +3 to +5
  • Guiding System - Max Targets bonus increased from +3 to +5
 

Crafting

  • Added a crafting bench upgrade in World Tier 5 that allows players to craft at Gear Score 500. The items crafted are gear score 500, there will be no random range in terms of gear score/power. The bench upgrade is given to players when they complete the “Enter WT5”-project (same as all the other bench upgrades in endgame, the upgrade will be available at the bench once the bench is upgraded to World Tier 5). Players already in WT5 will automatic get it as they log in, The upgrade requires 1 weapon and 1 gear piece of Gear Score 490+, and some of each Specialized (blue) material Crafted items can be used in recalibration, both as materials and to be improved
  • Deconstructing High-End gear now guarantees a brand material (increased from 50% drop chance). Named branded items also award the brand mat on deconstruction
  • Deconstructing gear set items awards 4 of each Specialized (blue) material
  • Added an opt-in perk for the player to share blueprints and materials between characters in endgame. Some Blueprints and mats are excluded to not break game logic/progression, such as the specific exotic materials. This perk can be crafted and the blueprint is available at Inaya, the Crafting vendor.
  • The blueprints awarded from control points, vendors and projects are merged into one pool of rewards. Players can get all these blueprints from all three sources. Once the pools has been exhausted, none of the sources will give more blueprints.
 

Grenades

  • Increased the radius of the Gunner's Riot Foam Grenade from 2m to 3m
 

PvP

  • Changed shotgun PvP modifier to 1.0 (was 1.65)
    • Net result in PvP with revised normalization modifiers:
      • M870: -14% damage
      • AA12: -21% damage
      • Super90: -17% damage
      • SASG-12: -17% damage
      • SPAS12: -42% damage
  • Changed the general PvP modifier to 0.55 (was 0.40)
 

Specializations

  • Reduced the TAC-50 signature weapon’s damage per shot
 

Talents

  • Calculated Talent reduced to 20% from 10%. Now works off any kill from cover instead of weapon kills.
 

Vendors

  • Cassie Now sells GS 500 items. She sells normal gear, some exotics and named weapons
 

UI

  • Improved player feedback when trying to pick up ammo with maximum signature weapon ammo
  • Inspecting a player now allows inspection of weapons, grenades and skills
 

3C

  • Intercepted projectile by the deflector drone now do a % damage, rather than binary be dropped or not
  • Return player control quicker after dropping down
  • Reduced Depth of Field strength when aiming
  • Improved reload + interaction prioritization (if you hold down the interact, it will cancel the reload and start the interaction)
  • Improved player replication for players with widely different quality connections, should reduce inconsistent speedup/freezing of remote players
 

Audio

  • Slapback System enabled: The gunshot echo system that was featured briefly in the private beta prior to launch has been re-enabled
 

Localization

  • Improved Arabic voice-over localization
  • Added missing lore description for Dodge Citys Gunslinger Holster
 

Bug Fixes

Skills
  • Cyclone Magazine +Extra Sniper Ammo variant added to all loot list quality tiers
  • Unstable Oscillator and Atmosperic Analyzer Pulse Mods now properly reference the correct Effect Duration platform modifier
  • Vac Pack and Guiding System Firefly mods now correctly increase Max Targets by the amount listed on the tooltip
  • Distributed Architecture and Super Glue Pulse mods no longer affect the radius/range of the Banshee Pulse
  • Explosive Seeker Mine radius now correctly says 5m in the Skills UI
  • Cluster Seeker Mine radius is now displayed in the Skills UI
  • Explosive and Cluster Seeker Mines now show the correct explosion radius before detonating
  • Incinerator Turret burn damage is now affected by all increases to Skill Damage from geatalents
  • Firestarter Chem Launcher burn damage is now affected by all increases to Skill Damage from geatalents
  • Firestarter Chem Launcher now correctly states that it inflicts fire damage.
  • Added missing Artillery Turret & Tactician Drone showcase videos.
  • Airburst burn damage is now affected by all increases to Skill Damage from geatalents
  • Fixed an issue causing the Chem Launcher cooldown to reset when restocking ammo
  • Fixed an issue where the Turret skill could deploy inside a wall under certain circumstances
  • Fixed an issue causing the reviver hive to not revive players when thrown
  • Fixed skill mods requirement having an invisible decimal, resulting in incorrect power requirement information
  • Fixed the Banshee Pulse skill mod description to state that it applies Confusion status effect on affected target
 
Conflict
  • Fixed an AFK related exploit in the Conflict PvP mode
  • Fixed several locations on Conflict maps where players could ignore damage when behind cover
 
Weapons & Gear
  • Fixed an issue where the Sweet Dreams and Lullaby upgrade blueprints wouldn't appear on the crafting vendor under certain circumstances
  • Fixed an issue where some Longe Range Pack "Sett" backpacks could roll with 0% weapon damage on Specialized (blue) quality
  • Fixed an issue where the opportunistic talent did not work in PvP.
  • Fixed an issue causing armor rolls below the minimum advertised when upgrading an exotic gear piece.
 
Missions & Open World
  • Fixed an issue causing players to become stuck during the “Reach the first hall” objective in the Air & Space museum mission
  • Fixed a loot exploit in the Invaded Capitol Hill stronghold
  • Fixed enemies becoming stuck in their spawn rooms in the “Museum Water Source” side mission
  • Fixed “Neutralize the hostile” objective not updating correctly in the “Agent Edwards Support” side mission
  • Fixed an issue where NPC’s from a Warhound Convoy could spawn in an inaccessible area
  • Fixed an inaccessible bounty location in the Judiciary Square zone
  • Fixed several areas where players could leave the playable map
  • Fixed several areas where players could fall through the world
  • Fixed several areas where players could vault into water. Don’t go swimming with all that gear, agents!
  • Fixed several areas with missing climb prompts
  • Fixed several areas where the player could become stuck in the open world
  • Fixed several areas where the players could become stuck in missions
  • Fixed several world objects with missing cover prompts
 
Special Field Research
  • Fixed Special Field Research objective “Complete 5 Public Executions with Marksman Rifle” not progressing under certain circumstances
  • Fixed the Specialization adventure progression circle to be consistent with other progression circles
 
Commendations
  • Fixed “Resource Distribution Merit” not progressing correctly
  • Fixed “Calibration Award” not unlocking not progressing correctly
  • Fixed “Prone Target Award” not progressing correctly.
 
Loadouts
  • Fixed an issue causing loadouts using the same skill to revert all affected loadouts to the same skill mod
 
UI
  • Fixed the Conflict UI being misaligned when using Dual Monitors and the Offset UI option
 
NPC
  • NPCs no longer double heal their armor
  • Players can now damage NPCs rappelling on ropes with explosives
  • Fixed an error during the calculation of weakpoint kill stats
  • Players can no longer easily pass through Black Tusk Warhounds
  • Control point officers no longer instantly revive players if the player has just used the Chem Launcher
  • Outcasts suicide rushers now blow themselves up closer to their target
  • Fixed abnormal NPC behaviour when suppressed outside of the players view
 
Dark Zone
  • Fixed an issue where agents at Dark Zone level 50 do not lose XP when killed as a rogue agent.
  • Fixed an issue where the Black Tusk medic’s drones would self-destruct in the Dark Zones
  • Fixed an issue where the player was unable to cut the rope at an extraction if the “Sleight of Hand” perk was active.
 
Specialization
  • Fixed an issue where killing wildlife would yield signature weapon ammo.
  • Fixed an issue where signature weapon ammo could drop mid-air
 
Cosmetics
  • Fixed a clipping issue with the Gunner Uniform when equipped on a female character
 
Connectivity
  • Fixed an issue relating to interacting with ECHO’s when in a group
  • Fixed several occurrences of Delta errors when interacting with world objects
 
Performance
  • Fixed performance drops when browsing player inventory on Xbox One
  • Fixed performance drops when opening the Ubisoft Club Challenge tab on PC
 
Audio
  • Fixed an issue causing NPC weapon audio to be stuck in a loop under certain circumstances
  • Fixed an issue causing missing weapon audio when firing immediately after having switched from a grenade
 
Other
  • Fixed an issue causing older versions of the Tobii Eye Tracker to be unresponsive
  • Fixed an issue causing the “Aim at Gaze” option for the Tobii Eye Tracker to be inaccurate
  • Fixed an issue with the Motion Sickness mode causing the player’s FOV to change drastically when enabled
  • Fixed an issue where players incorrectly could vote kick a member during a boss fight in the Roosevelt Island stronghold on challenging difficulty
Source
submitted by JokerUnique to thedivision [link] [comments]

MAME 0.210

MAME 0.210

It’s time for the delayed release of MAME 0.210, marking the end of May. This month, we’ve got lots of fixes for issues with supported systems, as well as some interesting additions. Newly added hand-held and tabletop games include Tronica’s Shuttle Voyage and Space Rescue, Mattel’s Computer Chess, and Parker Brothers’ Talking Baseball and Talking Football. On the arcade side, we’ve added high-level emulation of Gradius on Bubble System hardware and a prototype of the Neo Geo game Viewpoint. For this release, Jack Li has contributed an auto-fire plugin, providing additional functionality over the built-in auto-fire feature.
A number of systems have had been promoted to working, or had critical issues fixed, including the Heathkit H8, Lola 8A, COSMAC Microkit, the Soviet PC clone EC-1840, Zorba, and COMX 35. MMU issues affecting Apollo and Mac operating systems have been addressed. Other notable improvements include star field emulation in Tutankham, further progress on SGI emulation, Sega Saturn video improvements, write support for the CoCo OS-9 disk image format, and preliminary emulation for MP3 audio on Konami System 573 games.
There are lots of software list additions this month. Possibly most notable is the first dump of a Hanimex Pencil II cartridge, thanks to the silicium.org team. Another batch of cleanly cracked and original Apple II software has been added, along with more ZX Spectrum +3 software, and a number of Colour Genie cassette titles.
That’s all we’ve got space for here, but there are lots more bug fixes, alternate versions of supported arcade games, and general code quality improvements. As always, you can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

Software list items promoted to working

New NOT_WORKING software list additions

Source Changes

submitted by cuavas to emulation [link] [comments]

MAME 0.210

MAME 0.210

It’s time for the delayed release of MAME 0.210, marking the end of May. This month, we’ve got lots of fixes for issues with supported systems, as well as some interesting additions. Newly added hand-held and tabletop games include Tronica’s Shuttle Voyage and Space Rescue, Mattel’s Computer Chess, and Parker Brothers’ Talking Baseball and Talking Football. On the arcade side, we’ve added high-level emulation of Gradius on Bubble System hardware and a prototype of the Neo Geo game Viewpoint. For this release, Jack Li has contributed an auto-fire plugin, providing additional functionality over the built-in auto-fire feature.
A number of systems have had been promoted to working, or had critical issues fixed, including the Heathkit H8, Lola 8A, COSMAC Microkit, the Soviet PC clone EC-1840, Zorba, and COMX 35. MMU issues affecting Apollo and Mac operating systems have been addressed. Other notable improvements include star field emulation in Tutankham, further progress on SGI emulation, Sega Saturn video improvements, write support for the CoCo OS-9 disk image format, and preliminary emulation for MP3 audio on Konami System 573 games.
There are lots of software list additions this month. Possibly most notable is the first dump of a Hanimex Pencil II cartridge, thanks to the silicium.org team. Another batch of cleanly cracked and original Apple II software has been added, along with more ZX Spectrum +3 software, and a number of Colour Genie cassette titles.
That’s all we’ve got space for here, but there are lots more bug fixes, alternate versions of supported arcade games, and general code quality improvements. As always, you can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

Software list items promoted to working

New NOT_WORKING software list additions

Source Changes

submitted by cuavas to MAME [link] [comments]

GESTIONARTE Binary Options Magnet The Worlds First Binary Options Bot zmartbit - ProTradeHub Binary Signals Tutorial with IQ Option Binary Option Digital Binary Options Trading Signals - YouTube Potential Energy of Bar Magnet in UMF (part 2)

Now with 223 members earning $1,857.93 a day. The video shows what their member accomplished from the software. Rob, 21, bought a new Audi sports car after 5 weeks of being a member. Read more Profit Magnet – Make money with binary options? Tokyo BOT review – Not what you think. Apr 19, 2016 Apr 19, 2016 by Susan p. What is “Tokyo BOT Binary Options Trading. Binary options is a simple trading instrument that can be used to earn money by guessing the future of the Forex, stocks, commodity and other prices. With binary options you either win if you guessed it right, or lose if you guessed it wrong. BinaryTrading.com is here to help you to win more often than lose. Binary options aren’t bad but Profit Magnet is! There are several loop holes in this binary options service that are evident from watching the video on the single paged “website”. The video will tell you that you can make $1000 in the first 24 hours of using this system. Featureless members dashboard More bad Dukascopy Binary options contest is a competition between participants using DEMO accounts for binary options trading. The participants are ranked by their monthly cumulative profit. The Contest is conducted regularly on a monthly basis. The total prize fund is 10,000 USD to be shared among the winn... The photo depicted below is a screenshot of their alleged team members found in the Profit-Magnet.net homepage. Aaron Martin’s picture was taken from Shutter Stock which indicates hes not a real person or “CEO”, and his identity was fabricated by crooked developers of this scam software. Trading Binary Options is among the easiest

[index] [25550] [28950] [8148] [16572] [4949] [16139] [8688] [22421] [8242] [13395]

GESTIONARTE

# lecture2- magnetic materials -magnetic potential energy,time period of oscillations of bar magnet - Duration: 10:57. ... Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING! ... Take The Stress Out of Trading - Get Into Binary Options Today! If you've never heard of Binary Options before, you probably trade Forex, Stocks, Commodities... http://www.maxireviews.com proudly presents Binary Options Magnet The Worlds First Binary Options Bot from Thomas Hunt "I Make $100 - $900 Per Day Trading Wi... Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING! ... McMurray & Members Recommended for you. ... it brings Financial prosperity, success and Luck, Money Magnet, listen 10 ... Binary options are form of options trading based on a yes or no question. Try binary options today at: https://www.wallstreetsurvivor.com You're either right or you're wrong in this all or nothing ...

Flag Counter